https://wiki.archlinux.org/title/GRUB

Then make sure your CMOS has the Arch drive as the first boot target.

Never had a problem with it. Perhaps people are complaining about the lack of features the proprietary Logitech software provides? I never needed it anyway, so I say mine works perfectly.

Yes, that’s the same thing. Removing it from one place, and just adding it to another. No big deal.

I honestly don’t think many people were even using this feature compared to SSL certs. Anyone using TLS everywhere already has their own cert manager workflow, othey’d be using another system to do it ala k8s, or they’d be doing it at the network fabric instead of per-service. I can’t think of many use-cases where regular users of LE would have a TLS-enabled public service they would need other random users to trust. I’m sure there’s some, but nowhere on the scale of their SSL users.

The PKI in this context is just the platform that is managing the issuing and revocation of certificates not the underlying algorithms being used, if that’s what you’re asking.

So the LE systems that accept, check, and approve the initial request, and then handle the revocation when needed. Using a different stack for different use-cases is a best practice, simply because if one is compromised, it doesn’t affect the other. In this case it’s just splitting the standard LE web services and TLD services into two different stacks that do the same thing, but I assume would have isolated CAs, one for each use-case. This would mean a new root CA needs to be deployed out into the world in order to verify the TLS side, but maybe I’m missing something.

How do you mean?

This honestly is basic security in a number of ways. Separate PKI for every use-case is the standard. Eggs in on ebasket, yadablahwut.

The actual change shouldn’t take long for LE to actually do, it’s the implication of the thing though. I’d love to see a different tool for enrolling TLS services, or at least a better flow than the existing one.

https://docs.fedoraproject.org/en-US/quick-docs/selinux-troubleshooting/#_selinux_denials_in_the_audit_log

An error would be awesome.

You can have your WiFi start with the rest of your network service before login if you choose. Maybe that’s the limitation here.

Random new Linux distro from China with zero history or contributions from any FOSS devs?

Nawthx