tlssrv man page on Plan9

Man page or keyword search:  
man Server   549 pages
apropos Keyword Search (all sections)
Output format
Plan9 logo
[printable version]

TLSSRV(8)							     TLSSRV(8)

       tlssrv,	tlsclient,  tlssrvtunnel,  tlsclienttunnel  -  TLS  server and

       tlssrv [ -c cert.pem ] [ -l logfile ] [ -r remotesys ] cmd [  args  ...

       tlsclient [ -t trustedkeys ] [ -x excludedkeys ] address

       tlssrvtunnel plain-addr crypt-addr cert.pem

       tlsclienttunnel crypt-addr plain-addr trustedkeys

       Tlssrv  is a helper program, typically exec'd in a /bin/service file to
       establish an SSL or TLS connection before launching cmd args; a typical
       command	might  start  the IMAP or HTTP server.	Cert.pem is the server
       certificate; factotum(4) should hold  the  corresponding	 private  key.
       The  specified  logfile	is  by	convention  the same as for the target
       server.	Remotesys is mainly used for logging.

       Tlsclient is the reverse of tlssrv: it dials address, starts  TLS,  and
       then  relays between the network connection and standard input and out‐
       put.  If the -t flag (and, optionally,  the  -x	flag)  is  given,  the
       remote  server must present a key whose SHA1 hash is listed in the file
       trustedkeys but not in the file excludedkeys.   See  thumbprint(6)  for
       more information.

       Tlssrvtunnel  and tlsclienttunnel use these tools and listen1 (see lis‐
       ten(8)) to provide TLS network tunnels, allowing legacy application  to
       take advantage of TLS encryption.

       Listen	for  TLS-encrypted  IMAP  by  creating	a  server  certificate
       /sys/lib/tls/imap.pem and a  listener  script  /bin/service.auth/tcp993

	      exec tlssrv -c/sys/lib/tls/imap.pem -limap4d -r`{cat $3/remote} \
		  /bin/ip/imap4d -p -dyourdomain -r`{cat $3/remote} \

       Interact	  with	 the   server,	 putting  the  appropriate  hash  into
       /sys/lib/tls/mail and running:

	      tlsclient -t /sys/lib/tls/mail tcp!server!imaps

       Create a TLS-encrypted VNC connection from a client  on	kremvax	 to  a
       server on moscvax:

	      mosc% vncs -d :3
	      mosc% tlssrvtunnel tcp!moscvax!5903 tcp!*!12345 \
	      krem% tlsclienttunnel tcp!moscvax!12345 tcp!*!5905 \
	      krem% vncv kremvax:5

       (The  port  numbers passed to the VNC tools are offset by 5900 from the
       actual TCP port numbers.)



       factotum(4), listen(8), rsa(8)
       Unix's stunnel

                             _         _         _ 
                            | |       | |       | |     
                            | |       | |       | |     
                         __ | | __ __ | | __ __ | | __  
                         \ \| |/ / \ \| |/ / \ \| |/ /  
                          \ \ / /   \ \ / /   \ \ / /   
                           \   /     \   /     \   /    
                            \_/       \_/       \_/ 
More information is available in HTML format for server Plan9

List of man pages available for Plan9

Copyright (c) for man pages and the logo by the respective OS vendor.

For those who want to learn more, the polarhome community provides shell access and support.

[legal] [privacy] [GNU] [policy] [cookies] [netiquette] [sponsors] [FAQ]
Polarhome, production since 1999.
Member of Polarhome portal.
Based on Fawad Halim's script.
Vote for polarhome
Free Shell Accounts :: the biggest list on the net