Skip Navigation

Posts
3
Comments
255
Joined
2 yr. ago

  • I don't know if I agree. I get it, but it's kind of important that people know that if they do something weird with a piece of software, that it might expose them to remote code execution or root shell exploits. It certainly does make you numb to the word "critical", but I don't have a solution to that.

  • Many exploits and vulnerabilities are not relevant within the scope the software is typically deployed, so remain unfixed for a long time, even if they are rated high severity.

  • Some users are not worth having.

  • Respectfully, you have no idea how Matrix works and I know you don't use it if you think you have to tell people what backend you use for them to connect to you.

  • If the fucking name of a project is the reason you won't use it, then by all means, don't. We're not missing you.

  • xd

  • Nope, but people are defensive of their financial decisions.

  • What is that picture? The blogpost doesn't elaborate on it...

  • It isn't possible to switch non-destructively.

  • I don't care what other phones do.

  • I'm throwing my phone into the sea the moment it tells me I'm not allowed to do something.

  • /c/selfhosted moment

    Sure don't patch a quiet and easy root shell escalation because it is, by itself, not a remote exploit. I sure do hope you trust every single piece of software running on your computer.

  • What do you mean? If you use Linux on your computer, it's also relevant. Any program can quietly drop a root shell from any privilege level in 10 lines of python.

  • Friend has a cat with 0 teeth left who has no issues inhaling solid food. Some cats do not care and will go beast mode on any food presented to them!

  • AI promoter blog

  • me when i just say shit

  • nano todo