[openssl.org #576] wtls certificate
Hi ! I am asking you about the possibility of intergrating the wtls certificates in the certificates formats supported by the openssl. Could you tell me how can i add this format to be supported? Thank you! ___ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com __ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
[openssl.org #576] wtls certificate
[EMAIL PROTECTED] - Sat Apr 12 21:49:41 2003]: Hi ! I am asking you about the possibility of intergrating the wtls certificates in the certificates formats supported by the openssl. Could you tell me how can i add this format to be supported? Thank you! I have worked on these things but the code is proprietary. The WTLS certificate format is a very weird beast that bears no resemblance to anything currently in OpenSSL, it doesn't even use ASN1! Well there's a bit that can be ASN1 but not much else. This would mean that its routines would have to be developed separately and integrating support into things like 'ca' would be messy. Steve. __ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
[openssl.org #550] bug report - library and header version mismatch
[EMAIL PROTECTED] - Thu Mar 27 22:04:39 2003]:
I just had a look at your testing script, and I believe it has a flaw in this part:
#
# Search for shared libraries (libcrypto and libssl).
# Relies on shared libraries looking like libcrypto.s*
#
echo Searching for and checking OpenSSL shared libraries
(libcrypto.s*, libssl.s*).
libraries=`find $1 -follow -name 'libcrypto.s*' -print 2/dev/null`
for lib in $libraries
do
echo Trying libcrypto $lib findssl.log
${CC} -o conftest conftest.c $lib 2findssl.log
if [ -x ./conftest ]
then
ver=`./conftest 2/dev/null`
rm -f ./conftest
echo $ver $lib
fi
done
echo
When you execute ./conftest, you have no control over which libcrypto.so it uses.
Unless you have an environment variable LD_LIBRARY_PATH with '.' as one of the
directories when you run that script in the OpenSSL directory, it's very likely you
will pick up /usr/lib/libcrypto.so. How about inserting the command 'ldd ./conftest'
before the 'ver=...' line and see what exactly is loaded?
--
Richard Levitte
[EMAIL PROTECTED]
__
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
[openssl.org #550] bug report - library and header version mismatch
[levitte - Sun Apr 13 00:29:12 2003]:
[EMAIL PROTECTED] - Thu Mar 27 22:04:39 2003]:
I just had a look at your testing script, and I believe it has a flaw
in this part:
#
# Search for shared libraries (libcrypto and libssl).
# Relies on shared libraries looking like libcrypto.s*
#
echo Searching for and checking OpenSSL shared libraries
(libcrypto.s*, libssl.s*).
libraries=`find $1 -follow -name 'libcrypto.s*' -print 2/dev/null`
for lib in $libraries
do
echo Trying libcrypto $lib findssl.log
${CC} -o conftest conftest.c $lib 2findssl.log
if [ -x ./conftest ]
then
ver=`./conftest 2/dev/null`
rm -f ./conftest
echo $ver $lib
fi
done
echo
When you execute ./conftest, you have no control over which
libcrypto.so it uses. Unless you have an environment variable
LD_LIBRARY_PATH with '.' as one of the directories when you run
that script in the OpenSSL directory, it's very likely you will
pick up /usr/lib/libcrypto.so. How about inserting the command
'ldd ./conftest' before the 'ver=...' line and see what exactly is
loaded?
Just made a test. The 'ver=...' line needs to look like this:
ver=`LD_LIBRARY_PATH=.:$LD_LIBRARY_PATH ./conftest 2/dev/null`
--
Richard Levitte
[EMAIL PROTECTED]
__
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
