shithub: tlsclient

ref: c6a42c0410eb728bddab3c64d64991ec838fd643
dir: /tlsclient.1/

View raw version
.TH TLSCLIENT 1
.SH NAME
tlsclient \- 9front tls client
.SH SYNOPSIS
.B tlsclient
[
.B -bR
]
[
.B -u
.I user
]
[
.B -h
.I host
]
[
.B -a
.I auth
]
.B -p
.I port
command...
.SH DESCRIPTION
.B Tlsclient
may be used to establish encrypted tls tunnels with 9front
.B tlssrv
servers using p9any to derive pre-shared keys. The
.BR -u ,
.BR -h ,
and
.B -a
flags configure the paramaters for authentication.
These paramaters may also be configured through the
.IR USER ,
.IR CPU ,
and
.IR AUTH ,
environment variables respectively.
.PP
The
.I command
given is executed on the client, with its
standard input and output pointing to the output and input
of the remote connection. The
.B -R
flag changes this behavior, causing the
.I command
to be executed on the remote system in a
similar fashion to 9front's rcpu. In this
mode, if
.I command
is not specified a rc login shell is used.
The
.B -b
flag causes tlsclient to fork into the background.
.SH PASSWORDS
By default
.B tlsclient
will ask for the users' password through
.BR getpass (3).
For non interactive use the
.I PASS
environment variable may be used to specify
the password literal and
.I TLSCLIENT_ASKPASS
may be set to a program that will be executed
to provide the password on stdout.
.SH BUGS
The lack of factotum and portable namespaces make
this password business not fun.