Re:Support the FSF: Help us stop Restricted Boot
by JoshTriplett on Saturday December 29, 2012 @10:39AM
(#4982331)
While the name "Secure Boot" seems like horribly misleading doublespeak, this still seems like a case where giving something a more descriptive name results in less effective communication. Calling it 'UEFI "Secure" Boot' would have sufficed, along with describing it as "restricted boot", but attempting to rebrand it seems like an ineffective and actively harmful marketing tactic here.
[ Parent
| on HN ]
Re:Support the FSF: Help us stop Restricted Boot
by Karunamon on Saturday December 29, 2012 @12:51PM
(#4982762)
They're only trying to redefine the label to fit what the software actually does. A strong argument could be made that the name as commonly accepted is a misnomer considering what the endgame is.
Digital "rights" management is not about your rights, it's about restricting you from doing what you want with your content. Hence the R in DRM now means "restriction".
Same concept here.
Re:Support the FSF: Help us stop Restricted Boot
by JoshTriplett on Saturday December 29, 2012 @01:02PM
(#4982800)
I agree with you entirely that the generally recognized name doesn't fit; however, I still think it seems counterproductive to attempt to rebrand it.
"Digital Restrictions Management" worked better, because it still abbreviates as DRM so nobody goes "huh?" when you say it. "Restricted Boot" needs an accompanying explanation to tie it to the official name of 'UEFI "Secure" Boot', which makes the attempted rebranding counterproductive.