![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://fry.gs/pictrs/image/c6832070-8625-4688-b9e5-5d519541e092.png)
deleted by creator
deleted by creator
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.
The “down” was definitely edited after the fact.
Thanks! Not quite as wild as I was expecting (kind of surprised this was enough to push them to delete their account)
Do you have any sources for this?
The GitHub says they plan on adding other fediverse connections in the future.
Where can you find an N100 for $60 with 4GB of memory?
EDIT: Nvm, found the comment replying to this mentioning Radxa boards. Just found them the other day. Very interested.
Aren’t most CPU’s and chipsets proprietary? Not to mention all of the firmware blobs they require? What are some affordable, non-proprietary options?
Doesn’t Kate have its own theme options?
As a user of Debian and Arch: I don’t know how to feel
Thanks for the link! I was trying to figure out the Lunduke complaints (I don’t know if I’ve ever heard of this guy before). This video did a solid job of catching me up.
You’re the one who replied “any google hardware” though.
You didn’t mention rsync, which I think is usually considered standard. I’d look into that.
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.