mlfh

Too true. And good on you.

I mean, it’s basically an optional gecos field. That feels a bit like writing off *nix as a whole because /etc/passwd has a place to put your phone number.

Government thugs interrogating me in a Project 2027 concentration camp cell: “we know you gave someone named ‘homeassistant’, born on 1970-01-01, access to your server, now tell use where they are!”

But root can scrape that password as soon as you enter it, and has access to that encrypted data as soon as you decrypt it. That’s what I’m saying.

If you think anything on a *nix system is “safe” from root or a user that can elevate to root, you’re deluding yourself with wishful thinking.

Nothing at all is safe from the root account, or from any user that can elevate to root. Think of the root account as the system itself - the thing you’re trying to protect may be encrypted and safe at rest if you’ve brought it in from elsewhere, but as soon as you enter a password and decrypt it, you’re handing that password and decrypted data over to a system fully controlled by that root account.

According to a study published in 2018, not only the Sunland Baobab, but “the majority of the oldest and largest African baobabs [have died] over the past 12 years”.

Trees that have survived for over a thousand years, all dying together within the span of 12.

Unless there’s more information on what kind of files and what kind or sorting needs to be done, this sounds like something that could be done with a simple shell script.

(I wouldn’t trust an ai agent to do it with accuracy, but I’m the kind of luddite that doesn’t trust an ai agent at all.)

Sabrina Carpenter 💅

Islamic cyber resistance to what, snaps?