hi!
i would like to report some bugs in ssleay. unfortunately i don't have
diffs against latest openssl source, but the fixes are really small, so i
hope it's not too much trouble to incorporate them.
1) crypto/bio/b_printf.c uses static buffer for vsprintf which might
overflow. we should use
Currently V3 extension support is almost absent.
We've done almost all of what you're suggesting:
typedef struct x509_extension_method_st
{
int nid;
void (*clear)();
int (*get_bool)(); // used if extn is ASN1_BIT_STRING
int (*set_bool)();
int (*get_str)();
[EMAIL PROTECTED] wrote:
Currently V3 extension support is almost absent.
We've done almost all of what you're suggesting:
typedef struct x509_extension_method_st
{
int nid;
void (*clear)();
int (*get_bool)(); // used if extn is ASN1_BIT_STRING
int
Arne Ansper wrote:
hi!
i would like to report some bugs in ssleay. unfortunately i don't have
diffs against latest openssl source, but the fixes are really small, so i
hope it's not too much trouble to incorporate them.
1) crypto/bio/b_printf.c uses static buffer for vsprintf which
Hi,
I suggest we dump the whole logic and instead use
PEM_X509_INFO_read_bio() to read in the whole lot. This is designed to
Hadn't even noticed this function - looks a lot simpler. I'll try it out
and probably move to that for now. Unless someone feels strongly one way
or another about the
-BEGIN PGP SIGNED MESSAGE-
I have a few problems to report with openssl 0.9.4. Please note that
I'm not reporting in order to criticize your work, which I consider
wonderful and extremely useful, or to attempt to get free support,
but only because the docs asks me to do so.
config
Country Name (2 letter code) [AU]:AU
Organization Name (eg, company) []:Dodgy Brothers
Common Name (eg, YOUR name) []:Brother 1
Common Name (eg, YOUR name) []:Brother 2
Request (and private key) is in newreq.pem
Using configuration from ../apps/openssl.cnf
error on line 6 of config file
Hi,
after first establishing a session, the verify_result can be obtained
via SSL_get_verify_result(SSL *con), it may yield X509_V_OK or not!
When reloading an old session, the certificate is not checked again;
as verify_result is not stored in SSL_SESSION (at least I didn´t find it)
and the
