[BACK]Return to signify.1 CVS log [TXT][DIR] Up to [local] / src / usr.bin / signify

Diff for /src/usr.bin/signify/signify.1 between version 1.3 and 1.4

version 1.3, 2013/12/31 11:03:53 version 1.4, 2013/12/31 17:33:17
Line 22 
Line 22 
 .Nd cryptographically sign and verify files  .Nd cryptographically sign and verify files
 .Sh SYNOPSIS  .Sh SYNOPSIS
 .Nm signify  .Nm signify
 .Op Fl I Ar input  
 .Op Fl N  .Op Fl N
   .Op Fl I Ar input
 .Op Fl O Ar output  .Op Fl O Ar output
 .Op Fl P Ar pubkey  .Op Fl P Ar pubkey
 .Op Fl S Ar seckey  .Op Fl S Ar seckey
 .Op Fl V Ar generate|sign|verify  .Fl V Ar generate | sign | verify
 .Sh DESCRIPTION  .Sh DESCRIPTION
 The  The
 .Nm  .Nm
 utility creates and verifies cryptographic signatures.  utility creates and verifies cryptographic signatures.
 The mode of operation is selected by the verb passed to the  The mode of operation is selected by the
 .Fl Ar V  .Fl V
 option.  option.
 Options are as follows  .Pp
 .Bl -tag -width iPPpubkey  The options are as follows:
   .Bl -tag -width Ds
 .It Fl I Ar input  .It Fl I Ar input
 Input file to  Input file to sign or verify.
 .Ar sign  
 or  
 .Ar verify .  
 .It Fl N  .It Fl N
 Do not ask for a passphrase during key generation.  Do not ask for a passphrase during key generation.
 Otherwise,  Otherwise,
 .Nm  .Nm
 will prompt the user for a passphrase on the tty.  will prompt the user for a passphrase on the terminal.
 .It Fl O Ar output  .It Fl O Ar output
 The signature file to create or verify.  The signature file to create or verify.
 The default is  The default is
Line 63 
Line 61 
 and used by  and used by
 .Ar sign  .Ar sign
 to sign a message.  to sign a message.
 .It Fl V Ar generate|sign|verify  .It Fl V Ar generate | sign | verify
 Select the desired operation.  Select the desired operation.
 .El  .El
 .Sh EXIT STATUS  .Pp
 The  The key and signature files created by
 .Nm  .Nm
 utility may fail for the following reasons:  have the same format.
   The first line of the file is a free form text comment that may be edited,
   so long as it does not exceed a single line.
   The second line of the file is the actual key or signature base64 encoded.
   .Sh EXIT STATUS
   .Ex -std signify
   It may fail because of one of the following reasons:
   .Pp
 .Bl -bullet -compact  .Bl -bullet -compact
 .It  .It
 Some necessary files do not exist.  Some necessary files do not exist.
 .It  .It
 Entered passphrase is incorrect.  Entered passphrase is incorrect.
Line 82 
Line 87 
 .El  .El
 .Sh EXAMPLES  .Sh EXAMPLES
 Create a new keypair:  Create a new keypair:
 .Dl "$ signify -P newkey.pub -S newkey.sec -V generate"  .Dl $ signify -P newkey.pub -S newkey.sec -V generate
 Sign a file, specifying signature name:  .Pp
 .Dl "$ signify -S key.sec -I message.txt -O msg.sig -V sign"  Sign a file, specifying a signature name:
   .Dl $ signify -S key.sec -I message.txt -O msg.sig -V sign
   .Pp
 Verify a signature, using the default signature name:  Verify a signature, using the default signature name:
 .Dl "$ signify -P key.pub -I generalsorders.txt -V verify"  .Dl $ signify -P key.pub -I generalsorders.txt -V verify
 .Sh FILES  
 The key and signature files created by  
 .Nm  
 have the same format.  
 The first line of the file is a free form text comment that may be edited,  
 so long as it does not exceed a single line.  
 The second line of the file is the actual key or signature base64 encoded.  
 .Sh SEE ALSO  .Sh SEE ALSO
 .Xr cmp 1 ,  .Xr cmp 1 ,
 .Xr sha256 1 ,  .Xr sha256 1 ,
Legend:
Removed from v.1.3  
changed lines
  Added in v.1.4