<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<br>
On 07.06.12 22:20, Kerry Brown wrote:
<blockquote
cite="mid:A0615421071EDD4A9F851117D67D538A5D5D28B6@EXCH01.KDBSystems.local"
type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta name="Generator" content="Microsoft Word 14 (filtered
medium)">
<base href="x-msg://1175/">
<style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.apple-style-span
{mso-style-name:apple-style-span;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif][if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif"; color: rgb(31,
73, 125);">We’ll have to agree to disagree. I don’t see that
changing a setting in the BIOS is a big deal. If Microsoft
was telling OEMs to not implement a way to turn off
SecureBoot I’d be right there with you complaining. FWIW
Apple is also implementing this and there is no way to turn
it off AFAIK. New Apples will only be able to boot Mac OS or
Windows 8 because of this.</span></p>
</div>
</blockquote>
<br>
While I don't intend to defend Apple in any way... what you describe
is:<br>
<br>
- speculation, because no such Apple computers exist;<br>
- not likely to happen, because an Apple computer user might want to
install Windows 7 (which is better suited for desktop/laptop use)
and that Windows version can't boot with "secure" boot loaders. The
existence of successful previous versions of Windows is the sole
reason why Microsoft is agreeing to make this optional on "desktop"
computers.<br>
<br>
My opinion is that this idea will not fly for long. The percentage
of Windows computers is decreasing and the new purchases are more in
either the DIY category or computers not intended to run Windows.
Those who manufacture hardware need to make some money, however
strong their love for Microsoft is (or not).<br>
Yes, we will see a number of models with such UEFI loader, mostly on
trade shows -- and life will continue as usual.<br>
The concept is just not good enough from technical and logistics
perspective. It benefits nobody else but Microsoft.<br>
<br>
There is of course the unfortunate involvement in all this for
Verisign. I wonder here however, because Verisign actually sold the
certificates business to Symantec last year. Are they starting
again? Not likely. So it will be really Symantec, to take all the
bad press. But, if this is going to use certificates, someone has to
root the chain of trust and it is likely all those industry parties
agree that be someone "impartial".<br>
</body>
</html>