Linked by Thom Holwerda on Mon 4th Feb 2013 22:10 UTC
Thread beginning with comment 551573
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[3]: Do Microsoft Respond Like This?
by mjg59 on Tue 5th Feb 2013 22:00
in reply to "RE[2]: Do Microsoft Respond Like This?"
The FSF agree that this is a worthwhile freedom. It shouldn't be possible for any vendor to have more control over a system than you - that means that if the vendor can limit which software the system will run, you should also have that ability. The laptop I'm currently using gives me that ability. A Chromebook doesn't.
But still, let's find out how willing Microsoft are to enforce this. Find an example of a machine that doesn't let you install your own keys and I'll make sure Microsoft know about it, then we'll see what happens from there.
RE[4]: Do Microsoft Respond Like This?
by segedunum on Tue 5th Feb 2013 22:10
in reply to "RE[3]: Do Microsoft Respond Like This?"
The FSF agree that this is a worthwhile freedom. It shouldn't be possible for any vendor to have more control over a system than you - that means that if the vendor can limit which software the system will run, you should also have that ability.
I'm curious that you're painting it this way, as others are.
When you're having to get yourself key-signed by Microsoft I find that statement rather laughable to be perfectly honest. I think you'll find the FSF does not agree with you that everything is absolutely fine.
Find an example of a machine that doesn't let you install your own keys and I'll make sure Microsoft know about it, then we'll see what happens from there.
Hmmmmmmm.
Edited 2013-02-05 22:12 UTC




Member since:
2005-07-06
No, they don't. That is purely at the behest of the hardware manufacturer and you've provided nothing to back up that Microsoft will enforce this in any way. Stop repeating this crap.
You will be reporting on manufacturers not implementing modifiable key systems in no time, mark my words. The only reason you can disable Secure Boot now is because of the bootable software that users and companies still need to be able to run on current hardware.
That's a curious way of putting freedom and a very curious way of painting what Microsoft is doing with this.
Edited 2013-02-05 21:55 UTC