I know with WinNT4 with IIS 4 and the certificate managing software
(KeyManager?) tended to break things. I couldn't even install a test cert
from Thawte or VeriSign.
I installed openssl (9.x) on my Slackware Linux box and generated a
certificate for IIS 5.0 (win2k) with no problem. Just removed everything
prior to the ----Begin Certificate---- like you had. Works just fine.
The slackware installation of openssl included a perl script to act as a
wrapper to openssl. CA.pl, all I had to do was rename the request file to
newreq.txt run `./CA.pl -sign' and it output newcert.txt
For perhaps once, M$ didn't break something? If that's the case...
Could someone let me know if hell really froze over?
On Thu, 25 Jan 2001, Tony Lill wrote:
> I don't know it M$ broke anything in IIS 5.0, but I recently signed my
> own certificate for an IIS 4.0 server, and it worked fine (once I
> figured out that I had to manually strip everything before the "BEGIN
> CERTIFICATE" stuff in the signed cert). I just used the sign.sh script
> from the mod_ssl source.
>
> If they did break something, perhaps you could "downgrade" to IIS 4.0
> --
> Tony Lill, [EMAIL PROTECTED]
> President, A. J. Lill Consultants fax/data (519) 650 3571
> 539 Grand Valley Dr., Cambridge, Ont. N3H 2S2 (519) 241 2461
> --------------- http://www.ajlc.waterloo.on.ca/ ----------------
> "Welcome to All Things UNIX, where if it's not UNIX, it's CRAP!"
> ______________________________________________________________________
> OpenSSL Project http://www.openssl.org
> User Support Mailing List [EMAIL PROTECTED]
> Automated List Manager [EMAIL PROTECTED]
>
Jacob D. Barde
Systems Engineer
McAdams Technologies, Inc.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
