supporting "smime-signed" receipts as per RFC 2634

2006-08-30 Thread hauser
Hi, It would be great to have an additional parameter to create the request for such a receipt in "openssl smime -sign" as per http://www.faqs.org/rfcs/rfc2634.html chapter 2. It seems that MS-Outlook can do this since a while. Others seem to have struggled with validating such "smime-signed"

RE: ocsp response validation problem

2006-08-30 Thread Fitzsimons, Nick
Hi, From my work in this area, I found that the error at the end of the ocsp command is only a problem with the running of the command - the contents of the file produced are not impacted. However, the way to avoid the error is to concatenate (doing it in a text editor is fine) all the certs

EAP-TLS certs

2006-08-30 Thread Teo
Hi, I have need of certs for 3 clients, for some tests on freeradius with a sniffer that it capture the input. Therefore I want certs of test the type which already use, generated with the script CA.all inside freeradius-1.1.2 sources. How I can make 3 certs for distinct for the clients? Is it pos

EAP-TLS certs

2006-08-30 Thread Teo
Hi, I have need of certs for 3 clients, for some tests on freeradius with a sniffer that it capture the input. Therefore I want certs of test the type which already use, generated with the script CA.all inside freeradius-1.1.2 sources. How I can make 3 certs for distinct for the clients? Is it pos

How to get the reason for rovocation in CRL Validation?

2006-08-30 Thread surendra.ande
Hi, I am using openssl 0.9.8b. I am doing CRL validation. In that process, I got the CRL status thru the following API: API: sk_X509_REVOKED_find(crl->crl->revoked, &rtmp). After that, I need find out the reason for revocation. I am using the API X509_REVOKED_get_ext_d2i(&rtmp, NID_crl_reason,

ocsp response validation problem

2006-08-30 Thread Simon McMahon
Hi, 0.9.8b I'm doing some OCSP testing and I had a little confusion with OCSP response validation. If you leave out -CAfile on the request then the validation fails even in the simple case where the CA is the same as the issuer. The examples in the ocsp(1) doc should include a request that in

Re: EAP-TLS certs

2006-08-30 Thread Abhijit Rao
> > Someone knows gives me of the information also on the guides who > can help me? > Thousand thanks for all > > Matteo ;-) > The certs can be prepared without using CA.all - which is what I did. Two command (.bat or shell scripts) files - one used to create self-issued CA and the other to

EAP-TLS certs

2006-08-30 Thread Teo
Hi, I have need of certs for 3 clients, for some tests on freeradius with a sniffer that it capture the input. Therefore I want certs of test the type which already use, generated with the script CA.all inside freeradius-1.1.2 sources. How I can make 3 certs for distinct for the clients? Is it pos

Re: SMIME_read_PKCS7 fails with memory BIO but works with file BIO

2006-08-30 Thread Marco Roeland
On Tuesday August 29th 2006 at 14:18 Heikki Toivonen wrote: > I am trying to use SMIME_read_PKCS7 to read a signed and encrypted MIME > message from memory BIO, but I can't get it to work. It works fine if I > construct a file BIO to read from. Am I doing something wrong, or is > this a bug? > >

Re: Validating Cert Chain

2006-08-30 Thread Marek Marcola
Hello, > i have a question about this following method > > int X509_STORE_CTX_init(X509_STORE_CTX *ctx, X509_STORE *store, >X509 *x509, STACK_OF(X509) *chain); > > if i understand this correctly the argument 'x509' is the cert that u want > to be verified & the 'chain' is

Re: BIO and DTLS

2006-08-30 Thread Marek Marcola
Hello, > Can anyone tell me if the behavior of the BIO_new_accept, BIO_do_accept, > and BIO_read functions changes in any way while using DTLS? DTLS works over UDP so BIO_do_accept has no usage. Internally DTLS works on BIO created with BIO_new_dgram() and uses BIO_read() on that BIO (ssl3_read_n(

Re: Unable to locate the keystore/certificate store or private key

2006-08-30 Thread Marek Marcola
Hello, > The basic succession of calls are as follows. I think the program > waits for an ssl_read or ssl_write to implicitly trigger the handshake > process. > > meth = TLSv1_client_method() > > SSL_load_error_strings(); > SSLeay_add_ssl_algorithms(); > SSL_CTX_new(meth); > > > ssl = SSL_