5 ms·

Smh, the FUD is suffocating in here. And really, a round of applause for everyone butting into say they don't need this. Do you have a habit of doing this for a

Smh, the FUD is suffocating in here. And really, a round of applause for everyone butting into say they don't need this. Do you have a habit of doing this for all features? Sorry, but I expect my Linux install to be at least as secure as my Windows (Pro) installation. And without this, it's not. It's that simple. In years, most of you will be benefiting from this, it will become table stakes and the FUD will subside. It's hard to really read this thread. If you care about user freedom, this sure ain't got nothing to do with it. Other than giving me the freedom to have a more secure computer. Just sad to see the FUD cause people to just get so activated without even understanding the stakes at hand. (Think. It's not like MS is watching this feature to decide whether or not to allow user-key-enrollment on the ARM Surface).

bayindirh 4y ago
I just don’t trust a company and its employees which actively tried to kill Linux back in the day. Adding the fact that said company is designer, enforcer and gatekeeper of such technology makes everything more worrisome. Lastly, telling that people are spreading FUD against the company which defined and is synonymous with FUD is ironic. That’s all, Thank you.
- stoplying1 4y ago
  Great, thats cool. I'm concerned about accessibility to general computing too. But this article is about an optional feature in an FOSS software that is only as good or bad as the distro using it. Please, you must understand, you devalue your point by demonstrating that you either don't understand the layering at play here, and where the real risks are, or you don't care to advocate in any sort of meaningful or compelling way. Instead, you just repeated FUD and waved your arms more. Again, about something we probably agree about, but is simply not at hand here. I mean the issue that you're worried about? How about the millions of capable smartphones being tossed because of closed bootloaders? Android manufacturers, Google's Nest and Chromecast products, and Apple's iOS devices here are far greater offenders. And just more insidious. My 3 year old phone that works damn fine is considered literal garbage by Google (no security updates, means I use Lineage, means I can't bank, watch Netflix, use credit card apps, and more). Microsoft has never used security features to invalidate my old hardware. Ever. Again, totally tangential from whether or not SystemD has first-rate support for this (mostly because at this point it's about UX and distro mechanics such that users and distros can freely secure their computers. The functionality to just lock-er-down has been here. For a decade). This issue is about capitalism, economic incentives, social politics, etc. But, I don't expect that conversation to play out on this site much. Finally, Pixel and Chromebook prove that secure computing AND user freedom CAN be respected and can be user-empowering. Please, if you care, advocate for their models. (Which, again, I can also do on all x86 Microsoft devices and Microsoft Surface ARM, at least, today).

bayindirh 4y ago

I just don’t trust a company and its employees which actively tried to kill Linux back in the day. Adding the fact that said company is designer, enforcer and gatekeeper of such technology makes everything more worrisome. Lastly, telling that people are spreading FUD against the company which defined and is synonymous with FUD is ironic. That’s all, Thank you.

stoplying1 4y ago
Great, thats cool. I'm concerned about accessibility to general computing too. But this article is about an optional feature in an FOSS software that is only as good or bad as the distro using it. Please, you must understand, you devalue your point by demonstrating that you either don't understand the layering at play here, and where the real risks are, or you don't care to advocate in any sort of meaningful or compelling way. Instead, you just repeated FUD and waved your arms more. Again, about something we probably agree about, but is simply not at hand here. I mean the issue that you're worried about? How about the millions of capable smartphones being tossed because of closed bootloaders? Android manufacturers, Google's Nest and Chromecast products, and Apple's iOS devices here are far greater offenders. And just more insidious. My 3 year old phone that works damn fine is considered literal garbage by Google (no security updates, means I use Lineage, means I can't bank, watch Netflix, use credit card apps, and more). Microsoft has never used security features to invalidate my old hardware. Ever. Again, totally tangential from whether or not SystemD has first-rate support for this (mostly because at this point it's about UX and distro mechanics such that users and distros can freely secure their computers. The functionality to just lock-er-down has been here. For a decade). This issue is about capitalism, economic incentives, social politics, etc. But, I don't expect that conversation to play out on this site much. Finally, Pixel and Chromebook prove that secure computing AND user freedom CAN be respected and can be user-empowering. Please, if you care, advocate for their models. (Which, again, I can also do on all x86 Microsoft devices and Microsoft Surface ARM, at least, today).