Hi
In non-blocking mode, for client we call
SSL_connect
In case SSL_connect returns -1 with SSL_ERROR_WANT_READ u need to wait
in Select and once the sock fd is readable, u again need to all
SSL_connect till the SSL_connect returns success or some other error
code (except read or write wait)..
Hello openssl-users,
:D
I knew it must be trivial!
In case someone (as lame as me) needs an example:
#include unix.h
#include sys/stat.h
#include openssl/rsa.h
#include openssl/ssl.h
#include openssl/evp.h
#include openssl/bio.h
#include openssl/bn.h
#include openssl/pem.h
int
main( int
Hello,
printf( pubmod==%s\n, BN_bn2dec( ca_rsa-n ) );
printf( pubexp==%s\n, BN_bn2dec( ca_rsa-e ) );
printf( privexp==%s\n, BN_bn2dec( ca_rsa-d ) );
I think that BN_bn2hex() is more portable, readable, ...
But you should be aware that BN_bn2dec()/BN_bn2hex() allocates
Hello Marek,
Monday, August 14, 2006, 9:48:56 PM, you wrote:
printf( pubmod==%s\n, BN_bn2dec( ca_rsa-n ) );
printf( pubexp==%s\n, BN_bn2dec( ca_rsa-e ) );
printf( privexp==%s\n, BN_bn2dec( ca_rsa-d ) );
I think that BN_bn2hex() is more portable, readable, ... But you
Hello,
Monday, August 14, 2006, 9:48:56 PM, you wrote:
printf( pubmod==%s\n, BN_bn2dec( ca_rsa-n ) );
printf( pubexp==%s\n, BN_bn2dec( ca_rsa-e ) );
printf( privexp==%s\n, BN_bn2dec( ca_rsa-d ) );
I think that BN_bn2hex() is more portable, readable, ... But you
We were looking to upgrade to latest and greatest of OpenSSL to plug what we
thought were vulnerabilities. We are running 0.9.7a, according to when we
pass the 'version' flag. However, according to RedHat the package we have
installed, via up2date, is patched to cover the latest vulnerabilities
My inclination is to believe a vendor when they say things like it's XXX
version n, with all known vulnerability fixes thru version n+m
Vendors often do this kind of thing, for the same reason you don't want to
upgrade RHEL installations.
/r$
--
SOA Appliances
Application Integration
Hi,
I have problems displaying a special kind of X509 certificate.
X509_print() returns without error, but afterwards the error stack contains an
error 'wrong tag'.
The openssl x509 utility has no problems with this certificate, neither does
the i2d_X509().
Is there another possibility,