Fifteen Million Merits, IIRC?

I found a blog post outlining exactly that. If you use it locally, it will install and start a service temporarily. That service runs as SYSTEM and invokes your command. To succeed, you need to be a local administrator.

If you try the same remote, it tries to access \\remote-server-ip\$admin and installs the service with that. To succeed your current account on your local machine must exist on the remote machine and must be an administrator there.

So in short: It only works, if you’ve already the privilege to do so and the tool itself is not (ab)using a privilege escalation or something like that. Any hacker and virus may do the very same and doesn’t need psexec - it’s just easier for them to use that tool.

Never thought about that, but since these tools just work, when you copy them to your PC… how does psexec do that? It’d either need you to be an administrator (and then it’s not really a privilege escalation as you could have registered any program into the task scheduler or as a service to run as SYSTEM) or it’d need a delegate service, that should only be available when you use an installer - which again wasn’t was has been done when just copying the tool.

Also please pre-install the sysinternals suite, thanks

Can’t decide which one is more relevant - the $5 wrench hack, or any sort of blackmailing.

XKCD 538 - Security

XKCD 416 - Zealous Autoconfig

It’s not the most detailed thing, but I just use a free account on cron-job.org to send a head request every two minutes to a few services that are reachable from the internet (either just their homepage or some ping endpoint in the API) and then used the status page functionality to have a simple second status page on a third party server.

You can do a bit more on their paid tier, but so far I didn’t need that.

On the other hand, you could try if a free tier/cheap small vps on one of the many cloud providers is sufficient for an uptime Kuma installation. Just don’t use the same cloud provider as all other of your services run in.

First actual case of bug being found

Maybe, but knowing the ease of sudo, I really hate using runas. Most of the time, I just want plain old admin privileges. Mostly I don’t care whether I can impersonate another user with this.

Also it’s just wrong advice, since you explicitly need --no-preserve-root for it to work… /s

Jokes aside, please don’t troll anyone with things, that can have severe consequences. Yes, they should have a backup. Yes, they should know how to restore from it. Yes, they should have tested it prior. Yes, you shouldn’t blindly trust people online.

But even then: Assuming my backup works and I can easily revert the damage. Maybe I need to complete an assignment until tomorrow and just lost 1-2 hours because my PC was busy doing the restore? There’s always a high chance of collateral damage

Docker evolved into Podman! Podman forgot daemon and learned rootless!

Yeah, but in case I’m on a server, I’m going to free all the other trapped users, too! (Although I’d probably just terminate the ssh session then)

Help, how do I exit vi?

Ctrl+Alt+F2
sudo killall vim

Hmmm… never thought about that, honestly, but it makes sense