Never expose the bare remote control endpoint publicly. For example, recently macOS had a critical vulnerability where an attacker could completely bypass authentication on their Screen Sharing daemon, and the researcher had estimates around 40k publicly exposed systems, and it was found out that the vulnerability was in fact being used in the wild. Exposing things like that publicly is asking for trouble.

Personally I don’t like relying on 3rd party systems like Tailscale, so I just have a WireGuard peer running firewalled to only allow access to what is necessary, though you can skip the firewall part. This obviously assumes you have a routable public IP, i.e. no CGNAT, if that’s not the case Tailscale is probably what you want.

If we take the EFF wordlist commonly used to generate passphrases, we have 7776 words. If we take ASCII alphanumerics and special characters we have about 92. Assuming we generate a NIST compliant password of 15 characters in length we get 92^15=2.8*10^29 of combinations. To get the same level of security (same number of combinations) using the EFF wordlist we need (log(2.8)+29)/log(7776)=29.45/3.9=7.6 around 8 words. If we assume the words are 7 characters long on average, plus the separators, we get 7*8+6=62 characters long. If we start to also include Unicode characters like other scripts or emojis (something I’ve recommended to others) the required number of words grows even more. I don’t know about you, but I can’t be bothered to type that all out every time, a password manager works for me.

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.

I mean, nobody’s forcing you to update them every day, and you can always schedule it off hours.

I mean, nobody’s forcing you to update them every day, and you can always schedule it off hours.

Yep, don’t forget to seed!

AppImage may be up-to-date now, but it has no self update mechanism, so a Flatpak is a better choice IMO

I was never much of a social person, have barely used Reddit, I just randomly felt trying lemmy to see if it’s any less toxic than Phoronix 😂

Mine didn’t die, but it’s Ryzen gen 1 which is not supported by Windows 11 so Cachy it is.

Yes, though slight caveats: Mint has 2 branches, 1 based on Ubuntu, as you said, but the other one based on Debian skipping Ubuntu actually, since there are a lot of things they are dissatisfied with Ubuntu, and one among them are snaps, so if you see anything regarding snaps when searching Ubuntu threads, disregard them completely.

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?

ZSTD and BYRFS, among many other smaller things, hello?

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:

1. For full functionality, snap requires Ubuntu specific kernel patches, and has a hard dependence on Systemd, whereas Flatpaks work everywhere.
2. Most Flatpak users default to the flarhub repo, however, just like you can have other apt sources, Flatpak supports other repos. Snaps on the other hand are exclusively tied to and controlled by Canonical, which seems very unlike Unix and rubs many wrong.
3. You can install packages as a non-root user into your home with Flatpaks, but snaps can only be managed by root, since they are system packages. This means that they are very unsuitable for atomic distros like Fedora Silverblue.
4. Technically not the fault of snaps but the decision by Canonical, when you try to install something with apt on Ubuntu (and derived) it may instead install it through snap, which, because of sandboxing and other security measures, may result in very unexpected and hard to diagnose issues. I personally wasted a day trying to fix a broken Docker daemon, which turned out to be due to snap, when I explicitly wanted an apt! I personally have no major issues with snaps in general, but ffs let me decide whether it’s a snap or not >_<

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.