|
|
|
| Authored by: JamesK on Tuesday, July 10 2012 @ 04:29 PM EDT |
"Secure Boot is intended to prevent malware from running before the
operating system has booted."
Years ago, when I used and worked with OS/2, one point was that an OS/2 system
could only be infected by a boot sector virus and then only if the computer had
been booted from an infected floppy. On the other hand, Windows could easily be
infected with a variety of viruses by a variety of methods. Just how is this
malware supposed to get on the system to be bootable in the first place?
Certainly Windows wouldn't allow such a thing. ;-)
---
The following program contains immature subject matter. Viewer discretion is
advised.[ Reply to This | Parent | # ]
|
| |
| Authored by: dio gratia on Tuesday, July 10 2012 @ 07:51 PM EDT |
The requirement the adminstrator and user passwords be set before enabling
Secure Boot runs contrary to Microsoft's requirement that securemode='1' be set
as a requirement for client platform delivery. Someone would have to set those
passwords already and set secure boot mode before loading Windows 8 (and one
could imagine the restore imagine Windows RE).
You'd be dependent on the vendor for supplying the administrator password to
allow you to turn off secure mode or change the user password. And if they some
default value, the security added by the process is minimal to non-existent.
[ Reply to This | Parent | # ]
|
|
|
|
|
