View Single Post
Old 03-20-2016, 12:00 AM   #3
knc1
Going Viral
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
What is the point?
That is the normal operation for the device.

= = = = = =

And why in the world would you distribute your private key?
Even in Windows, of a Public-Private key-pair, the Private key is kept, well, private.

Now anyone in the world can use your private key to sign a Windows driver, claiming to be yourself.

I think you should pull that archive and re-think (or read the directions) on what its contents should be.

That re-think should include posting a CRL for the (just) compromised key-pair and using a new key-pair to sign the next driver (and then only distribute the public key required to verify the signing of the driver).

Last edited by knc1; 03-20-2016 at 12:19 AM.
knc1 is offline   Reply With Quote