3 ms·
How much will this break Linux? Will we ever recover? Here are the problems I can already smell from this: - SSH not working - Forced encryption, which will s
by dsign 6y ago
How much will this break Linux? Will we ever recover? Here are the problems I can already smell from this:
- SSH not working
- Forced encryption, which will slow useful I/O work like compiling a project to a crawl. Admittedly it says somewhere else that encryption will be optional, but we have seen "secure by default" and patches like specter botch the performance of computers where performance is at a premium. If opting out becomes a PITA, it will cost billions of hours of collective time, as another commenter suggested.
- UID mappings. There are decades of code, systems and services built around the status quo. The container images that I use to develop projects in my home folder may not work anymore.
- Mental effort. Now `/home/user` won't simply be a folder, but a mount. Anything under `/home/user` that needs to be mounted somewhere else may or may not work. Or may work part of the time, provided that one understands all the nitty-gritty details of the mount mechanism and the mount order.
- oehtXRwMkIs 6y agoA big chunk of the article talks about SSH. Encryption does not dramatically slow IO, especially with transparent compression in btrfs for example. In my case on a r5 3600 and Arch Linux it has negligible effect.