Sponsored Content
Full Discussion: Three way handshake
Top Forums Programming Three way handshake Post 70528 by Perderabo on Saturday 30th of April 2005 10:55:57 AM
Old 04-30-2005
This is a TCP concept. TCP guarantees reliable dilevery of data. It does this by using sequence numbers. Each byte of data gets a sequence number. Both sides of the connection keep the other side informed of the sequence number of the next byte of data it needs to recieve. The sequence numbers do not start at 0 or 1. The initial sequence number is random. So both sides need to syncronize ISN's. This establishes a TCP connection.

1. The client sends a packet with it's ISN. This packet has a SYN flag. This packet is addressed to some well-known port on the server. And it has the local port number the client has picked for itself.

2. The server send a packet back to client. This packet does two things. First it sets the ACK flag and and sets the ack number to the client's ISN+1. And it sets the SYN flag and sends it's own ISN.

3. The client sends a packet to ACK the server's ISN+1.

At this point both client and server know each other's sequence numbers.
 

4 More Discussions You Might Find Interesting

1. IP Networking

Incomplete three way handshake

I've got a strange problem with a single mail sender (it is one of those large free mail providers). My mail server works well with thousands of senders but not this one, so we have made a connection dump and it seems that the three way handshake is not completed 15:55:59.177431 IP... (0 Replies)
Discussion started by: 3wayTrouble
0 Replies

2. UNIX for Dummies Questions & Answers

windows linux handshake !!

hi i wanted to know how to read the status of RTS/CTS line using ioctl calls....i am programming using c/c++ and linux if someone can post a code snippet or suggest a book for the same...it will be very helpful.... 2. also i will like to know can a windows application and a rtos application... (1 Reply)
Discussion started by: nivea_jmd
1 Replies

3. Solaris

handshake/connection errors

I'm running solaris openssl 097l and I upgraded to 098h. I see errors in the logs that seem like debugging errors that showed up, but seemed to happen in both versions I believe. I am using a certificate from another machine to test for this server. I believe the error messages generate when I... (4 Replies)
Discussion started by: csross
4 Replies

4. UNIX for Dummies Questions & Answers

No mail sending - Deferred: 403 4.7.0 TLS handshake failed

Please help! I am in urgent need of assistance. What started out as a small problem with IMAP folders not working seems to have spread. Our mail server, Scalix running on CentOS 5.5 isn't sending out any mail. There are now over 400 emails queued waiting to go out, all of which give the... (0 Replies)
Discussion started by: beckyboo
0 Replies
SSL_do_handshake(3SSL)						      OpenSSL						    SSL_do_handshake(3SSL)

NAME
SSL_do_handshake - perform a TLS/SSL handshake SYNOPSIS
#include <openssl/ssl.h> int SSL_do_handshake(SSL *ssl); DESCRIPTION
SSL_do_handshake() will wait for a SSL/TLS handshake to take place. If the connection is in client mode, the handshake will be started. The handshake routines may have to be explicitly set in advance using either SSL_set_connect_state(3) or SSL_set_accept_state(3). NOTES
The behaviour of SSL_do_handshake() depends on the underlying BIO. If the underlying BIO is blocking, SSL_do_handshake() will only return once the handshake has been finished or an error occurred, except for SGC (Server Gated Cryptography). For SGC, SSL_do_handshake() may return with -1, but SSL_get_error() will yield SSL_ERROR_WANT_READ/WRITE and SSL_do_handshake() should be called again. If the underlying BIO is non-blocking, SSL_do_handshake() will also return when the underlying BIO could not satisfy the needs of SSL_do_handshake() to continue the handshake. In this case a call to SSL_get_error() with the return value of SSL_do_handshake() will yield SSL_ERROR_WANT_READ or SSL_ERROR_WANT_WRITE. The calling process then must repeat the call after taking appropriate action to satisfy the needs of SSL_do_handshake(). The action depends on the underlying BIO. When using a non-blocking socket, nothing is to be done, but select() can be used to check for the required condition. When using a buffering BIO, like a BIO pair, data must be written into or retrieved out of the BIO before being able to continue. RETURN VALUES
The following return values can occur: 1. The TLS/SSL handshake was successfully completed, a TLS/SSL connection has been established. 0 The TLS/SSL handshake was not successful but was shut down controlled and by the specifications of the TLS/SSL protocol. Call SSL_get_error() with the return value ret to find out the reason. <0 The TLS/SSL handshake was not successful because a fatal error occurred either at the protocol level or a connection failure occurred. The shutdown was not clean. It can also occur of action is need to continue the operation for non-blocking BIOs. Call SSL_get_error() with the return value ret to find out the reason. SEE ALSO
SSL_get_error(3), SSL_connect(3), SSL_accept(3), ssl(3), bio(3), SSL_set_connect_state(3) 1.0.1e 2014-08-06 SSL_do_handshake(3SSL)
All times are GMT -4. The time now is 08:24 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy