Re: OpenSSL 0.9.6 and shared libraries

From: Albert Chin-A-Young [EMAIL PROTECTED] china I'm building OpenSSL 0.9.6 with shared libraries for Solaris, HP-UX, china IRIX, and Digital UNIX. HP-UX and IRIX are not currently supported so china we'll be adding support. A few questions though: china 1. Any reason libtool was not chosen?

[PATCH] apps/ca.c

Here are the diffs I mentioned in an earlier email. To recap: adds the -notext option to the usage info adds the -nodb option to avoid recording the cert in the database adds the -mins option to specify cert expiration in minutes adds the -find DN option to printthe pathname of a cert

Bug in openssl 0.9.6 for certificate verification

I have some code that I could use to verify certificate, and that's not able to do it anymore when compiled with 0.9.6 I traced this to the following line (330) in the file by_dir.c This line has been changed from 0.9.5 to 0.9.6. I think the last argument in the call to sk_X509_OBJECT_value

Re: OpenSSL 0.9.6 and shared libraries

From: Albert Chin-A-Young [EMAIL PROTECTED] china I've attached the patch I'm working with at the moment. It's a work in china progress. The patch adds support for building shared libraries on china IRIX. I'll save that patch to be at least an inspiration for what I do :-). china A downside is

Re: OpenSSL 0.9.6 and shared libraries

On Fri, Oct 13, 2000 at 05:59:35PM +0200, Richard Levitte - VMS Whacker wrote: From: Albert Chin-A-Young [EMAIL PROTECTED] china Also, why do you '-L. -lcrypto' when building libssl.so? The china shared library version of libssl should mimick the static china version. I'm expressing a

Re: Bug in openssl 0.9.6 for certificate verification

Jean-Marc Desperrier wrote: I have some code that I could use to verify certificate, and that's not able to do it anymore when compiled with 0.9.6 I traced this to the following line (330) in the file by_dir.c This line has been changed from 0.9.5 to 0.9.6. I think the last argument in

PKCS12 modes

PKCS#12 specifies two privacy (password and public-key) and two integrity (password and public-key) modes. However, it appears as though OpenSSL implements only the PKCS#12 password privacy mode. Or have I simply overlooked something here? Are there any plans to implement the other modes?

Re: OpenSSL 0.9.6 and shared libraries

From: Albert Chin-A-Young [EMAIL PROTECTED] china That's because libc is shared. So, that means the symbolic china links have to be created during build time I guess. Exactly. -- Richard Levitte \ Spannvägen 38, II \ [EMAIL PROTECTED] Chairman@Stacken \ S-168 35 BROMMA \ T: +46-8-26 52

RE: Serial number 00

Using that config file go into the ./apps/demoCA directory and edit the serial file and put in whatever number you want. Mike -Original Message- From: Sergey Badaev [mailto:[EMAIL PROTECTED]] Sent: Friday, October 13, 2000 4:32 PM To: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL

Re: OpenSSL 0.9.6 and shared libraries

From: Albert Chin-A-Young [EMAIL PROTECTED] china Are you updating CVS with your changes. I'm going to start tracking china CVS via rsync and want to keep in sync with what you are doing. I'm one of the developers, so the answer is yes. -- Richard Levitte \ Spannvägen 38, II \ [EMAIL

ftime, times, gettimeofday and getrusage

There are a number of time fetching functions out there, some obsoleted by others: ftime() is obsoleted by gettimeofday() under BSD 4.2. gettimeofday() is defined in SVr4 and BSD4.3. They are both used to find out actual time since 1970-01-01 down to at least a millisecond. times()