From 86bce23e53e6cc89ed5104b21a5fe33fab5a7a9f Mon Sep 17 00:00:00 2001 From: Russ Allbery Date: Thu, 24 Apr 2008 23:05:14 +0000 Subject: The wallet command-line client now reads the data for store from a file (using -f) or from standard input (if -f wasn't given) when the data isn't specified on the command line. The data still must not contain nul characters. --- client/wallet.pod | 44 ++++++++++++++++++++++++++------------------ 1 file changed, 26 insertions(+), 18 deletions(-) (limited to 'client/wallet.pod') diff --git a/client/wallet.pod b/client/wallet.pod index b6e8ff4..657929b 100644 --- a/client/wallet.pod +++ b/client/wallet.pod @@ -4,9 +4,9 @@ wallet - Client for retrieving secure data from a central server =head1 SYNOPSIS -B [B<-hv>] [B<-c> I] [B<-f> I] -[B<-k> I] [B<-p> I] [S I>] [B<-S> I] -[B<-u> I] I [I ...] +B [B<-hv>] [B<-c> I] [B<-f> I] + [B<-k> I] [B<-p> I] [S I>] + [B<-S> I] [B<-u> I] I [I ...] =head1 DESCRIPTION @@ -65,16 +65,17 @@ sometimes be useful to use a different prefix for testing a different version of the wallet code on the server. This option can also be set in F; see L below. -=item B<-f> I +=item B<-f> I -This flag is only used in combination with the C command. Rather -than sending the secure data to standard output (the default), store the -secure data in the file I. +This flag is only used in combination with the C and C +commands. For C, rather than sending the secure data to standard +output (the default), the secure data will be stored in I. For +C, the data to be stored will be read from I. -If the object being retrieved is not a keytab object, any current file -named I is renamed to F.bak> before the new file is -created. F.new> is used as a temporary file and any existing -file with that name will be deleted. +With C, if the object being retrieved is not a keytab object, any +current file named I is renamed to F.bak> before the new +file is created. F.new> is used as a temporary file and any +existing file with that name will be deleted. If the object being retrieved is a keytab object and the file I already exists, the downloaded keys will be added to the existing keytab @@ -83,6 +84,11 @@ ktremove> or an equivalent later to clean up old keys. F.new> is still used as a temporary file and any existing file with that name will be deleted. +C does not yet support nul bytes in I (or in any other way of +specifying the data to be stored). To store binary files in the wallet, +you will need to encode them with uuencode, base64, or some similar scheme +and then decode them after retrieval. + =item B<-k> I The service principal of the wallet server. The default is to use the @@ -323,15 +329,17 @@ name, the owner, any specific ACLs set on the object, the expiration if any, and the user, remote host, and time when the object was created, last stored, and last downloaded. -=item store +=item store [] Stores for the object identified by and for later -retrieval with C. Not all object types support this. - -Currently, is limited to not containing nul characters and may -therefore not be binary data, and is limited by the maximum command line -length of the operating system of the wallet server. These restrictions -will be lifted in the future. +retrieval with C. Not all object types support this. If is +not specified on the command line, it will be read from the file specified +with B<-f> (if given) or from standard input. + +Currently, the stored data must not contain nul characters and may +therefore not be binary data. Its length is also limited by the maximum +command line length of the operating system of the wallet server. These +restrictions will be lifted in the future. If an object with type and name does not already exist when this command is issued (as checked with the check interface), B -- cgit v1.2.3