> From: openssl-users [mailto:openssl-users-boun...@openssl.org] On Behalf Of
> Viktor Dukhovni
> Sent: Saturday, July 20, 2019 09:18
>
> > Atm, it's inclear why it's working for Michael Wojcik ... different
> version?
> > something's changed?
>
> I am discounting his report of success. The full
On 7/20/19 8:17 AM, Viktor Dukhovni wrote:
On Sat, Jul 20, 2019 at 07:35:49AM -0700, PGNet Dev wrote:
Checking cipherlist for just TLSv1.3 ciphers FAILs here,
openssl ciphers -stdname -s -V
'TTLS13-CHACHA20-POLY1305-SHA256:TLS13-AES-128-GCM-SHA256:TLS13-AES-256-GCM-SHA384'
On Sat, Jul 20, 2019 at 07:35:49AM -0700, PGNet Dev wrote:
> >> Checking cipherlist for just TLSv1.3 ciphers FAILs here,
> >>
> >>openssl ciphers -stdname -s -V
> >> 'TTLS13-CHACHA20-POLY1305-SHA256:TLS13-AES-128-GCM-SHA256:TLS13-AES-256-GCM-SHA384'
> >>Error in cipher list
> >
Hi,
On 7/20/19 7:28 AM, Viktor Dukhovni wrote:
> On Fri, Jul 19, 2019 at 10:38:19AM -0700, PGNet Dev wrote:
>
>> I suspect I've misunderstood usage of TLSv1.3 @
>>
>> https://www.openssl.org/blog/blog/2018/02/08/tlsv1.3/
>>
>> Checking cipherlist for just TLSv1.3 ciphers FAILs here,
>>
>>
On Fri, Jul 19, 2019 at 10:38:19AM -0700, PGNet Dev wrote:
> I suspect I've misunderstood usage of TLSv1.3 @
>
> https://www.openssl.org/blog/blog/2018/02/08/tlsv1.3/
>
> Checking cipherlist for just TLSv1.3 ciphers FAILs here,
>
> openssl ciphers -stdname -s -V
>
>>> Configuration file difference?
>
>> which config file are you referring to?
>
> The default OpenSSL configuration file. openssl.cnf, in the directory
> displayed by "openssl version -d". But I can't think offhand of anything in
> the configuration file that I'd expect to have this sort
> Works for me:
> $ openssl ciphers -stdname -s -V
> 'TTLS13-CHACHA20-POLY1305-SHA256:TLS13-AES-128-GCM-SHA256:TLS13-AES-256-GCM-SHA384'
simplifying to build defaults
./config -v \
--prefix=/usr/local/ssl-test \
--openssldir=/usr/local/ssl-test \
[Apologies if the formatting here is a little screwy. For the moment I have to
use Outlook Web Interface, which is even more problematic than the standalone
Outlook client.]
> > Different OpenSSL release?
> yes
> openssl version
> OpenSSL 1.1.1c 28 May 2019
Eh, that's probably
> Works for me:
heh. of COURSE it does!
sanity check here,
openssl ciphers -stdname -s -V
'TTLS13-CHACHA20-POLY1305-SHA256:TLS13-AES-128-GCM-SHA256:TLS13-AES-256-GCM-SHA384'
Error in cipher list
140042399306176:error:1410D0B9:SSL routines:SSL_CTX_set_cipher_list:no
cipher
> From: openssl-users [mailto:openssl-users-boun...@openssl.org] On Behalf Of
> PGNet Dev
> Sent: Friday, July 19, 2019 11:38
>
> Checking cipherlist for just TLSv1.3 ciphers FAILs here,
>
> openssl ciphers -stdname -s -V 'TTLS13-CHACHA20-POLY1305-
>
I suspect I've misunderstood usage of TLSv1.3 @
https://www.openssl.org/blog/blog/2018/02/08/tlsv1.3/
Checking cipherlist for just TLSv1.3 ciphers FAILs here,
openssl ciphers -stdname -s -V
'TTLS13-CHACHA20-POLY1305-SHA256:TLS13-AES-128-GCM-SHA256:TLS13-AES-256-GCM-SHA384'
11 matches
Mail list logo