On Wed, Oct 25, 2017 at 05:19:23PM +0200, Tomas Mraz wrote:
>
> The problem is that by default the applications do not read the file and
> do not apply the defaults. Even the openssl s_client/s_server does not
> seem to work, but I might be doing something wrong.
>
> What I would like to see is a
On 25/10/17 16:19, Tomas Mraz wrote:
>> |However libssl currently does not have a way to apply some policy such
>> |as using just protocol TLS1.2 or better system-wide with a possibility
>> |for sysadmin to configure this via some configuration file. Of course
>> |it would still be up to indi
On 09/28/2017 12:21 AM, Steffen Nurpmeso wrote:
> Hello.
>
> Tomas Mraz wrote:
> |I would like to restart the discussion about possibilities of system-
> |wide configurability of OpenSSL and particularly libssl.
> |
> |Historically OpenSSL allowed only for configuration of the enabled
> |cip
Hello.
Tomas Mraz wrote:
|I would like to restart the discussion about possibilities of system-
|wide configurability of OpenSSL and particularly libssl.
|
|Historically OpenSSL allowed only for configuration of the enabled
|ciphersuites list if application called appropriate API call. This
I would like to restart the discussion about possibilities of system-
wide configurability of OpenSSL and particularly libssl.
Historically OpenSSL allowed only for configuration of the enabled
ciphersuites list if application called appropriate API call. This is
now enhanced with the SSL_CONF API
