I found a solution. It seems that the 'export' from the IIS key manager is
not strictly an encrypted private keyfile. I located this message via
deja.com:
Forum: comp.infosystems.www.servers.unix
Subject:howto convert ssl private key IIS->Apache
Date:08/23/1999
Author:bum <[EMAIL PROTECTED]>
subj. The method described as:
1. Export a backup file of the Certificate from the Key-Manager. 2.
Find this string in the binary file : "private-key" 3. Trace back
until You find this Hex value : "30 82"
4. Write from that position to a new file (tmp.bin).
5. With OpenSSL : ssleay rsa -inform NET -in tmp.bin -out key.pem 6.
Type password...
doesn't work. Maybe because IIS key is 1024 bits instead of 512 and
certified by Thawte, not Verisign. I get error:
asn1 encoding routines:ASN1_get_object:too long:asn1_lib.c:140
Is there any other way how to extract private key from that stupid
IIS?
Any suggestions?
Although it seems this technique didn't work for the message author, it
worked for me <smile>.
____
Bowen Moursund (dBASE, Inc.)
USMail: PO Box 12526, San Antonio TX 78212-0526, USA
UPS: 2515 McCullough Suite 201, San Antonio TX 78212, USA
Web: http://www.dbase.com
--
This is The OpenSA Project's mailing list. For more information,
please visit the project's web site at http://www.opensa.org
To unsubscribe the list, send an empty email message to address
[EMAIL PROTECTED]
