A very good article. I have to disagree with the part about the DRM though:
>Untrue. The argument here is that Secure Boot can be used to restrict the software that a machine can run, and so can limit a system to running code that implements effective copy protection mechanisms.
An operating system is software, too. Secure boot, if it's impossible to disable (which isn't mandatory, but possible) can be used to restrict what software you can run (boot) on your computer. That's pretty much the textbook definition of Digital Restrictions Mismanagement.
In order for it to be any sort of copy protection mechanism it needs to be possible for the OS to guarantee that secure boot was used. It's not. That means the OS can't rely on the hardware being in any known-good state.
3 comments
[ 2.5 ms ] story [ 15.1 ms ] threadGod says... 32:19 Behold, my belly is as wine which hath no vent; it is ready to burst like new bottles.
32:20 I will speak, that I may be refreshed: I will open my lips and answer.
32:21 Let me not, I pray you, accept any man's person, neither let me give flattering titles unto man.
32:22 For I know not to give flattering titles; in so doing my maker would soon take me away.
33:1 Wherefore, Job, I pray thee, hear my speeches, and hearken to all my words.
>Untrue. The argument here is that Secure Boot can be used to restrict the software that a machine can run, and so can limit a system to running code that implements effective copy protection mechanisms.
An operating system is software, too. Secure boot, if it's impossible to disable (which isn't mandatory, but possible) can be used to restrict what software you can run (boot) on your computer. That's pretty much the textbook definition of Digital Restrictions Mismanagement.