RSSfeed
28th October 2011, 15:02
http://feedads.g.doubleclick.net/~a/aDeVzE-N_8NHmompP0pdVDMn5vY/0/di (http://feedads.g.doubleclick.net/~a/aDeVzE-N_8NHmompP0pdVDMn5vY/0/da)
http://feedads.g.doubleclick.net/~a/aDeVzE-N_8NHmompP0pdVDMn5vY/1/di (http://feedads.g.doubleclick.net/~a/aDeVzE-N_8NHmompP0pdVDMn5vY/1/da)
Canonical, along with Red Hat, have today published a white paper on the potential implications, and benefits, of “Secure boot” – the new ‘locked in’ boot safeguard Microsoft will require all PCs to ship with should they want to install Windows 8.
Secure Boot is designed to protect users from malware – a noble aim. It achieves this by only allowing pre-approved and signed software contained to boot. Software that isn’t approved is*prohibited*from booting.
Microsoft, whose Windows 8 operating system will need Secure boot to be enabled by default, have laid out their idea of how secure boot should be*implemented*- one that will see users of alternate operating systems, such as Ubuntu, placed at a disadvantage.
Microsoft’s proposal places no requirement on system*manufacturers*to provide*users with an ‘off’ switch for Secure Boot, nor does it lay out a method for adding extra ‘trusted’ software and operating systems after a system has been bought.
Solution Canonical and Red Hat propose a different solution: one that provides users with the security afforded by Secure Boot, but one that also allows users to add more software and OSes – such as Linux – to the BIOS’ approval list.
This would, it’s hoped, allow users to run both Windows 8 and Linux, be it installed or on live media, on a PC with Secure Boot enabled.
Further still, the white paper suggests that PCs ship with a user-friendly interface for disabling/enabling secure boot altogether.
Read the whitepaper (http://blog.canonical.com/2011/10/28/white-paper-secure-boot-impact-on-linux/) http://cdn.omgubuntu.co.uk/wp-content/plugins/flattr/img/flattr-badge-large.png (http://www.omgubuntu.co.uk/?flattrss_redirect&id=22814&md5=a1dde752bf20f20aba6963e25fef9213)
http://feeds.feedburner.com/~ff/d0od?i=sJQ_Qrl9yNU:i8VRxX_NAFU:wBxX2hOkimM (http://feeds.feedburner.com/~ff/d0od?a=sJQ_Qrl9yNU:i8VRxX_NAFU:wBxX2hOkimM) http://feeds.feedburner.com/~ff/d0od?d=qj6IDK7rITs (http://feeds.feedburner.com/~ff/d0od?a=sJQ_Qrl9yNU:i8VRxX_NAFU:qj6IDK7rITs) http://feeds.feedburner.com/~ff/d0od?i=sJQ_Qrl9yNU:i8VRxX_NAFU:V_sGLiPBpWU (http://feeds.feedburner.com/~ff/d0od?a=sJQ_Qrl9yNU:i8VRxX_NAFU:V_sGLiPBpWU) http://feeds.feedburner.com/~ff/d0od?i=sJQ_Qrl9yNU:i8VRxX_NAFU:-BTjWOF_DHI (http://feeds.feedburner.com/~ff/d0od?a=sJQ_Qrl9yNU:i8VRxX_NAFU:-BTjWOF_DHI) http://feeds.feedburner.com/~ff/d0od?i=sJQ_Qrl9yNU:i8VRxX_NAFU:gIN9vFwOqvQ (http://feeds.feedburner.com/~ff/d0od?a=sJQ_Qrl9yNU:i8VRxX_NAFU:gIN9vFwOqvQ) http://feeds.feedburner.com/~ff/d0od?d=yIl2AUoC8zA (http://feeds.feedburner.com/~ff/d0od?a=sJQ_Qrl9yNU:i8VRxX_NAFU:yIl2AUoC8zA)
http://feeds.feedburner.com/~r/d0od/~4/sJQ_Qrl9yNU
Mer ... (http://feedproxy.google.com/~r/d0od/~3/sJQ_Qrl9yNU/)
http://feedads.g.doubleclick.net/~a/aDeVzE-N_8NHmompP0pdVDMn5vY/1/di (http://feedads.g.doubleclick.net/~a/aDeVzE-N_8NHmompP0pdVDMn5vY/1/da)
Canonical, along with Red Hat, have today published a white paper on the potential implications, and benefits, of “Secure boot” – the new ‘locked in’ boot safeguard Microsoft will require all PCs to ship with should they want to install Windows 8.
Secure Boot is designed to protect users from malware – a noble aim. It achieves this by only allowing pre-approved and signed software contained to boot. Software that isn’t approved is*prohibited*from booting.
Microsoft, whose Windows 8 operating system will need Secure boot to be enabled by default, have laid out their idea of how secure boot should be*implemented*- one that will see users of alternate operating systems, such as Ubuntu, placed at a disadvantage.
Microsoft’s proposal places no requirement on system*manufacturers*to provide*users with an ‘off’ switch for Secure Boot, nor does it lay out a method for adding extra ‘trusted’ software and operating systems after a system has been bought.
Solution Canonical and Red Hat propose a different solution: one that provides users with the security afforded by Secure Boot, but one that also allows users to add more software and OSes – such as Linux – to the BIOS’ approval list.
This would, it’s hoped, allow users to run both Windows 8 and Linux, be it installed or on live media, on a PC with Secure Boot enabled.
Further still, the white paper suggests that PCs ship with a user-friendly interface for disabling/enabling secure boot altogether.
Read the whitepaper (http://blog.canonical.com/2011/10/28/white-paper-secure-boot-impact-on-linux/) http://cdn.omgubuntu.co.uk/wp-content/plugins/flattr/img/flattr-badge-large.png (http://www.omgubuntu.co.uk/?flattrss_redirect&id=22814&md5=a1dde752bf20f20aba6963e25fef9213)
http://feeds.feedburner.com/~ff/d0od?i=sJQ_Qrl9yNU:i8VRxX_NAFU:wBxX2hOkimM (http://feeds.feedburner.com/~ff/d0od?a=sJQ_Qrl9yNU:i8VRxX_NAFU:wBxX2hOkimM) http://feeds.feedburner.com/~ff/d0od?d=qj6IDK7rITs (http://feeds.feedburner.com/~ff/d0od?a=sJQ_Qrl9yNU:i8VRxX_NAFU:qj6IDK7rITs) http://feeds.feedburner.com/~ff/d0od?i=sJQ_Qrl9yNU:i8VRxX_NAFU:V_sGLiPBpWU (http://feeds.feedburner.com/~ff/d0od?a=sJQ_Qrl9yNU:i8VRxX_NAFU:V_sGLiPBpWU) http://feeds.feedburner.com/~ff/d0od?i=sJQ_Qrl9yNU:i8VRxX_NAFU:-BTjWOF_DHI (http://feeds.feedburner.com/~ff/d0od?a=sJQ_Qrl9yNU:i8VRxX_NAFU:-BTjWOF_DHI) http://feeds.feedburner.com/~ff/d0od?i=sJQ_Qrl9yNU:i8VRxX_NAFU:gIN9vFwOqvQ (http://feeds.feedburner.com/~ff/d0od?a=sJQ_Qrl9yNU:i8VRxX_NAFU:gIN9vFwOqvQ) http://feeds.feedburner.com/~ff/d0od?d=yIl2AUoC8zA (http://feeds.feedburner.com/~ff/d0od?a=sJQ_Qrl9yNU:i8VRxX_NAFU:yIl2AUoC8zA)
http://feeds.feedburner.com/~r/d0od/~4/sJQ_Qrl9yNU
Mer ... (http://feedproxy.google.com/~r/d0od/~3/sJQ_Qrl9yNU/)