pushtls, tlsClient, tlsServer, initThumbprints, freeThumbprints,
okThumbprint, okCertificate, readcert, readcertchain – attach TLS1
or SSL3 encryption to a communication channel|
int pushtls(int fd, char *hashalg, char *encalg,
int tlsClient(int fd, TLSconn *conn)
int tlsServer(int fd, TLSconn *conn)
uchar *readcert(char *filename, int *pcertlen)
PEMchain *readcertchain(char *filename)
Thumbprint *initThumbprints(char *ok, char *crl, char *tag)
void freeThumbprints(Thumbprint *table)
int okThumbprint(uchar *hash, int len, Thumbprint *table)
int okCertificate(uchar *cert, int len, Thumbprint *table)
Transport Layer Security (TLS) comprises a record layer protocol,
doing message digesting and encrypting in the kernel, and a handshake
protocol, doing initial authentication and secret creation at
user level and then starting a data channel in the record protocol.
TLS is nearly the same as SSL 3.0, and the software
should interoperate with implementations of either standard.
To use just the record layer, as described in tls(3), call pushtls to open the record layer device, connect to the communications channel fd, and start up encryption and message authentication as specified in hashalg, encalg, and secret. These parameters must have been arranged at the two ends of the conversation by other means. For example, hashalg could be sha1, encalg could be rc4_128, and secret could be the base–64 encoding of two (client–to–server and server–to–client) 20–byte digest keys and two corresponding 16–byte encryption keys. Pushtls returns a file descriptor for the TLS data channel. Anything written to this descriptor will get encrypted and authenticated and then written to the file descriptor, fd. Pushtls , tlsClient and tlsServer close the original file descriptor on success. If dir is non–zero, the path name of the connection directory is copied into dir. This path name is guaranteed to be less than 40 bytes long.
TlsClient will optionally compute a session key for use by higher–level protocols. To compute a session key, the caller must set sessionType to a known session type; sessionKeylen to the desired key length; sessionKey to a buffer of length sessionKeylen; and sessionConst to the desired salting constant. The only supported session type is ttls, as used by 802.1x.
TlsServer executes the server side of the handshake. The caller must initialize conn–>cert, usually by calling readcert to read and decode the PEM–encoded certificate from filename, return a pointer to malloced storage containing the certificate, and store its length through pcertlen. The private key corresponding to cert.pem should have been previously loaded into factotum. (See rsa(8) for more about key generation.)
Readcertchain will read a PEM–encoded chain of certificates from
filename and return a pointer to a linked list of malloced PEMChain
structures, defined in libsec.h:
Conn is not required for the ongoing conversation and may be freed
by the application whenever convenient.
Start the client half of TLS and check the remote certificate:|
/sys/lib/tls thumbprints of trusted services|
/sys/lib/ssl PEM certificate files
dial(2), tls(3), factotum(4), thumbprint(6)|
Return –1 on failure.|
Client certificates and client sessionIDs are not yet implemented.
Note that pushtls, tlsClient and tlsServer do not close the original file descriptor on failure, only on success.
The sessionID and cert pointers in the TLSconn structure have to be freed by the caller.
Note that in the TLS protocol sessionID itself is public; it is
used as a pointer to secrets stored in factotum.