No, I think it’s saying that opensuse breeds Linux distros, and is trying to get Debian and arch to rub cloacas.

Also, opensuse once bit off a little chunk of someone’s ear.

Okay. You’re still doing tech support either way. I have no way of knowing how much free tech support you’re willing to give, hence my caveat of how much you’re willing to support them.

Netflix would disagree. People feel like they’re supposed to be getting access to a service, and if they’re not getting it they’ll complain to the nearest party to what isn’t working. In this case that’s you or Netflix being asked questions about why the router isn’t working.
That it’s wrong or irrational has nothing to do with who’s getting asked the question, and who’s the first line of troubleshooting when the service doesn’t work.

If people didn’t ask the wrong people questions, Netflix wouldn’t need support articles on how to reset your router.

Honestly, you’re supporting a chunk of her network by being a media provider in the first place. “It won’t play” doesn’t usually come with an assurance that it’s not a device or network issue.

Neither plex nor jellyfin seem remotely worth the effort to provide to others in my opinion, I just felt like sharing that there are ways to afford network protection to locked down devices.

I’ve got no real care for jellyfin one way or another, just sharing that there’s ways to make the network obey.

I think giving people access to my media server is asking for too much trouble personally. Now you’re dealing with forgotten passwords, people using your bandwidth at weird hours, and you basically become the media fairy, responsible for finding whatever it is people want, and then dealing with their issues when their device can’t codec at it for whatever janky reason.

I’m good at setting boundaries with family so it’s not stressful, just more annoying than I want to deal with.

Depending on their router and how much IT labor you care to do for these people you can actually configure a site to site VPN tunnel. All traffic for a particular address range will get routed through the VPN automatically.

It used to be a high end feature but it’s made it’s way into general routers since it doesn’t really require many resources and it lets you label it as having more home office features.

Walk me through that analogy, and what point you’re trying to make. My hammer doesn’t typically have unexpected interactions with things I’m not hammering. When I build a bookshelf, I don’t have to make sure my desk is clean to keep people I let borrow books from unlocking my front door without a key.

Do you think that improper setuid isn’t a common enough vulnerability to have a name and designation?

What constitutes a security nightmare if not something that requires a large and annoying amount of work, and can be made insecure by a mistake somewhere else?

I would describe need to proactively go out of your way to ensure a program is simple, minimal, and carefully constructed to avoid interactions potentially outside of a restricted security scope as a “security nightmare”.

Being possible to do right or being necessary in some cases at the moment doesn’t erase the downsides.

It’s the opposite of secure by default. It throws the door wide open and leaves it to the developer and distro maintainer to make sure there’s nothing dangerous in the room and that only the right doors are opened. Since these are usually not coordinated, it’s entirely possible for a change or oversight by the developer to open a hole in multiple distros.
In a less nightmarish system a program starting to do something it wasn’t before that should be restricted is for the user to get denied, not for it to fail open.

https://www.cve.org/CVERecord/SearchResults?query=Setuid

It may be possible, but it’s got the hallmarks of a nightmare too.