Hi.
I'm actually amazed how many people comment without having a clue what they are talking about.
What you're describing is not an issue but the fix of an issue ๐
When the kernel boots with the parameter quiet, systemd should get the option systemd.show_status=auto. With this option it should only inform about failures and such like. In current releases this finally works.
To get the old behaviour you just have to add systemd.show_status=true to your kernel parameters.
It's not that difficult to build your own kernel based on the official debian one: https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html#s-common-official
Before clicking the link I thought there was a new restic clone/fork out there...
Did the same in python. Ages ago. And again in python half a decade ago. And again in python a few months ago.
Never repeat anything.
They are still developing and selling Sailfish OS. They just stopped making their own hardware.
Well it's not completely useless. It offers some insights into the system. Which service accounts exists, what usernames are used.
If an attacker finds a valid username they can then start bruteforcing the password.
From your account list we can see you have sshd and xrdp. Do they both provide the same kind of bruteforce protection? Are there any recent exploits for either?
Yes you could, but (and it's a big but): performance will be bad, performance for all other TOR users will be impeded, you won't be able to open an incoming port, it'll be a bad experience for everyone.
Additionally it's quite easy to leak identifiable info in such a setup.
https://blog.torproject.org/bittorrent-over-tor-isnt-good-idea/
Berlin, Germany: we drink water straight from the tap. It's free and delicious. If you don't feel like drinking tap, just drink a "Berliner Rohrperle". It's the same thing with a fancier name, because our tap water is awesome.
Nowadays we even have public drinking fountains dotted around the city.
Yeah that gets turned into a phone link
Yes it has. But it's still working fine for me.
There are some forks that might be better, but since I don't experience too much issues I never looked for alternatives.
Yes that's the recommended path.
Information on how to upgrade can be found in the official documentation:
https://www.debian.org/releases/stretch/amd64/release-notes/ch-upgrading.html
https://www.debian.org/releases/buster/amd64/release-notes/ch-upgrading.html
https://www.debian.org/releases/bullseye/amd64/release-notes/ch-upgrading.html
https://www.debian.org/releases/bookworm/amd64/release-notes/ch-upgrading.html
As others pointed out it might be a PITA. Depending on your installed software and configuration a new install might be easier.