Depends a bit on what features you want to have. I use LibreELEC to run Kodi (and nothing else). Previously I used OSMC to run Kodi and some other things (steam link among others). You can use an app (kore) control kodi, which is very conveniant. RF remotes work well too, apparently.
I use a remote called the “Pepper Jobs W10 Gyro” and I love it. All the keys are set up for Windows (🤢) shortcuts, but other than that it’s awesome. It would be great for Kodi.
It seems that the consensus from all the comments is that you do in fact need a firewall. So my question is how does that look exactly? A hardware firewall device directly between modem and router? I using the software firewall on the router enough? Or, additionally having software firewall installed on all capable devices on the network? A combination of the above?
Depends on your setup. I got a network-level firewall+router setup between my modem and my LAN. But also, got firewalld (friendly wrapper on iptables) on every Linux device I care about because I don’t want to unintentionally expose something to the network.
hm, guess maybe I should find something for Android and my Windows boxes.
And like most things related to Linux on the internet, the consensus is generally incorrect. For a typical home user who isn’t opening ports or taking a development laptop to places with unsecure wifi networks, you don’t really need a firewall. It’s completely superflous. Anything you do to your PC that causes you genuine discomfort will more than likely be your own fault rather than an explicit vulnerability. And if you’re opening ports on your home network to do self-hosting, you’re already inviting trouble and a firewall is, in that scenario, a bandaid on a sucking chest wound you self-inflicted.
I bought my wife an HP Stream 13 some years back. It came with Windows 8 installed. Which worked just fine until updates bloated it so much it literally took up the entire (paltry) SSD. Windows 10 came out and it offered a free upgrade, which would have been smaller. Unfortunately, every time I tried to do that, it just complained it didn’t have the space to make the switch. I rolled it back to an older Windows 8 and disabled updates to try and keep using it. It complained constantly. I finally deleted the shit out of Windows and installed Lubuntu. It’s worked since then without issue.
I think it’s better to have one but you probably don’t need multiple layers. When I’m setting up servers nowadays, it’s typically in the cloud and AWS and the like typically have firewalls. So, I don’t really do much on those machines besides change ports to non-standard things. (Like the SSH port should be a random one instead of 22.)
But you should use one if you don’t have an ecosystem where ports can be blocked or forwarded. If nothing else, the constant login attempts from bots will fill up your logs. I disable password logins on web servers and if I don’t change the port, I get a zillion attempts to ssh using “admin” and some common password on port 22. No one gets in but it still requires more compute than just blocking port 22 and making your SSH port something else.
isn’t it an entire OS? I only need to bind the internet traffic of my container to the ones I want doing something like network_mode: container:myhidemecontainer in docker compose
Building images is easy enough. It’s pretty similar to how you’d install or compile software directly on the host. Just write a Dockerfile that runs the hide.me install script. I found this repo and image which may work for you as is or as a starting point.
When you run the image as a container you can set it up as the network gateway, just find a tutorial on how to set up a Wireguard container and replace Wireguard with your hide.me container.
In terms of kill switches you’d have to see how other people have done it, but it’s not impossible.
I found this repo and image which may work for you as is or as a starting point.
Wow I completely missed this one! This is exactly what I was planning to do! I actually installed the original repo because I’m not on arm, and it seem to work very well! I have to do a few tests to check if the killswitch actually works
I didn’t even look to see if the one I linked was a fork. I’m glad it works!
A cool thing about Dockerfiles is that they’re usually architecture agnostic. I think the one I linked is as well, meaning that the architecture is only locked in when the image is built for a specific one. In this case the repo owner probably only built it for arm machines, but a build for x86_64 should work as well.
Could you please provide a brief description of Vital? I’m in the process of rebuilding my musicmaking setup after a 15 years long hiatus, so I need to update myself on what’s out there.
On that note, it looks like I’m gonna go for bitwig over Ardour. Any thoughts/opinions on that?
Vital is a vst similar to Serum, a pretty popular paid vst. It has a bunch of preset sounds but offers a lot of options for effects and automation to design your own sounds. I use it a ton personally and get a lot of range from it.
Getting plugins to install is often a big hurdle, if they are working, they work. However I think performance suffers alot. Didn’t try it on any bigger synths yet tho.
Might depend on what DAW you use but I found it abit tedious to setup with Ardour, but after that it worked perfectly with the VSTs I was running on Windows, mainly Amplitube 5.
I use it for spitfire labs, ott, and delay lama (very important) and all work great. There are occasional crashes when messing with parameters, but usually those don’t happen more then once. I haven’t noticed any performance issues.
linux
Oldest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.