You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Esteban Chacon Martin edited this page Aug 20, 2022
·
1 revision
The server has the fallowing internal information structure.
/* Protocol version length */#definePROTOLEN 32
/* Hash application identity lentgth. */#defineHASHLEN 256
structtfproto {
/* Protocol version */charproto[PROTOLEN];
/* Hash identity */charhash[HASHLEN];
/* Directory for the database. */chardbdir[PATH_MAX];
/* Number of port for comm. */charport[PORTLEN];
}
The proto member holds the protocol version. The hash member
holds a message digest that identifies the client in order to allow the
use of the protocol. The dbdir member holds the directory for the
data that clients require to store. The port member indicates the
number of ports in which the server will listen for connections. As
stated before the hash has to be less than 256 bytes long; and the
proto less than 32 bytes long.
In order to match this structure when a client starts a connection,
there are some steps that must be follow.