Oops! Wrong patch! Correct one attached. If you feel like testing the
wrong one, go ahead, but there are some later non-essential adjustments.
diff --git a/crypto/ec/ecp_nistz256.c b/crypto/ec/ecp_nistz256.c
index bf3fcc6..33b07ce 100644
--- a/crypto/ec/ecp_nistz256.c
+++
On 05/12/14 02:10, b_smith...@hotmail.com wrote:
I apologize if this is not the right place to post this question but it
seems like the best of the choices available to me. I am trying to
understand when TLS 1.2 Suite B ECDSA will be generally available. I
understand that this functionality
On Thu, 4 Dec 2014 10:57:11 +0100 Kurt Roeckx wrote:
It seems *TLS*_VERSION constants are meant to be used to set
minimum / maximum. A drawback of such approach is that
applications need to be recompiled and/or modified when OpenSSL is
updated with support for newer protocol version, if
On Fri, Dec 05, 2014 at 02:14:54PM +0100, Tomas Hoger wrote:
On Thu, 4 Dec 2014 10:57:11 +0100 Kurt Roeckx wrote:
It seems *TLS*_VERSION constants are meant to be used to set
minimum / maximum. A drawback of such approach is that
applications need to be recompiled and/or modified when
Enhancement request.
I suggest to enhance the trust chain discovery used by openssl, when
verifying a SSL/TLS server certificate, to make it work with a popular
server configuration.
Recently, Mozilla has started to cleanup the Mozilla CA trust list and
remove CA certificates that use a weaker
I started with an AES256 demo I found at https://github.com/saju/misc and
modified the initialisations to use AES128. The test strings that program uses
are quite short - less than 100 characters. If I add a significantly longer
string to those test values Valgrind reports a string of what I
Team,
Am using openssl for my monitoring tools and i have facing *faulting module
ssleay32.dll, version 0.0.0.0, fault address 0x00010c8b *in application
log and its all type of windows OS
May i know that it is known issue or new issue,if it is known issue please
provide issue id.
Kindly help
Oops! Wrong patch! Correct one attached. If you feel like testing the
wrong one, go ahead, but there are some later non-essential adjustments.
diff --git a/crypto/ec/ecp_nistz256.c b/crypto/ec/ecp_nistz256.c
index bf3fcc6..33b07ce 100644
--- a/crypto/ec/ecp_nistz256.c
+++
|What is the SECLEVEL you refer to? I had a quick look at SSL_CONF API
|pointed out by Stephen.[.]
|
I did too. Attached a doc patch (against 1.0.2) to match code
reality. Fixes linking for me.
--steffen
diff --git a/doc/ssl/SSL_CONF_cmd.pod b/doc/ssl/SSL_CONF_cmd.pod
index
I started with an AES256 demo I found at https://github.com/saju/misc and
modified the initialisations to use AES128. The test strings that program
uses are quite short - less than 100 characters. If I add a significantly
longer string to those test values Valgrind reports a string of what
Am using openssl for my monitoring tools and i have facing *faulting module
ssleay32.dll, version 0.0.0.0, fault address 0x00010c8b *in application
log and its all type of windows OS
May i know that it is known issue or new issue,if it is known issue please
provide issue id.
Kindly help
On Fri, Dec 05, 2014 at 05:07:04PM +0100, Kurt Roeckx wrote:
On Fri, Dec 05, 2014 at 10:40:07AM -0500, Daniel Kahn Gillmor wrote:
(of course it would probably end up modifying some public
interfaces, so it would need to take effect publicly during an API change).
Adding const to a
On Fri, Dec 05, 2014 at 05:15:24PM +, Viktor Dukhovni wrote:
On Fri, Dec 05, 2014 at 05:07:04PM +0100, Kurt Roeckx wrote:
On Fri, Dec 05, 2014 at 10:40:07AM -0500, Daniel Kahn Gillmor wrote:
(of course it would probably end up modifying some public
interfaces, so it would need to
Gee, BOGUS_CONST is a little harsh. MAYBE_CONST or SHOULDBE_CONST would have
been nicer.
___
openssl-dev mailing list
openssl-dev@openssl.org
https://mta.opensslfoundation.net/mailman/listinfo/openssl-dev
On Fri, Dec 05, 2014 at 12:28:29PM -0500, Salz, Rich wrote:
Gee, BOGUS_CONST is a little harsh. MAYBE_CONST or SHOULDBE_CONST would have
been nicer.
Wietse does not mince words, and sarcasm is often lost in translation.
--
Viktor.
___
Hi,
Do you plan to integrate this one somewhere soon?
https://github.com/openssl/openssl/pull/113
I can help with merge if needed.
Kris
___
openssl-dev mailing list
openssl-dev@openssl.org
OpenSSL is currently not supported under Cygwin64.
Support for Cygwin64 will appear in 1.0.2, so that I'd like to hear a
little bit more about what kind of problem does it cause. The Cygwin64
support was submitted by Cygwin maintainer, and no additional issues
were reported.
.. credits should really go (if) to V. Smotlacha in the first place
(and I wonder, why the original Cc header was not preserved)
MB
___
openssl-dev mailing list
openssl-dev@openssl.org
https://mta.opensslfoundation.net/mailman/listinfo/openssl-dev
18 matches
Mail list logo
