• 1 Post
  • 145 Comments
Joined 3 年前
cake
Cake day: 2023年6月27日

help-circle
  • Fair point. Plex doesn’t ask for an API key, I wasn’t aware that other services asked for a user-provided key. It’ll be interesting to see how it shakes out with the services that ask for a user-provided API key.

    And yeah, I agree that 10 days notice is not good.

    Personally, I scrobble both to last.fm and to listenbrainz, but I get most of my stats from last.fm because of the easy drilldown features. If listenbrainz ever gets that worked out, I’ll switch… especially because listenbrainz can capture individual artists in tracks with more than one artist.









  • My comment, which you refer to, said nothing about NAT -or- firewalls. Rather, it’s a direct response to the second sentence in the article’s opening paragraph: “To the average computer user, the idea that someone could just… connect to your computer feels exotic, or even dangerous…”

    You may be correct that nobody would recommend implementing IPv6 without a firewall. But this article avoids the subject of firewalls completely, which in combination with that opening paragraph leaves the distinct impression that we shouldn’t be concerned about it because that’s the way the internet was meant to be.

    Of course this has nothing to do with NAT or IPv6, and the value of IPv6 can’t be overstated. But to ignore the security part of the equation is going to have one of two effects: 1) people who don’t know better will think they can use IPv6 without a firewall, or 2) people who understand the risks will be skeptical of the claims that IPv6 is better because you are leaving out an important part of the equation.









  • The point of the reverse proxy is that it simplifies your firewall configuration… you open one port (443) to one endpoint (your reverse proxy), and that’s it. The more complex your firewall configuration, the more likely you are to get something wrong and accidentally expose what you might not want to expose.

    I do not use my reverse proxy for access control.

    If you’re using containerized applications, then the worst-case scenario is somebody gets root permissions inside the container. Under those circumstances, they can destroy that instance of your application and access any data stored within the container. The thing is, they can ALSO do that if you’re on a VPS.

    If there happens to be a Docker vulnerability that allows file system access to the host AND AT THE SAME TIME an application vulnerability, then you might be in trouble. The confluence of those two events, especially if you keep things updated, is unlikely enough that I have no reservations about hosting public services on my home network.

    But that said… we all have our own level of risk tolerance. If it’s not right for you, then you shouldn’t do it.

    edit: just reading up on huntarr and ooooh boy. Vibe coded app that asked you to provide API keys so it could talk to and control other services. No wonder it caused problems. It’s probably worth saying out loud: if the container you want to install is used to talk to and control other containers, you need to be EXTRA SURE that it’s reputable.