auth(8) [plan9 man page]

AUTH(8) 						      System Manager's Manual							   AUTH(8)

NAME

       changeuser, wrkey, convkeys, printnetkey, status, auth.srv, guard.srv - maintain authentication databases

SYNOPSIS

       auth/changeuser [-np] user

       auth/wrkey

       auth/convkeys [-p] keyfile

       auth/printnetkey user

       auth/status user

       auth/auth.srv

       auth/guard.srv

DESCRIPTION

       These  administrative commands run only on the authentication server.  Changeuser manipulates an authentication database file system served
       by keyfs(4) and used by file servers.  There are two authentication databases, one holding information about Plan 9 accounts and one  hold-
       ing  SecureNet  keys.   A  user need not be installed in both databases but must be installed in the Plan 9 database to connect to a Plan 9
       service.

       Changeuser installs or changes user in an authentication database.  It does not install a user on a Plan 9 file server; see fs(8) for that.

       Option -p installs user in the Plan 9 database.	Changeuser asks twice for a password for the new user.	If the responses do not  match	or
       the password is too easy to guess the user is not installed.

       Option -n installs user in the SecureNet database and prints out a key for the SecureNet box.  The key is chosen by changeuser.

       If neither option -p or option -n is given, changeuser installs the user in the Plan 9 database.

       Changeuser  prompts for biographical information such as email address, user name, sponsor and department number and appends it to the file
       /adm/netkeys.who or /adm/keys.who.

       Wrkey prompts for a machine key, host owner, and host domain and stores them in local non-volatile RAM.

       Convkeys re-encrypts the key file keyfile.  Re-encryption is performed in place.  Without the -p option convkeys uses  the  key	stored	in
       /dev/keys  to decrypt the file, and encrypts it using the new key.  By default, convkeys prompts twice for the new password.  The -p forces
       convkeys to also prompt for the old password.  The format of keyfile is described in keyfs(4).

       Printnetkey displays the network key as it should be entered into the hand-held Securenet box.

       Status is a shell script that prints out everything known about a user and the user's key status.

       Auth.srv is the program, run only on the authentication server, that handles ticket requests on IL port 566.  It is started by an  incoming
       call  to  the  server  requesting  a  conversation ticket; its standard input and output are the network connection.  Auth.srv executes the
       authentication server's end of the appropriate protocol as described in auth(6).

       Guard.srv is similar.  It is called whenever a foreign (e.g. Unix) system wants to do a SecureNet challenge/response authentication.

FILES

       /adm/keys.who
	      List of users in the Plan 9 database.

       /adm/netkeys.who
	      List of users in	the SecureNet database.

SOURCE

       /sys/src/cmd/auth

SEE ALSO

       keyfs(4), securenet(8)

																	   AUTH(8)

Check Out this Related Man Page

DRAWTERM(1)						      General Commands Manual						       DRAWTERM(1)

NAME

       drawterm - connect to Plan 9 CPU servers from other operating systems

SYNOPSIS

       drawterm [-d] [-a authserver] [-c cpuserver] [-e encription_hash_algs] [-k keyspec] [-s secstoreserver] [-u username] [-C command args ...]

DESCRIPTION

       drawterm  is not a Plan 9 program.  It is a program that users of non-Plan 9 systems can use to establish graphical cpu(1) connections with
       Plan 9 CPU servers.  Just as a real Plan 9 terminal does, a drawterm serves its local name space as well as  some  devices  (the  keyboard,
       mouse,  and  screen) to a remote CPU server, which mounts this name space on /mnt/term and starts a shell.  Typically, either explicitly or
       via the profile, one uses the shell to start rio(1).

       By default, drawterm uses the CPU server $cpu or cpu, and the authentication server $auth or auth,

OPTIONS

       This program follows the syntax of the cpu(1) Plan 9 command.

       A summary of options is included below.

       -h     Show summary of options.

       -a     Specifies the authentication server to use. If not present uses the $auth environment variable, if present, or  tries  with  a  host
	      name of auth.

       -c     Specifies the cpu server to use. If not present uses the $cpu environment variable, if present, or tries with a host name of cpu.

       -u     Specifies  the  username to authenticate with. If not present uses the $USER environment variable, if present, or asks interactively
	      for an username.

       -s     Specifies the secstore server to use.

       -C     Specifies a command to be executed remotely.

       -e,-k  Allow for selecting the hash algorithm and keys used, they have the same meaning as in cpu(1).

SOURCE

       In Plan 9 distributions, /sys/src/cmd/unix/drawterm.

DIAGNOSTICS

       Drawterm prints most diagnostics in its own window.

BUGS

       Although at first drawterm may seem like a Plan 9 terminal, in fact it is just a way to provide a CPU server with  some	terminal  devices.
       The  difference	is important because one cannot run terminal-resident programs when using drawterm.  The illusion can be improved by deli-
       cate adjustments in /usr/$user/lib/profile.

       Should import latest /dev/draw to allow resize of window

       Should copy 9term code and make console window a real 9term window instead.

       Should implement /dev/label.

SEE ALSO

       cpu(1), rio(1) in the Plan 9 documentation

AUTHOR

       drawterm was written by Russ Cox <rsc@swtch.com>.

       This manual page was written by Russ Cox <rsc@swtch.com>, with modifications by Martin Ferrari <tincho@debian.org> for the Debian project.

								 October 16, 2008						       DRAWTERM(1)

Linux and UNIX Man Pages

auth(8) [plan9 man page]

Check Out this Related Man Page