Re: Outbound FTP java errors

I think it has nothing to do with OpenSSL. On Fri, Nov 15, 2019 at 3:00 AM Krista Brackin via openssl-users < openssl-users@openssl.org> wrote: > I am a novice...so any help please > > Below is the stack trace on the outbound file but I cannot make any > setting change workthoughts on

Outbound FTP java errors

I am a novice...so any help please Below is the stack trace on the outbound file but I cannot make any setting change workthoughts on what could be blocked me from transferring the file? log attached.  thank you!Krista FTP was not successful com.tms.common.lib.FTPClient.FTPException:

Re: Why can't I force a specific cipher with the openssl app with TLS 1.3?

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

Re: Why can't I force a specific cipher with the openssl app with TLS 1.3?

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

Why can't I force a specific cipher with the openssl app with TLS 1.3?

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

Re: sk_X509_OBJECT_num()

That makes sense. Thanks to everyone for the responses. Jason From: Dave Coombs Sent: Wednesday, November 13, 2019 5:30 PM To: Jason Schultz Cc: openssl-users@openssl.org Subject: Re: sk_X509_OBJECT_num() Hi, They're macros, defined in SKM_DEFINE_STACK_OF()