See PR:
https://github.com/openssl/openssl/pull/362
I'm really not sure if this is the best fix or not (or even if it is
reliable on older platforms) - but it cleared the error on my Mac OS X
system, and didn't appear to cause any issues on an Ubuntu or FreeBSD
distribution I tested on and I
Hello,
see GitHub pull request at
https://github.com/openssl/openssl/pull/354
which fixes memory leaks on error conditions in X509_add1_reject_object()
and PKCS7_verify().
Cheers
___
openssl-bugs-mod mailing list
openssl-bugs-...@openssl.org
Hello,
see GitHub pull request at
https://github.com/openssl/openssl/pull/355
which implements the HMAC-based Extract-and-Expand Key Derivation Function
(HKDF) as defined in RFC 5869, and used by QUIC and TLS 1.3.
It comes with tests as defined in the Appendix A of the same RFC.
Cheers
Hi,
I’ve been using openssl 1.0.1j on android 5.1.
On test, I’ve been getting the following crash messages because of
accessing unaccessable address (invalid pointer) on ASN1_primitive_free.
Fault address is changed every time.
Please provide your help.
Case 1.
08-05 13:05:28.238 I 505
On Wed Aug 05 01:06:40 2015, m...@bogosian.net wrote:
Hi Steve,
I've attached three certificate collections: two that fail (where
subject == issuer) and one that works around the problem (where
subject != issuer).
OK thanks for the examples. The bug is that OpenSSL 1.0.2 is less strict about
On Wed, Aug 05, 2015 at 11:01:13am +, Alessandro Ghedini via RT wrote:
Hello,
see GitHub pull request at
https://github.com/openssl/openssl/pull/354
which fixes memory leaks on error conditions in X509_add1_reject_object()
and PKCS7_verify().
I also added a couple more patches fixing
On 04/08/15 22:03, Ian McFadries (imcfadri) wrote:
Sorry for the delayed response, I was away for a week and was able to test
the fix today.
The fix did resolve the session ticket issue that I was encountering.
However, now I get an error when I am not using the session tickets under
Hi,
In ./Configure, there is this comment:
# big-endian platform. This is because ARMv7 processor always
# picks instructions in little-endian order. Another similar
# limitation is that -mthumb can't cross -march=armv6t2
# boundary, because that's where it became
Yesterday, I was alerted by a member of the list that my emails to
openssl-dev are ending up in their SPAM folder. After examining my emails
as sent out by OpenSSL's mailman, I saw that it is mucking with the
headers, causing DKIM failures. This could be because of one of two
reasons:
a)
I was *distinctly* upset, some years ago, to find that OpenSSL couldn't
do this for me and I had to do it myself. Now I see it can, and I can
fix my own code to use that facility thus:
http://git.infradead.org/users/dwmw2/openconnect.git/commitdiff/674881cbb
It looks like I can use it from 1.0.2
On Wed, Aug 05, 2015 at 06:54:33AM -0700, Quanah Gibson-Mount wrote:
Yesterday, I was alerted by a member of the list that my emails to
openssl-dev are ending up in their SPAM folder. After examining my emails
as sent out by OpenSSL's mailman, I saw that it is mucking with the headers,
On Wed, Aug 05, 2015 at 04:54:25PM +0200, Kurt Roeckx wrote:
On Wed, Aug 05, 2015 at 06:54:33AM -0700, Quanah Gibson-Mount wrote:
Yesterday, I was alerted by a member of the list that my emails to
openssl-dev are ending up in their SPAM folder. After examining my
emails as sent out by
OS - ChromeOs
Version affected - 1.0.2d
Hi, clang fails to build this version. 'ldrplb' and 'ldrneb' are pre-UAL
format, could I suggest to replaced those with UAL-format 'ldrbpl' and
'ldrbne' respectively? (GCC recognizes both)
A patch attached.
Thanks,
Han
diff -U5 -r
On Wed, Aug 05, 2015 at 04:54:57PM +, mancha wrote:
I interpret the comment to mean that, because OpenSSL lists modify
messages (see below), they should strip DKIM headers (see above) before
distribution to prevent false negatives in recipient implementations.
Won't that always give DKIM
On Wed, Aug 05, 2015 at 09:33:02PM +0200, Kurt Roeckx wrote:
On Wed, Aug 05, 2015 at 04:54:57PM +, mancha wrote:
I interpret the comment to mean that, because OpenSSL lists modify
messages (see below), they should strip DKIM headers (see above)
before distribution to prevent false
On 05/08/15 23:00, mancha wrote:
OpenSSL is certainly not alone in its practice of mangling headers
and adding body footers so I'd be curious to hear how other lists
handle domains such as yahoo.com.
We warn people that DKIM-using domains may experience bounces, and
that they should subscribe
On Wed 2015-08-05 17:04:30 -0400, Jonas Maebe wrote:
On 05/08/15 23:00, mancha wrote:
OpenSSL is certainly not alone in its practice of mangling headers
and adding body footers so I'd be curious to hear how other lists
handle domains such as yahoo.com.
We warn people that DKIM-using domains
Hi,
I'm seeing a build issue on PowerPC:
ppccap.c:10:20: fatal error: crypto.h: No such file or directory
#include crypto.h
A pull request to fix this is at:
https://github.com/openssl/openssl/pull/363
Regards,
Anton
___
openssl-bugs-mod mailing
fixed in master and 1.0.2, thanks!
--
Rich Salz, OpenSSL dev team; rs...@openssl.org
___
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
On 04/08/15 15:54, Blumenthal, Uri - 0553 - MITLL wrote:
On 04/08/15 00:37, Quanah Gibson-Mount wrote:
I also don't get why a CLA is required, overall.
It's not something I'm thrilled about either. However we have been
receiving legal advice. That advice tells us that we should be putting
20 matches
Mail list logo
