Fixed now, thanks for the report.
Steve.
--
Dr Stephen N. Henson. OpenSSL project core developer.
Commercial tech support now available see: http://www.openssl.org
--
Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4504
Please log in as guest with password guest if prompted
--
Hello,
in the Configure file only support for Android arm-v7 are found.
But general arm-v8/arm64/aarch64 are included for the Linux target.
--
Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4536
Please log in as guest with password guest if prompted
--
openssl-dev mailing list
To
On Tue Apr 12 13:41:51 2016, nbh...@gmail.com wrote:
> On my test server running OpenSSL 1.0.2e on Windows Server 2012. The
> "newest" cacert.pem fails with an error "SSL certificate problem: unable to
> get local issuer certificate", however, the one from 2014 works. I am
> attaching both.
>
Can
On Mon Mar 21 13:02:56 2016, ramunas.jurgi...@gmail.com wrote:
> I did write function which changes PKCS12 passphrase. I noticed that
> PKCS12_newpass function leaks memory. Memory leak disappears when
> commenting out line where is PKCS12_newpass func.
>
> Below I posted this code which I am
1.0.1 is at end-of life and is only getting security fixes for the rest of the
year.
1.0.2 is LTS and maybe this needs to be ported there (and master) as well?
--
Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4522
Please log in as guest with password guest if prompted
--
Fixed in commit acde647fb0347f64af8
Thanks for the report.
Steve.
--
Dr Stephen N. Henson. OpenSSL project core developer.
Commercial tech support now available see: http://www.openssl.org
--
Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4493
Please log in as guest with password
On Thu May 05 12:54:11 2016, howard.m.kash@mail.mil wrote:
>
> OpenSSL 1.0.2h fails to process large CRLs (anything over 1MB) with the
> error "X509_NAME_EX_D2I:too long:x_name.c:203" due to X509_NAME_MAX being
> set to 1024*1024. The CRLs I'm examining with "openssl crl -in
> -nextupdate
OpenSSL 1.0.2h fails to process large CRLs (anything over 1MB) with the
error "X509_NAME_EX_D2I:too long:x_name.c:203" due to X509_NAME_MAX being
set to 1024*1024. The CRLs I'm examining with "openssl crl -in
-nextupdate -noout" are up to 37MB (and growing). I have set X509_NAME_MAX
to
Hi,
I think there should be a test in order to avoid the same regression in future.
For example, run `test/tcrl` against a large crl list, which would have been
failed before of the fix for ticket RT#4531:
cd test
sh tcrl large_crl.pem
Theo.
--
openssl-dev mailing list
To
Closing this ticket at request of submitter. Erroneous duplicate of #4533
Matt
--
Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4534
Please log in as guest with password guest if prompted
--
openssl-dev mailing list
To unsubscribe:
> If you configure for mingw, you need to do so from inside a MSYS/MingW
> shell. If you want to build inside a cmd shell, you have to configure
> natively,
In addition a "matching perl" is likely to be required. I mean one can
start MSYS shell and have ActiveState Perl first on the $PATH and
If you configure for mingw, you need to do so from inside a MSYS/MingW
shell. If you want to build inside a cmd shell, you have to configure
natively, i.e. for one of the VC-* configuration targets.
Cheers,
Richard
In message <37d47403029a56ad3095af56b7323...@qualitesys.com> on Wed, 04 May
12 matches
Mail list logo