obj_dat.c doesn't compile

Since a few days back, crypto/objects/obj_dat.c doesn't compile. Here are the errors from gcc: 2112: error: `NID_id_GostR3410_94_cc' undeclared here (not in a function) 2112: error: initializer element is not constant 2112: error: (near initialization for `nid_objs[797].nid') 2113: error:

Re: obj_dat.c doesn't compile

On Sat, Apr 08, 2006, Gisle Vanem wrote: Since a few days back, crypto/objects/obj_dat.c doesn't compile. Here are the errors from gcc: 2112: error: `NID_id_GostR3410_94_cc' undeclared here (not in a function) 2112: error: initializer element is not constant 2112: error: (near

Re: [openssl.org #1313] openssl on HP UX 11.00

Patrick, You could be using Connect:Direct from Sterling Commerce, this automated file transfer package uses OpenSSL on Unix and the IBM toolkit on zOS. JohanPatrick Hsu via RT [EMAIL PROTECTED] wrote: Good morning:We are trying to provide secured communications between HP server K360/K580( o/s

RE: using /dev/random /dev/urandom

1. When using OpenSSL for signing data, and for SSL sessions (both client side and server side), should I use the /dev/random instead? IMO, if you're using the random data just to seed a PRNG, there is no rational reason to insist on using /dev/random instead of /dev/urandom. The only