> On May 25, 2017, at 10:28 AM, Salz, Rich via openssl-users
> wrote:
>
>> It uses SSL_CTX_use_certificate_chain_file in some places and in other places
>> it uses PEM_read_bio_X509
>>
>> When these APIs are used, can the OpenSSL stack detect updated files on
>> disk and reload them without an
So this is exclusively a change to support mingw64 ?
That seems to be all that is said here :
https://www.openssl.org/news/cl102.txt
OpenSSL CHANGES
___
Changes between 1.0.2l and 1.0.2m [xx XXX ]
*)
Changes between 1.0.2k and 1.0.2l [25 May 2017]
*) Have 'con
> It uses SSL_CTX_use_certificate_chain_file in some places and in other places
> it uses PEM_read_bio_X509
>
> When these APIs are used, can the OpenSSL stack detect updated files on
> disk and reload them without any intervention from the application?
No, it's a load and use the current content
Hi,
The reSIProcate project is using OpenSSL to load[1] certificates and
private keys.
It uses SSL_CTX_use_certificate_chain_file in some places and in other
places it uses PEM_read_bio_X509
When these APIs are used, can the OpenSSL stack detect updated files on
disk and reload them without any
Qint Software GmbH
Marlene-Dietrich-Str.59
80636 München
+49 172 8910563
Sitz: München HRB 117326
Geschäftsführer: Patrick Mayweg.
> On 25.05.2017, at 15:57, OpenSSL wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
>
> OpenSSL version 1.0.2l released
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
OpenSSL version 1.1.0f released
===
OpenSSL - The Open Source toolkit for SSL/TLS
https://www.openssl.org/
The OpenSSL project team is pleased to announce the release of
version 1.1.0f of our open sour
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
OpenSSL version 1.0.2l released
===
OpenSSL - The Open Source toolkit for SSL/TLS
https://www.openssl.org/
The OpenSSL project team is pleased to announce the release of
version 1.0.2l of our open sour
