> On Nov 15, 2019, at 4:25 AM, Matt Caswell wrote:
>
> It might be nice if we added a new option "-pskmd" or similar which
> enabled you to specify the md from the command line without having to
> have a session file first. However that isn't currently possible.
With a saved session there may
On 14/11/2019 22:30, Phil Neumiller wrote:
> Hi Matt,
>
> That works fine for 256 as you mentioned. I trying to speak to a piece of
> hardware that has one supported cipher, i.e. TLS_AES_256_GCM_SHA384. I
> tried the naive approach of
>
> PSK=63ef2024b1
> openssl s_server -accept 4433
Hi Matt,
That works fine for 256 as you mentioned. I trying to speak to a piece of
hardware that has one supported cipher, i.e. TLS_AES_256_GCM_SHA384. I
tried the naive approach of
PSK=63ef2024b1
openssl s_server -accept 4433 -tls1_3 -nocert -psk $PSK -sigalgs RSA+SHA384
-ciphersuites
On 14/11/2019 17:46, Phil Neumiller wrote:
> Here is my server script is:
>
> PSK=63ef2024b1
> openssl s_server -accept 4433 -tls1_3 -nocert -psk $PSK -ciphersuites
> TLS_AES_256_GCM_SHA384
>
> Here is the client:
>
> PSK=63ef2024b1
> openssl s_client -tls1_3 -psk $PSK -connect :4433
Here is my server script is:
PSK=63ef2024b1
openssl s_server -accept 4433 -tls1_3 -nocert -psk $PSK -ciphersuites
TLS_AES_256_GCM_SHA384
Here is the client:
PSK=63ef2024b1
openssl s_client -tls1_3 -psk $PSK -connect :4433 -ciphersuites
TLS_AES_256_GCM_SHA384
And here is the error:
Using
