david.durvaux at belnet.be
Mon Dec 2 14:15:23 CET 2013
Good to know.
BTW, it's relatively well explained on MSDN:
PGP Key Id 0xE84A32A0
Louizalaan 231 Avenue Louise
Brussel 1050 Bruxelles
T: +32 790 33 33
On 02 Dec 2013, at 12:34, Adi Kriegisch wrote:
>> So, in short, we have another whitepaper to wrote ;)
>> Ter info, don't know what's your problem with device signing but for security reasons, the recognized CA for drivers is now embedded somewhere in Windows kernel. You cannot change it and it's different from the computer / user CA store. :-S
>> If you didn't have a certificate signed by an authority can sign certificate for use on drivers, you need to boot windows in a development mode where it will basically accept anything :D.
> Fotunately it isn't that bad: You may very well install your own
> certificate authority into "Trusted Publishers" (machine wide, of course).
> Then you only get prompted wether you trust that certificate (and you may
> accept software signed by that publisher forever). The dialog looks ok and
> not like the whole world is on fire... ;-)
> For the signing certificate itself one needs to add
> "extendedKeyUsage = 188.8.131.52.4.1.3184.108.40.206" to the openssl.cnf...
> -- Adi
> Ach mailing list
> Ach at lists.cert.at
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 1535 bytes
Desc: Message signed with OpenPGP using GPGMail
More information about the Ach