Re: bad characters encoded on ssl logs coming from x509 cert

On Tue, Apr 27, 2010 at 5:29 PM, Luis Neves wrote: > > As I think they are in DER format so I use > openssl x509 -inform DER -in xx.cer -noout -text I was able to get it to output the characters correctly by adding "-nameopt multiline,utf8,-esc_msb" to the command-line. It makes me wonder th

RE: bad characters encoded on ssl logs coming from x509 cert

Hello Steve, and thanks for the reply, How can I find out what on my system (and Ive created two different machines with same problem) is making this behaviour? can you give me some help or clue? Im following all the howtos and docs in the Net on how to setup apache+mod_ssl+mod_authz_ldap+open

Re: non-blocking problem

On Tue, Apr 27, 2010, piper.guy1 wrote: > Hi again, > > I'm trying to follow the instructions in the OpenSSL reference book, > and their example code from their site for setting a socket to > 'non-blocking'. > > Before I made any changes, I was working with good code that was > making secure con

non-blocking problem

Hi again, I'm trying to follow the instructions in the OpenSSL reference book, and their example code from their site for setting a socket to 'non-blocking'. Before I made any changes, I was working with good code that was making secure connections with no problems. Essentially: bio = BIO_new_

Problem making openssl0.9.8n in solaris 10

I got this problem when making the openssl. I think its related with the gcc libs, but I'm not sure. making all in crypto/rand... gcc -I.. -I../.. -I../../include -fPIC -DOPENSSL_PIC -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -m32 -mcpu=ultrasparc -O3 -fomit-frame-pointer -Wall -D

remove

This communication is intended only for use by the addressee(s) named herein and may contain business confidential and/or legally privileged information. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution, disclosure or copying o

Re: Verisign client requirements

Thanks for your help David. Regards, /carl h. On Tue, Apr 20, 2010 at 9:54 PM, David Schwartz wrote: > > Piper Guy1 wrote: > >> > This is precisely what a browser does. Again, using the >> > "https://www.amazon.com"; example, OpenSSL takes care of getting the >> > certificate from the server, ma

Re: Verisign client requirements

It most certainly did Rene. Thanks for the complete response. Now I have to go away and digest it :-) Regards, /carl h. On Mon, Apr 19, 2010 at 5:12 PM, Rene Hollan wrote: > I think you need a tutorial in how X.509 hierarchies and chains of trust > work. > > Consider a public and private key pa

Re: bad characters encoded on ssl logs coming from x509 cert

On Tue, Apr 27, 2010, Luis Neves wrote: > Hi to all, > > I have this data on ssl_error_log, coming from a client certificate > > [Fri Apr 23 14:13:26 2010] [debug] ssl_engine_kernel.c(1219): > Certificate Verification: depth: 2, subject: /CN=Cart\\xC3\\xA3o de > Cidad\\xC3\\xA3o 001/OU=ECEstado

bad characters encoded on ssl logs coming from x509 cert

Hi to all, I have this data on ssl_error_log, coming from a client certificate [Fri Apr 23 14:13:26 2010] [debug] ssl_engine_kernel.c(1219): Certificate Verification: depth: 2, subject: /CN=Cart\\xC3\\xA3o de Cidad\\xC3\\xA3o 001/OU=ECEstado/O=SC EE - Sistema de Certifica\\xC3\\xA7\\xC3\\xA3o El

PR_USER_X509_CERTIFICATE details

Hi, I am trying to import an outlook PST file to my application running on Mac OS X. The PST file consists of contacts created in Outlook. The contacts have X509 certificates added to them. The problem I am facing is ASN decoding of the certificate fails. I have read somewhere that there is extr