retrieve memory usage per session in jsp
Hi Martin, I have this app running on tomcat + oc4j. The app is designed using simple j2ee and struts framework. I would like to watch/monitor how much memory is used per session at any given point of time. Basically i want to design a jsp just to monitor memory usage per session. If you are aware of any info about this. Please let me know. Thanks in advance. Ajay Kumar -- View this message in context: http://www.nabble.com/Re%3A-SSL-per-session-memory-usage-tp961035p21714991.html Sent from the OpenSSL - User mailing list archive at Nabble.com. __ OpenSSL Project http://www.openssl.org User Support Mailing Listopenssl-users@openssl.org Automated List Manager majord...@openssl.org
block type is not 01
Can you help me out? When I execute: openssl s_client -connect 204.101.57.74:443 I'm getting this error: 47620:error:0407006A:rsa routines:RSA_padding_check_PKCS1_type_1:block type is not 01:rsa_pk1.c:100: 47620:error:04067072:rsa routines:RSA_EAY_PUBLIC_DECRYPT:padding check failed:rsa_eay.c:697: 47620:error:1408D07B:SSL routines:SSL3_GET_KEY_EXCHANGE:bad signature:s3_clnt.c:1448: Apache 2.2.3 is handling the request, compiled with OpenSSL 0.9.8i. It does the same if I use another certificate (self-signed). I must be an Apache / OpenSSL problem. From the browser (Firefox) the certificate is accepted. Thanks! __ OpenSSL Project http://www.openssl.org User Support Mailing Listopenssl-users@openssl.org Automated List Manager majord...@openssl.org
Re: block type is not 01
On Wed, Jan 28, 2009 at 09:16:18PM -0500, Georges-Etienne Legendre wrote: Can you help me out? When I execute: openssl s_client -connect 204.101.57.74:443 I'm getting this error: 47620:error:0407006A:rsa routines:RSA_padding_check_PKCS1_type_1:block type is not 01:rsa_pk1.c:100: 47620:error:04067072:rsa routines:RSA_EAY_PUBLIC_DECRYPT:padding check failed:rsa_eay.c:697: 47620:error:1408D07B:SSL routines:SSL3_GET_KEY_EXCHANGE:bad signature:s3_clnt.c:1448: Apache 2.2.3 is handling the request, compiled with OpenSSL 0.9.8i. It does the same if I use another certificate (self-signed). I must be an Apache / OpenSSL problem. From the browser (Firefox) the certificate is accepted. Firefox negotiates 128-bit RC4-SHA in preference to 3DES, it probably rates 3DES as a 112-bit cipher. While s_client rates 3DES as a 168-bit cipher and the server's 3DES implementation is broken. Is the server running Apache on Windows based on Microsoft's CryptoAPI? Try: $ openssl s_client -cipher 'DEFAULT:!3DES' ... -- Viktor. __ OpenSSL Project http://www.openssl.org User Support Mailing Listopenssl-users@openssl.org Automated List Manager majord...@openssl.org
Re: Multiple CRL with same issuer
PS a écrit : Hi All, I was under the impression that openssl allows loading multiple CRLs for the same issuer. But, this does not seem to be the case as is proved by using openssl verify. $ ls -l ./ca/ total 24 lrwxrwxrwx 1 pshah users 10 Jan 28 21:56 ba4bb3b6.0 - cacert.pem - the CA cert lrwxrwxrwx 1 pshah users 14 Jan 28 21:56 ba4bb3b6.r0 - revoked_48.pem revokes only cert48.pem lrwxrwxrwx 1 pshah users 14 Jan 28 21:56 ba4bb3b6.r1 - revoked_49.pem - revokes only cert49.pem -rw-r--r-- 1 pshah users 1233 Jan 28 17:09 cacert.pem -rw-r--r-- 1 pshah users 560 Jan 28 17:10 revoked_48.pem -rw-r--r-- 1 pshah users 560 Jan 28 17:10 revoked_49.pem $ openssl verify -CApath ./ca/ -crl_check -verbose cert49.pem cert49.pem: OK $ openssl verify -CApath ./ca/ -crl_check -verbose cert48.pem cert48.pem: /C=--/ST=California/L=San Francisco/O=Riverbed Technology, Inc./OU=Steelhead/CN=hw1-sh18/emailaddress=fakeem...@example.com mailto:fakeem...@example.com error 23 at 0 depth lookup:certificate revoked 29615:error:0B07D065:x509 certificate routines:X509_STORE_add_crl:cert already in hash table:x509_lu.c:418: A CRL ( Certificat revocation list) is the list of ALL the revoked certificates at the time it is issued So if at time t1 a certificate 48 is revoked then all the subsequent CRLs MUST indicate that the certificate 48 as revoked If later at time t2 the certificate 49 is revoked hen all the subsequent CRLs MUST indicate that both certificate 48 and certificate 49 arte revoked Thus only the lasT CRL has to considered . Since the delivery times of the CRLs are close together it is not easy to check into the example which is ithe last CRL So, as seen above, the second CRL is not loaded (and I have confirmed this with gdb.). A second related question is that even if openssl allowed loading multiple CRL for the same issuer, it looks as if openssl will only use the first unexpired CRL from the list. There might be cases where you would have a fresher unexpired CRL which might not get picked and result in wrong verification result. If a CRL is expired this means that a new CRL should have been delivered and you have not received it. To avoid dangerous forbidden access every access should be forbidden. To take into account unexpected urgent problem a new CRL may be issued even when the previous one is not expired. I hope this help. Dominique LOHEZ A third question is that what if I had two valid CRLs from the same issuer (CRL1 revoked cert 1 and CRL2 revokes cert 2), then when cert 2 is to be verified, it would wrongly be considered unrevoked. Thanks, Paras -- Dr Dominique LOHEZ ISEN 41, Bd Vauban F59046 LILLE France Phone : +33 (0)3 20 30 40 71 Email: dominique.lo...@isen.fr __ OpenSSL Project http://www.openssl.org User Support Mailing Listopenssl-users@openssl.org Automated List Manager majord...@openssl.org
RE: Multiple CRL with same issuer
I was under the impression that openssl allows loading multiple CRLs for the same issuer. But, this does not seem to be the case as is proved by using openssl verify. $ ls -l ./ca/ total 24 lrwxrwxrwx 1 pshah users 10 Jan 28 21:56 ba4bb3b6.0 - cacert.pem - the CA cert lrwxrwxrwx 1 pshah users 14 Jan 28 21:56 ba4bb3b6.r0 - revoked_48.pem revokes only cert48.pem lrwxrwxrwx 1 pshah users 14 Jan 28 21:56 ba4bb3b6.r1 - revoked_49.pem - revokes only cert49.pem -rw-r--r-- 1 pshah users 1233 Jan 28 17:09 cacert.pem -rw-r--r-- 1 pshah users 560 Jan 28 17:10 revoked_48.pem -rw-r--r-- 1 pshah users 560 Jan 28 17:10 revoked_49.pem $ openssl verify -CApath ./ca/ -crl_check -verbose cert49.pem cert49.pem: OK $ openssl verify -CApath ./ca/ -crl_check -verbose cert48.pem cert48.pem: /C=--/ST=California/L=San Francisco/O=Riverbed Technology, Inc./OU=Steelhead/CN=hw1-sh18/emailaddress=fakeem...@example.com mailto:fakeem...@example.com error 23 at 0 depth lookup:certificate revoked 29615:error:0B07D065:x509 certificate routines:X509_STORE_add_crl:cert already in hash table:x509_lu.c:418: A CRL ( Certificat revocation list) is the list of ALL the revoked certificates at the time it is issued So if at time t1 a certificate 48 is revoked then all the subsequent CRLs MUST indicate that the certificate 48 as revoked If later at time t2 the certificate 49 is revoked hen all the subsequent CRLs MUST indicate that both certificate 48 and certificate 49 arte revoked Thus only the lasT CRL has to considered . Since the delivery times of the CRLs are close together it is not easy to check into the example which is ithe last CRL i think you misunderstood the question. the issue at hand is not about older and latest copies of a particular (certificate revocation) list, but it is about two *distinct* simultaneously valid and active (certificate revocation) lists that are issued/maintained by the same issuer. http://tools.ietf.org/html/rfc5280#section-5 Each CRL has a particular scope. The CRL scope is the set of certificates that could appear on a given CRL. For example, the scope could be all certificates issued by CA X, all CA certificates issued by CA X, all certificates issued by CA X that have been revoked for reasons of key compromise and CA compromise, or a set of certificates based on arbitrary local information, such as all certificates issued to the NIST employees located in Boulder. _ Hotmail® goes where you go. On a PC, on the Web, on your phone. http://www.windowslive-hotmail.com/learnmore/versatility.aspx#mobile?ocid=TXT_TAGHM_WL_HM_versatility_121208
Re: Multiple CRL with same issuer
I think you're trying to assume something that cannot be assumed: you assume that ALL unexpired CRLs are considered. This is not the case. As Dominiqué said, only the CRL that has the latest signature time is considered. This is evident in the name of the file type: Certificate Revocation *List*. It is legal to issue a CRL that revokes a certificate (possibly with an type of onhold, for V3 CRLs) with an expiration time of 2 years in the future, and the next hour the to remove the revocation status. If all simultaneously-valid CRLs are considered, then the intended consequence of unrevoking the certificate would be impossible. This is why the CRL must contain the *complete* list of *all* revoked certificates which have not yet expired. There is a PKIX extension, delta CRLs, which defines for V3 CRLs a way to allow for adding to the list of the most-recently-issued full CRL. In order to support unrevocation, there is a special status type (called remove_from_crl) for the delta CRL which is to be interpreted as removing the certificate from the revocation list; however, in a full V3 CRL, that status type is illegal. And in V2 CRLs (the default, since many implementations do not handle V3 CRLs) there is no means of specifying the extension that contains a status type regardless. This is specified in PKIX (currently RFC 5280); in order to maintain standards-conformance OpenSSL cannot change this behavior. (Nor can it even offer an option to change it, since its job is to maintain security-system interoperability, not capriciously make it less secure.) -Kyle H 2009/1/29 Giang Nguyen cau...@hotmail.com: I was under the impression that openssl allows loading multiple CRLs for the same issuer. But, this does not seem to be the case as is proved by using openssl verify. $ ls -l ./ca/ total 24 lrwxrwxrwx 1 pshah users 10 Jan 28 21:56 ba4bb3b6.0 - cacert.pem - the CA cert lrwxrwxrwx 1 pshah users 14 Jan 28 21:56 ba4bb3b6.r0 - revoked_48.pem revokes only cert48.pem lrwxrwxrwx 1 pshah users 14 Jan 28 21:56 ba4bb3b6.r1 - revoked_49.pem - revokes only cert49.pem -rw-r--r-- 1 pshah users 1233 Jan 28 17:09 cacert.pem -rw-r--r-- 1 pshah users 560 Jan 28 17:10 revoked_48.pem -rw-r--r-- 1 pshah users 560 Jan 28 17:10 revoked_49.pem $ openssl verify -CApath ./ca/ -crl_check -verbose cert49.pem cert49.pem: OK $ openssl verify -CApath ./ca/ -crl_check -verbose cert48.pem cert48.pem: /C=--/ST=California/L=San Francisco/O=Riverbed Technology, Inc./OU=Steelhead/CN=hw1-sh18/emailaddress=fakeem...@example.com mailto:fakeem...@example.com error 23 at 0 depth lookup:certificate revoked 29615:error:0B07D065:x509 certificate routines:X509_STORE_add_crl:cert already in hash table:x509_lu.c:418: A CRL ( Certificat revocation list) is the list of ALL the revoked certificates at the time it is issued So if at time t1 a certificate 48 is revoked then all the subsequent CRLs MUST indicate that the certificate 48 as revoked If later at time t2 the certificate 49 is revoked hen all the subsequent CRLs MUST indicate that both certificate 48 and certificate 49 arte revoked Thus only the lasT CRL has to considered . Since the delivery times of the CRLs are close together it is not easy to check into the example which is ithe last CRL i think you misunderstood the question. the issue at hand is not about older and latest copies of a particular (certificate revocation) list, but it is about two *distinct* simultaneously valid and active (certificate revocation) lists that are issued/maintained by the same issuer. http://tools.ietf.org/html/rfc5280#section-5 Each CRL has a particular scope. The CRL scope is the set of certificates that could appear on a given CRL. For example, the scope could be all certificates issued by CA X, all CA certificates issued by CA X, all certificates issued by CA X that have been revoked for reasons of key compromise and CA compromise, or a set of certificates based on arbitrary local information, such as all certificates issued to the NIST employees located in Boulder. Hotmail(R) goes where you go. On a PC, on the Web, on your phone. See how. __ OpenSSL Project http://www.openssl.org User Support Mailing Listopenssl-users@openssl.org Automated List Manager majord...@openssl.org
Re: Multiple CRL with same issuer
(First: I'm sorry. I misunderstood something I read in the OpenSSL documentation. CRLs are always V2 according to RFC5280.) I have not heard of the ability to specify or process multiple scopes in OpenSSL; however, have you verified that the CRL Extension Issuing Distribution Point is different between the two CRLs? This is where different scopes are specified (section 5.2.5 of RFC 5280). -Kyle H 2009/1/29 Kyle Hamilton aerow...@gmail.com: I think you're trying to assume something that cannot be assumed: you assume that ALL unexpired CRLs are considered. This is not the case. As Dominiqué said, only the CRL that has the latest signature time is considered. This is evident in the name of the file type: Certificate Revocation *List*. It is legal to issue a CRL that revokes a certificate (possibly with an type of onhold, for V3 CRLs) with an expiration time of 2 years in the future, and the next hour the to remove the revocation status. If all simultaneously-valid CRLs are considered, then the intended consequence of unrevoking the certificate would be impossible. This is why the CRL must contain the *complete* list of *all* revoked certificates which have not yet expired. There is a PKIX extension, delta CRLs, which defines for V3 CRLs a way to allow for adding to the list of the most-recently-issued full CRL. In order to support unrevocation, there is a special status type (called remove_from_crl) for the delta CRL which is to be interpreted as removing the certificate from the revocation list; however, in a full V3 CRL, that status type is illegal. And in V2 CRLs (the default, since many implementations do not handle V3 CRLs) there is no means of specifying the extension that contains a status type regardless. This is specified in PKIX (currently RFC 5280); in order to maintain standards-conformance OpenSSL cannot change this behavior. (Nor can it even offer an option to change it, since its job is to maintain security-system interoperability, not capriciously make it less secure.) -Kyle H 2009/1/29 Giang Nguyen cau...@hotmail.com: I was under the impression that openssl allows loading multiple CRLs for the same issuer. But, this does not seem to be the case as is proved by using openssl verify. $ ls -l ./ca/ total 24 lrwxrwxrwx 1 pshah users 10 Jan 28 21:56 ba4bb3b6.0 - cacert.pem - the CA cert lrwxrwxrwx 1 pshah users 14 Jan 28 21:56 ba4bb3b6.r0 - revoked_48.pem revokes only cert48.pem lrwxrwxrwx 1 pshah users 14 Jan 28 21:56 ba4bb3b6.r1 - revoked_49.pem - revokes only cert49.pem -rw-r--r-- 1 pshah users 1233 Jan 28 17:09 cacert.pem -rw-r--r-- 1 pshah users 560 Jan 28 17:10 revoked_48.pem -rw-r--r-- 1 pshah users 560 Jan 28 17:10 revoked_49.pem $ openssl verify -CApath ./ca/ -crl_check -verbose cert49.pem cert49.pem: OK $ openssl verify -CApath ./ca/ -crl_check -verbose cert48.pem cert48.pem: /C=--/ST=California/L=San Francisco/O=Riverbed Technology, Inc./OU=Steelhead/CN=hw1-sh18/emailaddress=fakeem...@example.com mailto:fakeem...@example.com error 23 at 0 depth lookup:certificate revoked 29615:error:0B07D065:x509 certificate routines:X509_STORE_add_crl:cert already in hash table:x509_lu.c:418: A CRL ( Certificat revocation list) is the list of ALL the revoked certificates at the time it is issued So if at time t1 a certificate 48 is revoked then all the subsequent CRLs MUST indicate that the certificate 48 as revoked If later at time t2 the certificate 49 is revoked hen all the subsequent CRLs MUST indicate that both certificate 48 and certificate 49 arte revoked Thus only the lasT CRL has to considered . Since the delivery times of the CRLs are close together it is not easy to check into the example which is ithe last CRL i think you misunderstood the question. the issue at hand is not about older and latest copies of a particular (certificate revocation) list, but it is about two *distinct* simultaneously valid and active (certificate revocation) lists that are issued/maintained by the same issuer. http://tools.ietf.org/html/rfc5280#section-5 Each CRL has a particular scope. The CRL scope is the set of certificates that could appear on a given CRL. For example, the scope could be all certificates issued by CA X, all CA certificates issued by CA X, all certificates issued by CA X that have been revoked for reasons of key compromise and CA compromise, or a set of certificates based on arbitrary local information, such as all certificates issued to the NIST employees located in Boulder. Hotmail(R) goes where you go. On a PC, on the Web, on your phone. See how. __ OpenSSL Project http://www.openssl.org User Support Mailing Listopenssl-users@openssl.org Automated List Manager
Re: How to parse pem file
Hi, consider reading the openssl x509 tool's sources for example, try openssl x509 -purpose some.cert The functionality can be coded to C using the X509 OpenSSL API for example, load the certificate like this: X509 *PEM_read_X509(FILE *fp, X509 **x, pem_password_cb *cb, void *u); and then use functions like these: X509_get_issuer_name X509_set_serialNumber ... On Thu, Jan 29, 2009 at 4:14 AM, Leo, Liangyou Wang (liangwan) liang...@cisco.com wrote: Hi all, Do you know which API could parse pem file of certificate? Then we could get version/validate/serial number and etc. Thanks! Regards, Leo __ OpenSSL Project http://www.openssl.org User Support Mailing Listopenssl-users@openssl.org Automated List Manager majord...@openssl.org
Re: block type is not 01
It works with what you suggested. Apache is running on a Linux box. Is there something to set in Apache to resolve this? -- Georges-Etienne Legendre, ing. jr On 29-Jan-09, at 3:56 AM, Victor Duchovni wrote: On Wed, Jan 28, 2009 at 09:16:18PM -0500, Georges-Etienne Legendre wrote: Can you help me out? When I execute: openssl s_client -connect 204.101.57.74:443 I'm getting this error: 47620:error:0407006A:rsa routines:RSA_padding_check_PKCS1_type_1:block type is not 01:rsa_pk1.c:100: 47620:error:04067072:rsa routines:RSA_EAY_PUBLIC_DECRYPT:padding check failed:rsa_eay.c:697: 47620:error:1408D07B:SSL routines:SSL3_GET_KEY_EXCHANGE:bad signature:s3_clnt.c:1448: Apache 2.2.3 is handling the request, compiled with OpenSSL 0.9.8i. It does the same if I use another certificate (self-signed). I must be an Apache / OpenSSL problem. From the browser (Firefox) the certificate is accepted. Firefox negotiates 128-bit RC4-SHA in preference to 3DES, it probably rates 3DES as a 112-bit cipher. While s_client rates 3DES as a 168- bit cipher and the server's 3DES implementation is broken. Is the server running Apache on Windows based on Microsoft's CryptoAPI? Try: $ openssl s_client -cipher 'DEFAULT:!3DES' ... -- Viktor. __ OpenSSL Project http://www.openssl.org User Support Mailing Listopenssl-users@openssl.org Automated List Manager majord...@openssl.org __ OpenSSL Project http://www.openssl.org User Support Mailing Listopenssl-users@openssl.org Automated List Manager majord...@openssl.org
DSA and safe primes
Hi, I was looking at a few specs and found that the standard primes used for Diffie-Hellman key exchange or in DSA are not safe-primes (http://en.wikipedia.org/wiki/Safe_prime). DH: None of primes in rfc5114 are safe primes DSA: FIPS-186-3 (page 15) recommends the order of group to be much smaller than prime size - for example, for 1024 bit prime, order of group should be 160 Why is this so ? Isn't it desirable for the order of the group to be as high as possible to make computation of discrete logarithm hard ? -Rahul __ OpenSSL Project http://www.openssl.org User Support Mailing Listopenssl-users@openssl.org Automated List Manager majord...@openssl.org
Openssl Error Code Translation
Hi, Can anybody tell how can I translate Openssl Error code to error description. I am calling ERR_peak_last_error(). The error code that I am receiving is b901. Is this a valid error code. How can I verify it. Thanks Tanu
Revoking DER certificate
Hello, could somebody tell me if it is possible to revoke a certificate which is in DER format, with the openssl ca command ? Or do I have to convert it to PEM format first ? I only succeeded to revoke PEM certificates, and I see no parameter for specifying the format of the certificate file. Gerald
openssl connection problem...
Hello, I'm new to this list, so I hope this is the correct place to post this problem. I'm trying to use openssl to connect to postgres. The process is not working. When I try to connect using s_client without any of the postgres bits, I get an error message as follows: walt...@cat:~$ openssl s_client -connect db:5433 CONNECTED(0005) 12210:error:140790E5:SSL routines:SSL23_WRITE:ssl handshake failure:../../../../common/openssl/ssl/s23_lib.c:226: I issued the same command with the debug option and get an error as follows: walt...@cat:~$ openssl s_client -debug -connect db:5433 CONNECTED(0005) write to 0008C418 [0008F170] (142 bytes = 142 (0x8E)) - 80 8c 01 03 01 00 63 00-00 00 20 00 00 39 00 00 ..c... .. 9.. 0010 - 38 00 00 35 00 00 16 00-00 13 00 00 0a 07 00 c0 8..5 0020 - 00 00 33 00 00 32 00 00-2f 03 00 80 00 00 66 00 .. 3..2../.f. 0030 - 00 05 00 00 04 01 00 80-08 00 80 00 00 63 00 00 .c.. 0040 - 62 00 00 61 00 00 15 00-00 12 00 00 09 06 00 40 b..a...@ 0050 - 00 00 65 00 00 64 00 00-60 00 00 14 00 00 11 00 ..e..d..`... 0060 - 00 08 00 00 06 04 00 80-00 00 03 02 00 80 0b fd 0070 - 56 53 2f a4 76 0b 02 c4-d9 fd 4e fd 06 fa 3b 65 VS/.v.N...;e 0080 - b4 9c 5f fb 8d 6b 25 5b-68 aa b3 90 ec d7 .._..k%[h. read from 0008C418 [000946D0] (7 bytes = 0 (0x0)) 12245:error:140790E5:SSL routines:SSL23_WRITE:ssl handshake failure:../../../../common/openssl/ssl/s23_lib.c:226: Is there a verbose command that will give me more information? While the hex dump is a lot of detailed information, I don't what it's telling me. Thank you for your help. Carol Walter __ OpenSSL Project http://www.openssl.org User Support Mailing Listopenssl-users@openssl.org Automated List Manager majord...@openssl.org
Re: Multiple CRL with same issuer
On Wed, Jan 28, 2009, PS wrote: Hi All, I was under the impression that openssl allows loading multiple CRLs for the same issuer. But, this does not seem to be the case as is proved by using openssl verify. $ ls -l ./ca/ total 24 lrwxrwxrwx 1 pshah users 10 Jan 28 21:56 ba4bb3b6.0 - cacert.pem - the CA cert lrwxrwxrwx 1 pshah users 14 Jan 28 21:56 ba4bb3b6.r0 - revoked_48.pem revokes only cert48.pem lrwxrwxrwx 1 pshah users 14 Jan 28 21:56 ba4bb3b6.r1 - revoked_49.pem - revokes only cert49.pem -rw-r--r-- 1 pshah users 1233 Jan 28 17:09 cacert.pem -rw-r--r-- 1 pshah users 560 Jan 28 17:10 revoked_48.pem -rw-r--r-- 1 pshah users 560 Jan 28 17:10 revoked_49.pem $ openssl verify -CApath ./ca/ -crl_check -verbose cert49.pem cert49.pem: OK $ openssl verify -CApath ./ca/ -crl_check -verbose cert48.pem cert48.pem: /C=--/ST=California/L=San Francisco/O=Riverbed Technology, Inc./OU=Steelhead/CN=hw1-sh18/emailaddress=fakeem...@example.com error 23 at 0 depth lookup:certificate revoked 29615:error:0B07D065:x509 certificate routines:X509_STORE_add_crl:cert already in hash table:x509_lu.c:418: So, as seen above, the second CRL is not loaded (and I have confirmed this with gdb.). OpenSSL 0.9.9-dev has additional CRL support not found in 0.9.8. It includes support for loading multiple CRLs with the same issuer name. Steve. -- Dr Stephen N. Henson. Email, S/MIME and PGP keys: see homepage OpenSSL project core developer and freelance consultant. Homepage: http://www.drh-consultancy.demon.co.uk __ OpenSSL Project http://www.openssl.org User Support Mailing Listopenssl-users@openssl.org Automated List Manager majord...@openssl.org
RE: Multiple CRL with same issuer
thanks, kyle, for pointing that out about the issuing distribution point. http://tools.ietf.org/html/rfc5280#section-5.2.5 so if i read that section correctly, the issuing distribution point extension is THE way to specify scope as you mentioned. so two distinct CRLs from the same issuer can be simultaneously valid/active (as long as they have different issuing distribution point extensions). that's what you were saying right? so no, in our case, the two CRLs do NOT have the issuing distribution point extensions. i notice they also happen to be v1. any way, dr henson has said 0.9.9-dev includes support for loading multiple CRLs with the same issuer name. thanks. Date: Thu, 29 Jan 2009 02:12:29 -0800 Subject: Re: Multiple CRL with same issuer From: aerow...@gmail.com To: openssl-users@openssl.org (First: I'm sorry. I misunderstood something I read in the OpenSSL documentation. CRLs are always V2 according to RFC5280.) I have not heard of the ability to specify or process multiple scopes in OpenSSL; however, have you verified that the CRL Extension Issuing Distribution Point is different between the two CRLs? This is where different scopes are specified (section 5.2.5 of RFC 5280). -Kyle H 2009/1/29 Kyle Hamilton : I think you're trying to assume something that cannot be assumed: you assume that ALL unexpired CRLs are considered. This is not the case. As Dominiqué said, only the CRL that has the latest signature time is considered. This is evident in the name of the file type: Certificate Revocation *List*. It is legal to issue a CRL that revokes a certificate (possibly with an type of onhold, for V3 CRLs) with an expiration time of 2 years in the future, and the next hour the to remove the revocation status. If all simultaneously-valid CRLs are considered, then the intended consequence of unrevoking the certificate would be impossible. This is why the CRL must contain the *complete* list of *all* revoked certificates which have not yet expired. There is a PKIX extension, delta CRLs, which defines for V3 CRLs a way to allow for adding to the list of the most-recently-issued full CRL. In order to support unrevocation, there is a special status type (called remove_from_crl) for the delta CRL which is to be interpreted as removing the certificate from the revocation list; however, in a full V3 CRL, that status type is illegal. And in V2 CRLs (the default, since many implementations do not handle V3 CRLs) there is no means of specifying the extension that contains a status type regardless. This is specified in PKIX (currently RFC 5280); in order to maintain standards-conformance OpenSSL cannot change this behavior. (Nor can it even offer an option to change it, since its job is to maintain security-system interoperability, not capriciously make it less secure.) -Kyle H 2009/1/29 Giang Nguyen : I was under the impression that openssl allows loading multiple CRLs for the same issuer. But, this does not seem to be the case as is proved by using openssl verify. $ ls -l ./ca/ total 24 lrwxrwxrwx 1 pshah users 10 Jan 28 21:56 ba4bb3b6.0 - cacert.pem - the CA cert lrwxrwxrwx 1 pshah users 14 Jan 28 21:56 ba4bb3b6.r0 - revoked_48.pem revokes only cert48.pem lrwxrwxrwx 1 pshah users 14 Jan 28 21:56 ba4bb3b6.r1 - revoked_49.pem - revokes only cert49.pem -rw-r--r-- 1 pshah users 1233 Jan 28 17:09 cacert.pem -rw-r--r-- 1 pshah users 560 Jan 28 17:10 revoked_48.pem -rw-r--r-- 1 pshah users 560 Jan 28 17:10 revoked_49.pem $ openssl verify -CApath ./ca/ -crl_check -verbose cert49.pem cert49.pem: OK $ openssl verify -CApath ./ca/ -crl_check -verbose cert48.pem cert48.pem: /C=--/ST=California/L=San Francisco/O=Riverbed Technology, Inc./OU=Steelhead/CN=hw1-sh18/emailaddress=fakeem...@example.com error 23 at 0 depth lookup:certificate revoked 29615:error:0B07D065:x509 certificate routines:X509_STORE_add_crl:cert already in hash table:x509_lu.c:418: A CRL ( Certificat revocation list) is the list of ALL the revoked certificates at the time it is issued So if at time t1 a certificate 48 is revoked then all the subsequent CRLs MUST indicate that the certificate 48 as revoked If later at time t2 the certificate 49 is revoked hen all the subsequent CRLs MUST indicate that both certificate 48 and certificate 49 arte revoked Thus only the lasT CRL has to considered . Since the delivery times of the CRLs are close together it is not easy to check into the example which is ithe last CRL i think you misunderstood the question. the issue at hand is not about older and latest copies of a particular (certificate revocation) list, but it is about two *distinct* simultaneously valid and active (certificate revocation) lists that are issued/maintained by the same issuer. http://tools.ietf.org/html/rfc5280#section-5 Each CRL has a particular scope. The CRL scope is the set of
Re: block type is not 01
On Thu, Jan 29, 2009 at 06:15:04AM -0500, Georges-Etienne Legendre wrote: It works with what you suggested. Apache is running on a Linux box. Is there something to set in Apache to resolve this? Yes, give it a set of non-broken 3DES ciphersuites. None of the below work: $ openssl ciphers -v '3DES+SSLv3:!aDSS:@STRENGTH' ADH-DES-CBC3-SHASSLv3 Kx=DH Au=None Enc=3DES(168) Mac=SHA1 EDH-RSA-DES-CBC3-SHASSLv3 Kx=DH Au=RSA Enc=3DES(168) Mac=SHA1 DES-CBC3-SHASSLv3 Kx=RSA Au=RSA Enc=3DES(168) Mac=SHA1 I don't know how this Apache managed to break these, but it certainly did. Perhaps it can't deal with non-stream ciphers that require padding, and miscalculates packet sizes... -- Viktor. __ OpenSSL Project http://www.openssl.org User Support Mailing Listopenssl-users@openssl.org Automated List Manager majord...@openssl.org
Privat key storage
Hi, I found that the private key is stored unencrypted in memory. Is there a way to configure a session so that the private key is not stored in memory but read and decrypted from the associated PEM file (using the callback set with SSL_CTX_set_default_passwd_cb) each time it is needed? Thank you, Regards Olivier Laissac
RE: openssl connection problem...
Hi Carol, I believe you can add -state as a parameter to the client and server side to see what phase things are happening in. Kevin. -Original Message- From: owner-openssl-us...@openssl.org [mailto:owner-openssl-us...@openssl.org] On Behalf Of Carol Walter Sent: Thursday, January 29, 2009 11:28 AM To: openssl-users@openssl.org Subject: openssl connection problem... Hello, I'm new to this list, so I hope this is the correct place to post this problem. I'm trying to use openssl to connect to postgres. The process is not working. When I try to connect using s_client without any of the postgres bits, I get an error message as follows: walt...@cat:~$ openssl s_client -connect db:5433 CONNECTED(0005) 12210:error:140790E5:SSL routines:SSL23_WRITE:ssl handshake failure:../../../../common/openssl/ssl/s23_lib.c:226: I issued the same command with the debug option and get an error as follows: walt...@cat:~$ openssl s_client -debug -connect db:5433 CONNECTED(0005) write to 0008C418 [0008F170] (142 bytes = 142 (0x8E)) - 80 8c 01 03 01 00 63 00-00 00 20 00 00 39 00 00 ..c... .. 9.. 0010 - 38 00 00 35 00 00 16 00-00 13 00 00 0a 07 00 c0 8..5 0020 - 00 00 33 00 00 32 00 00-2f 03 00 80 00 00 66 00 .. 3..2../.f. 0030 - 00 05 00 00 04 01 00 80-08 00 80 00 00 63 00 00 .c.. 0040 - 62 00 00 61 00 00 15 00-00 12 00 00 09 06 00 40 b..a...@ 0050 - 00 00 65 00 00 64 00 00-60 00 00 14 00 00 11 00 ..e..d..`... 0060 - 00 08 00 00 06 04 00 80-00 00 03 02 00 80 0b fd 0070 - 56 53 2f a4 76 0b 02 c4-d9 fd 4e fd 06 fa 3b 65 VS/.v.N...;e 0080 - b4 9c 5f fb 8d 6b 25 5b-68 aa b3 90 ec d7 .._..k%[h. read from 0008C418 [000946D0] (7 bytes = 0 (0x0)) 12245:error:140790E5:SSL routines:SSL23_WRITE:ssl handshake failure:../../../../common/openssl/ssl/s23_lib.c:226: Is there a verbose command that will give me more information? While the hex dump is a lot of detailed information, I don't what it's telling me. Thank you for your help. Carol Walter __ OpenSSL Project http://www.openssl.org User Support Mailing Listopenssl-users@openssl.org Automated List Manager majord...@openssl.org __ OpenSSL Project http://www.openssl.org User Support Mailing Listopenssl-users@openssl.org Automated List Manager majord...@openssl.org
RE: PBE, keystore questions
From: owner-openssl-us...@openssl.org On Behalf Of A Taylor Sent: Wednesday, 28 January, 2009 10:44 I am currently using the PKCS5 openssl function for PBE. Currently I have the values of the password, salt and iterations hardcoded in my example but I want to avoid this. Is there an openssl implementation of a key store or something similar? For the key store, how do i create one? Are there openssl functions to access the key store? Or is there some other construct I could use? Not really. openssl by itself can store a privatekey in a file under PBE (or in clear, which of course does not help security). (Also openssl can store in clear other things, like cert, that don't need security so this is not an issue. But still it's just a file.) Anything on top of that you have to build yourself or find elsewhere. If you did have a secure keystore, you could just store a privatekey (or secretkey) in it directly. Unless you're just being compatible with some other (existing) system or procedure, PBE is normally useful when you want a person to provide the password and thus control the key. Finally, is there an openssl function similar to memset that I could use to null out the password, salt and generated key from memory when I'm done with them? OPENSSL_cleanse in crypto.h It's not clear if salt is really sensitive and needs to be cleansed, but it doesn't hurt. (IVs are somewhat analagous, and are exposed.) You should cleanse any other sensitive data as well, such as cleartext after encryption (sent) or processing (received). __ OpenSSL Project http://www.openssl.org User Support Mailing Listopenssl-users@openssl.org Automated List Manager majord...@openssl.org
RE: Openssl Error Code Translation
From: owner-openssl-us...@openssl.org On Behalf Of tanu dutt Sent: Thursday, 29 January, 2009 08:31 Can anybody tell how can I translate Openssl Error code to error description. I am calling ERR_peak_last_error(). The error code that I am receiving is b901. Is this a valid error code. How can I verify it. I assume that's a typo and you mean 'peek'. That value is in the ERR_LIB_USER range, so it's up to your application. If it has (set-up and) done the appropriate ERR_load_strings, then ERR_error_string and friends should expand/explain it for you. __ OpenSSL Project http://www.openssl.org User Support Mailing Listopenssl-users@openssl.org Automated List Manager majord...@openssl.org
Re: Revoking DER certificate
If '-inform DER' doesn't work as an option to openssl ca, then use the command: openssl x509 -inform der -outform pem -in YOURCERTFILEHERE.der -out YOUROUTPUTFILEHERE.pem This will convert it to PEM encoding so that you can perform your revocation process on it. -Kyle H On Thu, Jan 29, 2009 at 8:05 AM, Gerald Iakobinyi-Pich nutri...@gmail.com wrote: Hello, could somebody tell me if it is possible to revoke a certificate which is in DER format, with the openssl ca command ? Or do I have to convert it to PEM format first ? I only succeeded to revoke PEM certificates, and I see no parameter for specifying the format of the certificate file. Gerald __ OpenSSL Project http://www.openssl.org User Support Mailing Listopenssl-users@openssl.org Automated List Manager majord...@openssl.org
Openssl signature verification
Dear All, In openssl API X509_verify(X509 *a, EVP_PKEY *r) is used to verify the signature of certificate. I have some doubt please help me. 1. Is in this API we are passing the CA certificate and public key of CA certificate? 2. What is data over SSL compute the HASH? 3. SSL will decrypt the CA signature (Which is on CA certificate bundle)? 4. Decrypted CA Signature will match to above HASH.(query 2)? Please tell me. Thank you. Regards, --Ajeet Kumar Singh
Issue related to Finger print
Dear All, In Openssl for signature verification we are using API ASN1_item_verify(). Let me know the data which is used for finger print (signature) creation is the CA public key or some thing else data . Please clarify this doubt. How we are verifying the signature? Thank you. Regards, --Ajeet Kumar Singh
