Yep, there’s a reason 2FA recovery keys are usually printed and stored safely.
With that said, one way to avoid someone compromising service A due to somebody breaking into service B is to have different passwords everywhere, so a Password Manager is more convenient anyway.
The way a reverse proxy works is to literally stand in the middle of a connection, so either side only sees them communicating with the proxy, oblivious to the actual endpoint. The only “solution” to this, though it’s more of a hack really, is to somehow send the original IP as additional data in a way that both sides agree on, e.g. the X-Forwarded-For header as others have mentioned, however, as I’ve said, both sides need to support and aggree with that, so you may have to find a setting/config to enable on the services behind the proxy. Think of it this way, if services blindly trusted that header and you weren’t using a reverse proxy, a bad actor could send a request to your service with that header included thereby spoofing their identity in your logs, therefore, this kind of thing is usually opt-in
The removed drivers are usually those that are really old and not used by anybody (using the latest kernel), so it’s a bit different.
Yep, don’t forget to seed!
Yeah, but I thought the philosophy was not to break userspace. I’m fine with the removal if absolutely nobody uses it, but some have commented here being users of the feature
Ah, I see! From googling “data=ordered” is the default and does what you said. Still, why not leave it for those that want it?
Wasn’t the journal the main selling point in the transition from EXT2 to EXT3? This seems kinda backwards, what even is the rational?
Fir desktop use I personally think Fedora has the best balance between stability and being up-to-date, while staying fairly easy to use and with a large community. If the person wants something even harder to break and doesn’t mind a bit of an extra learning curve, atomic variants like Silverblue are alo a nice pick. My cousin went for Silverblue and loved it.
From what I’ve seen, there are 4 core issues people complain with snaps:
Bonus: Some also complain about security, that snaps have had many vulnerabilities, and that malware was distributed as snaps, but the same has been true for Flatpaks too, so I don’t think it’s fair to point that out.
Yeah, that and avoid very new things when using Linux are the morals of my story. But I can’t help it, I am a human and hate all Thinkpads now :P
The laptop BIOS did see updates and now works fine running Cachy, but for over a year it was terible. A whole list of cryptic kerner boot arguments would make it boot, but then touchpad and keyboard issues would remain, and if it ever went to sleep it would hard lock again, not ideal on a laptop. I personally didn’t contact support, but on the official forum there was a thread with a tonne of comments about how support would say Linux is not officially supported on this model and people giving up and returning it. I couldn’t because I ordered from overseas, specifically because I heard Thinkpads worked great with Linux. Needless to say I was royally disappointed. At least it works now, and works better than with Windows.
At least at launch it was a total mess, Linux would instantly hard freeze at boot time. They did eventually release BIOS updates that fixed them more than a year later, so mine is currently running Cachy, but just google for E484/E585 Linux issues, there’s a tonne of people complaining back in the day, and I was one of those early birds >_<
From what I remember, there was a similar-ish laptop a tier above which had received a BIOS update pretty fast, but even though the symptops were pretty much the same, Lenovo dragged their feet on this one.
The model is important! I had gotten an E series Ryzen gen 1 years ago and the Linux support on it was atrocious! I swore to never buy a Thinkpad again.
This year alone I had to reinstall 3 Windows systems that were failing to work. Then again, my Windows 11 work laptop also seems to work just fine.
For home Wi-Fi I use a strong password, but that’s because it’s something I input once in a blue moon. For guests I have a guest Wi-Fi with a simpler* (still reasonably secure and random, but shorter and without special characters) password and a QR code for simple use, though they are rate limited and have no access to any other network clients.