RE: Multiple Threads accessing an SSL connection

Hey Thanks a lot for the answer David. Sanjay --- David Schwartz <[EMAIL PROTECTED]> wrote: > > >I read many posts about multiple threads > accessing > > a single SSL connection for read/write. I am still > > confused about the usage. What exactly is the > truth? > > You cannot access

Multiple Threads accessing an SSL connection

cause a problem?? If yes, then can I make use of mutex locks to allow only one thread access the SSL connection (for read/write) at a time??? If no, I am happy :) Thanks in advance, Sanjay Acharya Wichita State University __ Celebrate

Re: setting certificate expiry to more than 30 days

But Ted, if I have to use -days option then why do we need to specify "default_days" name-value pairs in the openssl.cnf? :( Sanjay Acharya Wichita State University --- Bernhard Froehlich <[EMAIL PROTECTED]> wrote: > Sanjay Acharya wrote: > > >Hello. I am pos

setting certificate expiry to more than 30 days

is generated fine with the x509 and -days 365 option. Can someone help me on this. Sanjay Acharya Wichita State University ---THE openssl.cnf FILE--- RANDFILE= $ENV::HOME/project/.rnd [ ca ] default_ca = my_ca_default [ my_ca_default ] dir = $ENV::HOME/project certs

Re: default_days problem

14:21:54 2005 GMT notAfter=Mar 30 14:21:54 2005 GMT I have the default_days set as default_days= 365 in my default_ca What could be the problem? The certificate is generated fine with the x509 option as mentioned in my earlier mail. Thanks in advance, Sanjay Acharya Wichita State Unive

default_days problem

e why this is happening? Is it because I am using "req" option. I am pasting my openssl.cnf below. The expiry date shows fine if I run the above command with the "-days = 365" option. Thanks in advance, Sanjay Acharya Wichita State University RANDFILE= $ENV::HOME