You are not logged in. Please login or register.
Please post questions or comments you have about wolfSSL products here. It is helpful to be as descriptive as possible when asking your questions.
ReferenceswolfSSL - Embedded SSL Library → wolfSSL → wolfSSL_connect Fail
FTP SSL downloads files from the Internet. The first time you control the connection, you can log in to the server, enter pasV mode, and resolve the IP address and port number. The second time you connect to the server, wolfSSL fails to connect, and the Client sends Client Hello and sends an Alert. Connect state: CLIENT_HELLO_SENT, and then shutdown is called for two-way shutdown. Attempts to re-read server information fail. The client never connected to the server.
Hello zyhaha,
Thanks for joining the wolfSSL Forums. It sounds like the server is expecting the client to use a session ticket to renegotiate the connection. Could you please share a pcap of the first and second connections?
Kind regards,
Eric @ wolfSSL Support
Probably not, because the server does not send the ticket to the client. During the second handshake, the Client sends the following Hello packets :Session ID Length: 0; Then the client sends Alert (Level: Warning, Description: Close Notify) and [FIN,ACK]
Hello Eric,
Thank you for your reply and help. The following is the PCAP file I provided.
Best wishes
The server is expecting the data channel to resume the session. You'll need to save the session from the first connection, and then set the session before doing the second connection.
Here is an example:
https://github.com/wolfSSL/wolfssl-exam … s-resume.c
wolfSSL - Embedded SSL Library → wolfSSL → wolfSSL_connect Fail
Powered by PunBB, supported by Informer Technologies, Inc.
Generated in 0.020 seconds (92% PHP - 8% DB) with 11 queries