hmackeys(1) [debian man page]

HMACKEYS(1)							  BP executables						       HMACKEYS(1)

NAME

       hmackeys - utility program for generating good HMAC-SHA1 keys

SYNOPSIS

       hmackeys [ keynames_filename ]

DESCRIPTION

       hmackeys writes files containing randomized 160-bit key values suitable for use by HMAC-SHA1 in support of Bundle Authentication Block
       processing, Bundle Relay Service connections, or other functions for which symmetric hash computation is applicable.  One file is written
       for each key name presented to hmackeys; the content of each file is 20 consecutive randomly selected 8-bit integer values, and the name
       given to each file is simply "keyname.hmk".

       hmackeys operates in response to the key names found in the file keynames_filename, one name per file text line, if provided; if not,
       hmackeys prints a simple prompt (:) so that the user may type key names directly into standard input.

       When the program is run in interactive mode, either enter 'q' or press ^C to terminate.

EXIT STATUS

       0 Completion of key generation.

EXAMPLES

       hmackeys
	   Enter interactive HMAC/SHA1 key generation mode.

       hmackeys host1.keynames
	   Create a key file for each key name in host1.keynames, then terminate immediately.

FILES

       No other files are used in the operation of hmackeys.

ENVIRONMENT

       No environment variables apply.

DIAGNOSTICS

       The following diagnostics may be issued to the logfile ion.log:

       Can't open keynames file...
	   The keynames_filename specified in the command line doesn't exist.

BUGS

       Report bugs to <ion-bugs@korgano.eecs.ohiou.edu>

SEE ALSO

       brsscla(1), ionsecadmin(1)

perl v5.14.2							    2012-05-25							       HMACKEYS(1)

DTN2ADMIN(1)							  BP executables						      DTN2ADMIN(1)

NAME

       dtn2admin - baseline "dtn" scheme administration interface

SYNOPSIS

       dtn2admin [ commands_filename ]

DESCRIPTION

       dtn2admin configures the local ION node's routing of bundles to endpoints whose IDs conform to the dtn endpoint ID scheme.  dtn is a non-
       CBHE-conformant scheme.	The structure of dtn endpoint IDs remains somewhat in flux at the time of this writing, but endpoint IDs in the
       dtn scheme historically have been strings of the form "dtn://node_name[/demux_token]", where node_name normally identifies a computer
       somewhere on the network and demux_token normally identifies a specific application processing point.  Although the dtn endpoint ID scheme
       imposes more transmission overhead than the ipn scheme, ION provides support for dtn endpoint IDs to enable interoperation with other
       implementations of Bundle Protocol.

       dtn2admin operates in response to "dtn" scheme configuration commands found in the file commands_filename, if provided; if not, dtn2admin
       prints a simple prompt (:) so that the user may type commands directly into standard input.

       The format of commands for commands_filename can be queried from dtn2admin with the 'h' or '?' commands at the prompt.  The commands are
       documented in dtn2rc(5).

EXIT STATUS

       0 Successful completion of "dtn" scheme administration.
       1 Unsuccessful completion of "dtn" scheme administration, due to inability to attach to the Bundle Protocol system or to initialize the
       "dtn" scheme.

EXAMPLES

       dtn2admin
	   Enter interactive "dtn" scheme configuration command entry mode.

       dtn2admin host1.dtn2rc
	   Execute all configuration commands in host1.dtn2rc, then terminate immediately.

FILES

       See dtn2rc(5) for details of the DTN scheme configuration commands.

ENVIRONMENT

       No environment variables apply.

DIAGNOSTICS

       Note: all ION administration utilities expect source file input to be lines of ASCII text that are NL-delimited.  If you edit the dtn2rc
       file on a Windows machine, be sure to use dos2unix to convert it to Unix text format before presenting it to dtn2admin.	Otherwise
       dtn2admin will detect syntax errors and will not function satisfactorily.

       The following diagnostics may be issued to the logfile ion.log:

       dtn2admin can't attach to BP.
	   Bundle Protocol has not been initialized on this computer.  You need to run bpadmin(1) first.

       dtn2admin can't initialize routing database.
	   There is no SDR data store for dtn2admin to use.  Please run ionadmin(1) to start the local ION node.

       Can't open command file...
	   The commands_filename specified in the command line doesn't exist.

       Various errors that don't cause dtn2admin to fail but are noted in the ion.log log file may be caused by improperly formatted commands
       given at the prompt or in the commands_filename file.  Please see dtn2rc(5) for details.

BUGS

       Report bugs to <ion-bugs@korgano.eecs.ohiou.edu>

SEE ALSO

       dtn2rc(5)

perl v5.14.2							    2012-05-25							      DTN2ADMIN(1)