Actually, I'd prefer that I wouldn't have to relink and redistribute my application
every
time a security patch comes out for OpenSSL. I haven't seen any issues in our
application
upgrading from 0.9.6 to 0.9.7 using this non version technique on our local
development nodes.
The version techn
In message <[EMAIL PROTECTED]> on Mon, 27 Jan 2003 22:40:24
+0100 (MET), " via RT" <[EMAIL PROTECTED]> said:
rt> Currently, on many Unix platforms I link my application against
rt> libssl.so and libcrypto.so. Typically, these are links set to resolve
rt> down to the versioned types of these fi
In message <[EMAIL PROTECTED]> on Mon, 27 Jan 2003 22:40:24
+0100 (MET), " via RT" <[EMAIL PROTECTED]> said:
rt> Currently, on many Unix platforms I link my application against
rt> libssl.so and libcrypto.so. Typically, these are links set to resolve
rt> down to the versioned types of these fil
On Mon, Jan 27, 2003, Michael Helm wrote:
> There are many certs in production use with policy extensions; the VeriSign
> end entity certs should provide many examples.
>
Yes I know about those. Is there any documentation however on what the
VeriSign policy extensions actually *mean*. The last t
Currently, on many Unix platforms I link my application against
libssl.so and libcrypto.so. Typically, these are links set to resolve
down to the versioned types of these files, like libssl.so.0.9.7 and
libcrypto.so.0.9.7. The internal names of these shared objects
include the major and minor
In the original 0.9.7 release there also seems to be some configuration
remnants left in the crypto/objects directory -- obj_dat.h; this isn't
removed by a "make clean".
\nick
__
OpenS
"Dr. Stephen Henson" writes:
> > 3. If there is no reference test suite available, should it be assumed
> > that there exists no tested, and, therefore with high probability no
> > correct, implementation of the certification path validation algorithm
> > which handles the policy mappings and name
I've checked over the snapshot that was current on or about 14-Jan-2003.
It builds OK.
In the original 0.9.7.tar.gz there were symbolic links already present
in include/openssl, and they are not removed by make clean. In the
snapshot the links are not present.
Script started on Mon Jan 27 10:1
hi,
I'm using 0.9.7 under Linux 2.4 series.
you should add a "uninstall" rule within Makefile, usefull when have to
use different versions of Ossl.
make install: to install
make uninsal: to remove
thx
vg
__
OpenSSL Project
