I used to generate a self-signed certificate for each hostname I was using for an SSL
connection (www.ultimeth.net, imaps.ultimeth.net, smtp.ultimeth.net, etc. ...). Then
a couple weeks ago in browsing the Internet, I happened across this site:
http://www.freessl.com. I noticed that they sell a "wildcard" SSL certificate. So I
thought, if they can sell one, why can't I generate a self-signed one?
The answer is, I/you can! Now I have just one self-signed certificate, and it works
with all of my Unix-based SSL-enabled servers.
It seems to me that it is in the best interest of the major CAs to not offer wildcard
certificates; that way, they can charge their outrageous prices for each certificate
that you need, and when you happen to change a hostname, they are right there at the
trough looking for more money.
The JetDirect situation is a bit different, in that the JetDirect firmware generates
the private key but never displays it. This means someone has to sign it. I think my
problem with the JetDirect server is as Umesh (from HP) stated, that I need to get the
generated certificate to include the requested extensions (see CSR below) to the
issued certificate.
-- Dean
Certificate Request:
Data:
Version: 2 (0x2)
Subject: CN=HpLj4600dn1.internal.ultimeth.net, L=Mill Creek, ST=Washington,
C=US, O=UltiMeth Systems, OU=0030C1CD3401, OU=J6057A, OU=Network Security
Subject Public Key Info:
Public Key Algorithm: rsaEncryption
RSA Public Key: (700 bit)
Modulus (700 bit):
09:e3:11:2c:bc:01:6f:95:f8:67:bd:be:4f:1f:67:
e8:f5:af:dc:1d:87:91:a4:21:f3:c9:e8:58:47:17:
a0:ad:45:cd:c8:e1:ef:b1:a9:8a:05:7d:6f:f8:75:
ee:97:27:3f:a8:cf:34:55:09:28:fe:a7:8e:77:03:
c9:e5:3b:e2:f2:cb:6b:77:ea:9e:7f:ae:44:8f:c8:
62:5c:aa:3f:fe:84:8c:eb:f3:50:df:6a:d5
Exponent: 65537 (0x10001)
Attributes:
Requested Extensions:
X509v3 Extended Key Usage:
TLS Web Server Authentication, TLS Web Client Authentication
Signature Algorithm: md5WithRSAEncryption
02:06:7b:1d:9b:bf:3d:5f:c2:f2:00:b1:6e:e0:c4:ca:71:fb:
a7:83:5b:05:97:9c:09:3b:f5:46:df:ec:aa:bb:f2:59:57:b6:
7e:85:30:28:02:b3:ed:ce:9c:ae:5e:86:02:0e:50:1c:b2:f9:
c7:20:90:0a:5b:e6:34:33:3d:22:13:80:23:14:40:a7:58:d9:
3f:b5:88:01:6c:e6:02:ec:14:59:50:c9:0a:91:a8:b3
Charles B Cranston wrote on 2003-07-14 08:13:
>I'm not sure that this is AT ALL relevant but I noticed that the issuer CN has a
>wildcard and I wonder 1) what this means, and 2) if this could be confusing something?
>
>Dean Gibson (System Administrator) wrote:
>
>>openssl x509 -req -in hplj4600dn1.csr -CA ultimeth.pem -days 3650 -set_serial 01
>>-out hplj4600dn1.crt
>
>>It didn't help; here's what "openssl x509 -in hplj4600dn1.crt -text -purpose" shows:
>
>>Certificate:
>> Data:
>> Version: 1 (0x0)
>> Serial Number: 1 (0x1)
>> Signature Algorithm: md5WithRSAEncryption
>> Issuer: C=US, ST=Washington, L=Mill Creek, O=UltiMeth Systems,
>> OU=Network Security, CN=*.ultimeth.net/
>......................................^
>> [EMAIL PROTECTED]
>> Validity
>> Not Before: Jul 14 08:05:58 2003 GMT
>> Not After : Jul 11 08:05:58 2013 GMT
>> Subject: CN=HpLj4600dn1.internal.ultimeth.net, L=Mill Creek,
>> ST=Washington, C=US, O=UltiMeth Systems,
>> OU=0030C1CD3401, OU=J6057A, OU=Network Security
>> Subject Public Key Info:
>> Public Key Algorithm: rsaEncryption
>> RSA Public Key: (700 bit)
>> Modulus (700 bit):
>> 09:e3:11:2c:bc:01:6f:95:f8:67:bd:be:4f:1f:67:
>...
>
>--
>Charles B (Ben) Cranston
>mailto: [EMAIL PROTECTED]
>http://www.wam.umd.edu/~zben
>
>______________________________________________________________________
>OpenSSL Project http://www.openssl.org
>User Support Mailing List [EMAIL PROTECTED]
>Automated List Manager [EMAIL PROTECTED]
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]