You can say that speaks volumes about the character of the author (though you are the one assigning said “shame”). You were asking why this report deserves credence. The points raised in the report have citations such that you can decide where you fall on the presented issues.

It looks pretty well cited to me. The fact that it was written anonymously doesn’t really take away from that.

90% sure wireguard (the VPN server) is going to need an open port if you want to connect from the outside.

FWIW: I’m running jellyfin and a whole host of other services on a Beelink with an Intel n95 and 8gb of ram. Runs like a champ.

Using Firefox mobile, everything works and is mostly performance 🤷‍♂️

You’re going to connect to the seedbox at some point, which ties your IP to the traffic. If you are worried about a VPN attaching your IP to traffic, this is no different, no?

If you are worried about VPN’s, why are you not worried about seedbox providers?

The OP ruled out zig and rust already

Right, that’s what I meant when I said “third party app”. Samsung can write an app to do this, but your average app installed from the play store likely cannot.

I’m not super well versed in the world of app development, but I would assume due to the way apps are sandboxed, this isn’t something that could be done with a third party app.

I know it’s of very little help, but I have not seen this issue, and I’ve been using Deluge for years (not automated via the arr suite, however)

It would do you well to find out what error it is throwing (check logs). Would be much easier to diagnose if you knew the actual issue.

im a big fan of the nas device being single purpose. its life should only exist in fileserving. i have several redundant nas devices and then a big ol app server.

This is the way. Except my “big ol’ app server” is an n95 mini pc that sips power.

Because even if an attacker could gain access even as root he cannot modify system files.

Your comment was already from the position of if an attacker could gain root access. My responses were to that directly, and nothing else.

Your comment also contained

The filesystem itself is also read-only.

Which is what led to the further discussion of root making that not so.

I don’t believe that to be the intent of the OP’s comment, given their second sentence, but they are welcome to state otherwise. I just don’t want them thinking that an immutable distribution gives them some kind of bulletproof security that it doesn’t.

While you are correct, any system is compromised if you have root, so isn’t that irrelevant at that point?

The original context for the comment chain was:

Because even if an attacker could gain access even as root he cannot modify system files.

So no, it’s completely relevant.

Someone with root can run ostree admin unlock --hotfix to make /usr writable. Someone with root can also delete all restore points.

It would be strange for them to call it that if it actually means “completely irrelevant from a security perspective”.

See the comment by superkret.

An attacker escaping from a container can’t be system root as Podman runs rootless (without some other exploit or weak password).

That would be true of podman running anywhere, and is not unique to an immutable distribution.

The filesystem itself is also read-only.

You can change that real quick if you have root access.

Because even if an attacker could gain access even as root he cannot modify system files.

They 100% can.

I really appreciate Open Source Alternative To for this (although their theme seems a little broken atm).

The GitHub says they plan on adding other fediverse connections in the future.