uftp_keymgt(1)							uftp_keymgt(1)



NAME
       uftp_keymgt  -  Encrypted UDP based ftp with multicast - key management
       utility

SYNOPSIS
       uftp_keymgt [ -m ] [ key_file [ key_file ...] ]

       uftp_keymgt [ -m ] -g key_size key_file

       uftp_keymgt [ -m ] -d key_file


DESCRIPTION
       uftp_keymgt is a utility for creating, viewing, and deleting  RSA  pri‐
       vate  keys  used	 by the UFTP suite.  Although keys can be generated on
       the fly by uftp(1), uftpd(1), and uftpproxyd(1), this utility  gives  a
       more straightforward way of doing so without having to kick off a dummy
       transfer just to create/view a key.

       The definition of key_file is dependent on the crypto library  UFTP  is
       compiled to use.

       On Windows systems using the native crypto library (CryptoAPI), all RSA
       private keys must be stored in a key container (technically  only  keys
       used to sign data, but for UFTP's purposes this is the case).  Key con‐
       tainers are internal to Windows, and each user (and the system) has its
       own set of key containers.  In this case, key_file is actually the name
       of the key container.

       All other systems use OpenSSL for the crypto  library  (although	 under
       Windows	UFTP  can be also be built to use it).	In this case, key_file
       specifies a file name where the RSA private key is  stored  unencrypted
       in PEM format (the OS is expected to protect this file).

       The -g option is used to generate a key of a given size and store it in
       the given key_file.  The key size and key fingerprint are then printed.
       Under  OpenSSL,	a key can actually be generated by the openssl(1) com‐
       mand line utility, although you'll still need to run uftp_keymgt on  it
       to see the fingerprint.

       The -d option is available only on Windows systems using CryptoAPI.  It
       deletes the key container specified by key_file.

       When neither -g or -d are specified, the size and  fingerprint  of  all
       keys  listed  are printed.  If no keys are specified under Windows with
       CryptoAPI, the private key for all key containers for the current  user
       are  printed.  Note that some key containers may exist that an applica‐
       tion other than UFTP is using, and some of those may not	 have  an  RSA
       private key.


OPTIONS
       The following options are supported:

       -g key_size key_file
	      Specifies the size of the key to create in bits and the key_file
	      to store it in.

       -d key_file
	      Specifies the Windows key container to delete.

       -m     For Windows systems using CryptoAPI, private keys	 are  normally
	      stored  in  the  key  container of the running user.  Specifying
	      this option stores keys in the system key	 container.   On  non-
	      Windows systems, this option has no effect.

SEE ALSO
       uftp(1), uftpd(1), uftpproxyd(1)

NOTES
       The     latest	  version     of     UFTP     can    be	   found    at
       http://www.tcnj.edu/~bush/uftp.html.  UFTP is covered by the  GNU  Gen‐
       eral  Public  License.	Commercial  licenses and support are available
       from Dennis Bush (bush@tcnj.edu).



UFTP 3.7			 28 June 2012			uftp_keymgt(1)
