OCB support has been merged in. Closing my own ticket.
Matt
___
openssl-dev mailing list
openssl-dev@openssl.org
https://mta.opensslfoundation.net/mailman/listinfo/openssl-dev
Hi,
The exact error which i faced in Event log are given below.
Faulting application name: aeagent.exe, version:0.0.0.0, time
stamp:0x53e1f20f
Faulting module name: SSLEAY32.dll, version:0.0.0.0, time stamp: 0x405a2628
Exception code: 0xc005
Fault offset: 0x00010c8b
Faulting process id :
Does:
- Fixes a typo in s_client.pod (2x in the).
- Changes .pod to reflect reality: it is SSL_CONF_CTX_finish(),
not SSL_CONF_finish().
- While here it seems best to change the remaining SSL_CONF_cmd(),
SSL_CONF_cmd_argv() and SSL_CONF_cmd_value_type() to have
a SSL_CONF_CTX_ prefix,
Oh yes: and on top of that former patch there really where also
dangling SSL_CTX_cmd() use cases in .pod files, which are thus and
finally changed to SSL_CONF_CTX_cmd via the attached patch, too.
Thank you.
--steffen
diff --git a/doc/ssl/SSL_CONF_CTX_cmd.pod b/doc/ssl/SSL_CONF_CTX_cmd.pod
index
rand_win.c(361) RAND_add(buf, sizeof(buf), 0);This is inconsistent with line
375 which passes sizeof(buf) for the bytes of entropy.
This means that the entropy from the OS pool is discounted; in normal
circumstances this is insignificant because the rest of this function collects
plenty of
Hello,
and finally i propose three new values for the Protocol slot of
SSL_CONF_CTX_cmd(): OLDEST, NEWEST and VULNERABLE.
I included OLDEST for completeness sake, NEWEST is in effect what
i've always forced for my thing whenever possible, and encouraged
users to use themselve, but of course it
I think magic names -- shorthands -- are a very bad idea. They are
point-in-time statements whose meaning evolves, if not erodes, over time.
___
openssl-dev mailing list
openssl-dev@openssl.org
I think magic names -- shorthands -- are a very bad idea. They are
point-in-time statements whose meaning evolves, if not erodes, over time.
___
openssl-dev mailing list
openssl-dev@openssl.org
On Mon, Dec 08, 2014 at 07:58:31PM +0100, Steffen Nurpmeso via RT wrote:
set ssl-protocol=ALL,-SSLv2
This results in the obvious problem that when they (get)
upgrade(d) their OpenSSL library they will see a completely
intransparent error message that no normal user will understand:
It was
On Mon, Dec 08, 2014 at 08:20:44PM +0100, Steffen Nurpmeso via RT wrote:
Hello,
and finally i propose three new values for the Protocol slot of
SSL_CONF_CTX_cmd(): OLDEST, NEWEST and VULNERABLE.
I actually find the option unfortunate and I think it should have
been one that sets the minimum
OCB support has been merged in. Closing my own ticket.
Following is not directly related to the case per se [which is why rt
doesn't get this message]. It's just that it makes nice example on why
one sometimes wants to implement encryption mode in assembly. If you
compare performance on
On 8 December 2014 at 19:20, Steffen Nurpmeso via RT r...@openssl.org wrote:
and finally i propose three new values for the Protocol slot of
SSL_CONF_CTX_cmd(): OLDEST, NEWEST and VULNERABLE.
In Qt we've added an enum value for TLS versions that is SecureProtocols so
that we could remove
Thanks for the response, Andy, it's good to know that the demo program does
actually work for someone. Sorry for the delay, I'm kinda busy with other
things right now. Also, I realised the link was truncated, but it looks as
though you found the demo anyway.
13 matches
Mail list logo
