On 12/10/18 00:06, Arne Schwabe wrote:
> The last version of the patch used the TLS1.2 version
> tls_ctx_restrict_ciphers to set the restrictions for both
> TLS 1.3 and TLS1.2 instead of using tls_ctx_restrict_ciphers_tls13
> for TLS1.3.
>
> Also fix minor style problem while I am touching the fun
Am 12.10.18 um 12:38 schrieb David Sommerseth:
> On 12/10/18 00:06, Arne Schwabe wrote:
>> The last version of the patch used the TLS1.2 version
>> tls_ctx_restrict_ciphers to set the restrictions for both
>> TLS 1.3 and TLS1.2 instead of using tls_ctx_restrict_ciphers_tls13
>> for TLS1.3.
>>
>> Al
On 22/08/18 00:08, Steffan Karger wrote:
> Simplifies the build scripts, and fixes my CI, where paths on the test
> slave can be different from paths on the build slave.
>
> Signed-off-by: Steffan Karger
> ---
> configure.ac | 11 ++-
> vendor/Makefile.am | 15 +++
> 2
Acked-by: Gert Doering
It now displays the expected result set (and the code change makes sense):
$ src/openvpn/openvpn --verb 4 --tls-ciphersuites TLS_AES_256_GCM_SHA384
--show-tls --tls-cipher TLS-DHE-RSA-WITH-AES-256-CBC-SHA256
Available TLS Ciphers, listed in order of preference:
Hi,
My testing shows that OpenSSL 1.1.1 likes to use PSS even for TLS 1.2, so,
even in the short-term, this can't be worked around by just disabling TLS
1.3.
Now, for cryptoapicert, it would have been easy to support PSS using
Windows CNG API provided OpenSSL passes the hash and ask to sign with
