Its not for you, its for spammers…

I remember you, how did you go with your raspi project? Looking forward to your updates!

/etc/passwd: you may be able to get to this from the GUI file manager.

If not, open a terminal and type: cat /etc/passwd. Copy the relevant lines.

To test the login, from a terminal, type su otheruser, replace otheruser with the username from /etc/passwd. It should ask for a password, put that in and it should log you in. Type whoami and make sure its the same username as you expected. Paste any errors here.

“Group policy me harder, babe”

I think that was meant to be a reply to me, so I’ll respond.

Technically, /etc/passwd can have encrypted passwords in it, but as far as I’m aware, no distro has done that in decades, so realistically its not that risky. It does expose the user names though.

Can you share the lines from /etc/passwd for your user and the user your adding? Despite its name, there are no passwords here, that is in /etc/shadow

Edit: can you su to login as the user?

Don’t windows-shame me!

I prefer to think of it as an open relationship. I have my home distro, my work distro, and if either of them aren’t in the mood, there is an wide variety of other distros to get the job done.

And if I’m feeling really kinky, there’s always Windows.

I think it perfectly highlights what can happen when the risk/severity is blown out of proportion. People will latch on to that and waste precious time and energy defending that.

If the original guy had just published “CUPS has a RCE, firewall it if you haven’t already”, the issue would have been patched in the next release, and the world would have kept turning.

It was a really cool bug, and a great find, it didn’t need the hype

Didn’t know that, but makes sense.

if you are from Russia, it is impossible to convince the US that you are not a part of a state-sponsored entity

This quote from your article does nail the problem on the head though.

Excellent, thanks for the update!

Russians can still contribute, they just can’t be direct maintainers.

Nothing will likely change in the short term.

Can you make your docker service start after the NFS Mount to rule that out?

A restart policy only takes effect after a container starts successfully. In this case, starting successfully means that the container is up for at least 10 seconds and Docker has started monitoring it. This prevents a container which doesn’t start at all from going into a restart loop.

https://docs.docker.com/engine/containers/start-containers-automatically/#restart-policy-details

If your containers are crashing before the 10 timeout, then they won’t restart.

https://roundthetwist.fandom.com/wiki/The_Cabbage_Patch_Fib

His wife was a little less impressed /s

Hans Reiser was convicted of murdering his wife. He is (was?) in jail.

Edit: https://en.m.wikipedia.org/wiki/Hans_Reiser

Not a direct answer, because I don’t know of anything like that, but can you make your cursor a cross hair, so its symetrical and transparent near the middle?

Something like: https://www.gnome-look.org/p/1964585

Linux distros are getting mature

I think this is exactly it. Back in the early days of Fedora and Ubuntu a new release often meant major bug fixes, new software, and possibly a significant qol/usability changes and performance changes. Now, its all new versions of stable software, which all behave roughly the same. Which is exactly what you want in a daily driver OS. Stability.

Thats for proving its untampered with right? I’m more thinking of validating the archive copy is a “true” copy when adding it initially, which requires each node to check against the live site?

Its definitely an intriguing idea though, but I don’t know enough to know how feasable it can be

I figured that every node would need to scrap the site, in order to validate the content. If there are thousands of nodes, that would ddos the site.

I don’t really understand how PoW would solve that, can you explain?