Salutations...
More reasons to deprecate Unified Extensible Firmware Interface (UEFI) and BIOS in favor of Coreboot ...
http://techreport.com/news/28728/wake-f ... -to-attack
http://www.uefi.org/sites/default/files ... hoenix.pdf
http://www.intelsecurity.com/resources/ ... overed.pdf
"Best Regards"...
Posted by 73.150.85.78 via http://webwarper.net
This is added while posting a message to avoid misusing the service
[Solved] Secure Boot Attacks (UEFI/BIOS)
[Solved] Secure Boot Attacks (UEFI/BIOS)
Last edited by fullmoonremix on 15 May 2016, 00:14, edited 2 times in total.
-
- Samurai
- Posts: 134
- Joined: 18 Sep 2012, 20:56
- Distribution: Porteus 64bit KDE4
- Location: Absurdistan
Re: [Solved] Secure Boot Attacks (UEFI/BIOS)
Do i have right understand that the main differenz at security beetween old BIOS and UEFI are:
The BIOS loads the different firmwares into the RAM and giving the Storage-Addresses to the OS.
After them the BIOS stops.
The UEFI loads the different firmwares into the RAM and using the firmware self to provide a Interface: the Unified Extensible Firmware Interface.
After them the UEFI do not stop.
(If i have a full paranoid, high secure OS where i have read each codeline and have self compiled,
them the UEFI can do nevertheless what they programmer of the UEFI want do to with my PC)
Is this correct ?
how does the Compatibility Support Module (CSM) work ?
The BIOS loads the different firmwares into the RAM and giving the Storage-Addresses to the OS.
After them the BIOS stops.
The UEFI loads the different firmwares into the RAM and using the firmware self to provide a Interface: the Unified Extensible Firmware Interface.
After them the UEFI do not stop.
(If i have a full paranoid, high secure OS where i have read each codeline and have self compiled,
them the UEFI can do nevertheless what they programmer of the UEFI want do to with my PC)
Is this correct ?
how does the Compatibility Support Module (CSM) work ?
Re: [Solved] Secure Boot Attacks (UEFI/BIOS)
Salutations...
BIOS = "old school"... Unified Extensible Firmware Interface ... aka. "UEFI" (Intel/WindozzZ?) = "new school"?
Both can be hacked (ie. firmware bug)... Coreboot cannot be hacked (yet?).
http://techreport.com/news/28728/wake-f ... -to-attack
http://www.uefi.org/sites/default/files ... hoenix.pdf
http://www.intelsecurity.com/resources/ ... overed.pdf
"Best Regards"...
Posted by 73.150.85.78 via http://webwarper.net
This is added while posting a message to avoid misusing the service
BIOS = "old school"... Unified Extensible Firmware Interface ... aka. "UEFI" (Intel/WindozzZ?) = "new school"?
Both can be hacked (ie. firmware bug)... Coreboot cannot be hacked (yet?).
http://techreport.com/news/28728/wake-f ... -to-attack
http://www.uefi.org/sites/default/files ... hoenix.pdf
http://www.intelsecurity.com/resources/ ... overed.pdf
"Best Regards"...
Posted by 73.150.85.78 via http://webwarper.net
This is added while posting a message to avoid misusing the service
-
- Samurai
- Posts: 134
- Joined: 18 Sep 2012, 20:56
- Distribution: Porteus 64bit KDE4
- Location: Absurdistan
Re: [Solved] Secure Boot Attacks (UEFI/BIOS)
Is coreboot and Windows 7 possible ?
is UEFI necessary for Windows 10 ?
is UEFI necessary for Windows 10 ?
Re: [Solved] Secure Boot Attacks (UEFI/BIOS)
Salutations...
https://www.coreboot.org/SeaBIOS#Windows
"Best Regards"...
Posted by 73.150.85.78 via http://webwarper.net
This is added while posting a message to avoid misusing the service
https://www.coreboot.org/SeaBIOS#Windows
"Best Regards"...
Posted by 73.150.85.78 via http://webwarper.net
This is added while posting a message to avoid misusing the service