I put that in my openssl.cnf in the [ usr_cert ] section, and did:
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:
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)
Signature Algorithm: md5WithRSAEncryption
b8:f0:ae:79:f8:77:1e:e0:dd:7e:40:61:91:04:bd:f2:13:e7:
5f:41:b9:45:b0:e2:68:e5:9d:bc:b4:60:dc:16:98:9d:3e:71:
cf:66:bc:52:04:d2:99:51:fb:bb:cd:6f:76:8b:40:02:e2:8f:
58:0c:cc:97:a9:b5:ac:88:b3:2b:ba:23:6a:07:32:f6:59:d5:
c6:8b:44:9f:b9:9b:4a:b2:88:bb:e4:b6:43:91:26:50:1f:c8:
55:c7:fb:7b:58:de:81:39:a7:08:bd:8d:bc:b8:85:a9:67:2e:
30:70:df:ec:14:58:3e:bd:d6:76:57:a2:36:1f:10:fc:8c:37:
2c:9d
Certificate purposes:
SSL client : Yes
SSL client CA : No
SSL server : Yes
SSL server CA : No
Netscape SSL server : Yes
Netscape SSL server CA : No
S/MIME signing : Yes
S/MIME signing CA : No
S/MIME encryption : Yes
S/MIME encryption CA : No
CRL signing : Yes
CRL signing CA : No
Any Purpose : Yes
Any Purpose CA : Yes
OCSP helper : Yes
OCSP helper CA : No
Do I have to add another parameter to openssl x509 ? My openssl.cnf was as it comes
from RedHat, with the exception that I changed the default values for responses for
generating a self-signed certificate.
-- Dean
Umesh wrote on 2003-07-13 23:22:
>Hi,
>
>The certificate on JetDirect can be used for both client and server
>authentication. JetDirect expects the installed certificate to contain
>extendedKeyUsage extension with the values serverAuth and clientAuth. Add the
>following line "extendedKeyUsage = clientAuth, serverAuth" in the section
>[usr_cert] in openssl.cnf before signing.
>
>Umesh
>
>
>"Dean Gibson (System Administrator)" wrote:
>>
>> We have an HP LJ 4600 with an internal JetDirect interface that provides an
>> embedded web server for administration. The web server has the ability to generate
>> a CSR (hplj.csr in the example below), which one can get signed and import the
>> signed certificate back into the web server.
>>
>> Since we feel that paying $$$ to a real CA to sign the CSR is a waste of money, we
>> thought we'd just try to sign it ourselves, so I did:
>>
>> openssl x509 -req -in hplj.csr -CA ultimeth.pem -days 3650 -set_serial 01 -out
>> hplj.crt
>>
>> where "ultimeth.pem" is a self-signed wildcard key/certificate previously generated
>> by openssl and working fine in Apache, Postfix, and IMAP servers.
>>
>> I then attempted to import (via cut-and-paste) the "hplj.crt" file back into the HP
>> JetDirect web server, but it doesn't like it ("The certificate entered was invalid.
>> Please try again and be sure to include the entire certificate correctly.").
>>
>> Now, I suspect that this is because the HP JetDirect web server checks to see if
>> the certificate was signed by other than a root CA.
>>
>> Any suggestions?
>>
>> -- Dean
>>
>> hplj.csr:
>>
>> -----BEGIN CERTIFICATE REQUEST-----
>> MIIB3DCCAW4CAQIwgcExKjAoBgNVBAMTIUhwTGo0NjAwZG4xLmludGVybmFsLnVs
>> dGltZXRoLm5ldDETMBEGA1UEBxMKTWlsbCBDcmVlazETMBEGA1UECBMKV2FzaGlu
>> Z3RvbjELMAkGA1UEBhMCVVMxGTAXBgNVBAoTEFVsdGlNZXRoIFN5c3RlbXMxFTAT
>> BgNVBAsTDDAwMzBDMUNEMzQwMTEPMA0GA1UECxMGSjYwNTdBMRkwFwYDVQQLExBO
>> ZXR3b3JrIFNlY3VyaXR5MHMwDQYJKoZIhvcNAQEBBQADYgAwXwJYDpuuvMURavW7
>> w/vIuwz+rqHSYpI3wlyvbHJgZ72ZNHHPdwFdHHfOHGRhn/9iLu0yY3jG+dig9hgL
>> 7a14KOX0Uppe2zFqlFenYxBBmAEMSvgvSJc3aL9bvQIDAQABoDAwLgYJKoZIhvcN
>> AQkOMSEwHzAdBgNVHSUEFjAUBggrBgEFBQcDAQYIKwYBBQUHAwIwDQYJKoZIhvcN
>> AQEEBQADWQAIrsaL/j4YV+IRxcFxfGcq9pAvtoMSz1wfPLbn1n2UP19z9aYS2E+Y
>> 4Vs5sQ4n0RefO/ssLV3X868CDni7v+CsFbuSeyzQo1D0DKNprzlZpmt8RI6QNjNh
>> -----END CERTIFICATE REQUEST-----
>>
>> hplj.crt:
>>
>> -----BEGIN CERTIFICATE-----
>> MIICsTCCAhoCAQEwDQYJKoZIhvcNAQEEBQAwgawxCzAJBgNVBAYTAlVTMRMwEQYD
>> VQQIEwpXYXNoaW5ndG9uMRMwEQYDVQQHEwpNaWxsIENyZWVrMRkwFwYDVQQKExBV
>> bHRpTWV0aCBTeXN0ZW1zMRkwFwYDVQQLExBOZXR3b3JrIFNlY3VyaXR5MRcwFQYD
>> VQQDFA4qLnVsdGltZXRoLm5ldDEkMCIGCSqGSIb3DQEJARYVc2VjdXJpdHlAdWx0
>> aW1ldGgubmV0MB4XDTAzMDcxMTE4NTkxOVoXDTEzMDcwODE4NTkxOVowgcExKjAo
>> BgNVBAMTIUhwTGo0NjAwZG4xLmludGVybmFsLnVsdGltZXRoLm5ldDETMBEGA1UE
>> BxMKTWlsbCBDcmVlazETMBEGA1UECBMKV2FzaGluZ3RvbjELMAkGA1UEBhMCVVMx
>> GTAXBgNVBAoTEFVsdGlNZXRoIFN5c3RlbXMxFTATBgNVBAsTDDAwMzBDMUNEMzQw
>> MTEPMA0GA1UECxMGSjYwNTdBMRkwFwYDVQQLExBOZXR3b3JrIFNlY3VyaXR5MHMw
>> DQYJKoZIhvcNAQEBBQADYgAwXwJYDpuuvMURavW7w/vIuwz+rqHSYpI3wlyvbHJg
>> Z72ZNHHPdwFdHHfOHGRhn/9iLu0yY3jG+dig9hgL7a14KOX0Uppe2zFqlFenYxBB
>> mAEMSvgvSJc3aL9bvQIDAQABMA0GCSqGSIb3DQEBBAUAA4GBAGeulywMQHY4NulL
>> 6so3kyBwmPGfi4cPqSUZKQPWceV27yjKZmfuDoSgSKRlsusIFROBo+DwTbzSYcbH
>> Oxb9digc4oasTQhdx3uFSuBWT0h/l3l1Qt2XaV+Zv7197eenWtF8YUisJhmr1Q+p
>> B3Gk+Z7eqHvPPBKEQzBhTZ7kywoX
>> -----END CERTIFICATE-----
>>
>> ______________________________________________________________________
>> 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]
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]