[Pgpius-commit] pius README,1.1,1.1.2.1

[Phil D. <ja...@us...>]

Update of /cvsroot/pgpius/pius
In directory ddv4jf1.ch3.sourceforge.com:/tmp/cvs-serv10838

Modified Files:
      Tag: pius_2_x_branch
	README 
Log Message:
Update README.

- Phil


Index: README
===================================================================
RCS file: /cvsroot/pgpius/pius/README,v
retrieving revision 1.1
retrieving revision 1.1.2.1
diff -C2 -d -r1.1 -r1.1.2.1
*** README	5 Feb 2009 21:36:34 -0000	1.1
--- README	5 Feb 2009 23:08:08 -0000	1.1.2.1
***************
*** 5,9 ****
  PIUS started life as a group of bad shell scripts I had thrown together through
  the years after going to various PGP keysigning parties. These scripts
! automated various bits and pieces of signing various keys and UIDs, but feel
  short of actually making it a mostly painless process.
  
--- 5,9 ----
  PIUS started life as a group of bad shell scripts I had thrown together through
  the years after going to various PGP keysigning parties. These scripts
! automated various bits and pieces of signing various keys and UIDs, but fell
  short of actually making it a mostly painless process.
  
***************
*** 19,26 ****
  wanted to be able to let the user enter the passphrase directly into gpg for
  security reasons, (2) Using the --{command,passphrase,status}-fd options turned
! not to be not  that well documented and not work the way the documentation
  suggested.
  
! This method quickly showed itself to be very fragile. So, Imanaged to bend gpg
  to my will without using pexpect, and the only thing left that uses pexpect is
  the 'interactive' mode, which will probably one day go away if gpg-agent
--- 19,26 ----
  wanted to be able to let the user enter the passphrase directly into gpg for
  security reasons, (2) Using the --{command,passphrase,status}-fd options turned
! not to be not that well documented and not work the way the documentation
  suggested.
  
! This method quickly showed itself to be very fragile. So, I managed to bend gpg
  to my will without using pexpect, and the only thing left that uses pexpect is
  the 'interactive' mode, which will probably one day go away if gpg-agent
***************
*** 30,45 ****
  USAGE
  
! The simplest use form is
!   $ pius -e -s <your_keyid> <keyid>
  
  This will sign all UIDs on <keyid>, and export one copy of the for each UID
  with only that UID signed. These keys are exported into a file in /tmp named
  <keyid>__<id>.asc, where id is usually an email address if we can extract one,
! otherwise some other piece of the UID. The '-e' flag is what turns on the
! encryption of the outfiles, and the '-s' flag denotes the "signing" keyid. This
! default mode uses the pexpect mode to drop you into gpg at the right time so
! you can enter your passphrase directly into it. This means in this mode you
! will be prompted once for every UID on every key you sign. This mode will go
! away eventually.
  
  There are two other modes which you can enter by using -p or -a. The -p option
--- 30,44 ----
  USAGE
  
! The simplest (but least useful) use form is
!   $ pius -s <your_keyid> <keyid>
  
  This will sign all UIDs on <keyid>, and export one copy of the for each UID
  with only that UID signed. These keys are exported into a file in /tmp named
  <keyid>__<id>.asc, where id is usually an email address if we can extract one,
! otherwise some other piece of the UID. The '-s' flag denotes the "signing"
! keyid. This default mode uses the pexpect mode to drop you into gpg at the
! right time so you can enter your passphrase directly into it. This means in
! this mode you will be prompted once for every UID on every key you sign. This
! mode will go away eventually.
  
  There are two other modes which you can enter by using -p or -a. The -p option
***************
*** 53,68 ****
  After a keysigning party you probably have a party keyring provided by the
  organizer and want to sign most of the keys on it. In this case, don't specify
! the all the keyids to sign and instead probably want:
!   $ pius -A -r </path/to/keyring.gpg> -e -s <your_keyid>
  
  The -r flag specifies a keyring to use, and the -A flag says to sign all keyids
! on tha tkeyring. Since you are prompted to verify each fingerprint, you can say
! no to any people on the ring you were unable to verify.
  
  There are a variety of other options that you may want:
    * customize the tmpdir and outdir directories (-t and -o respectively)
    * select the signing level (-l)
    * import the unsigned keys to the default keyring (-i)
    * verbose mode (-v)
  
  And more! See the '-h' option for more.
--- 52,73 ----
  After a keysigning party you probably have a party keyring provided by the
  organizer and want to sign most of the keys on it. In this case, don't specify
! the all the keyids to sign and instead probably want something more like:
!   $ pius -p -A -r </path/to/keyring.gpg> -m <your_email> -s <your_keyid>
  
  The -r flag specifies a keyring to use, and the -A flag says to sign all keyids
! on that keyring. Since you are prompted to verify each fingerprint, you can say
! no to any people on the ring you were unable to verify. The -p flag, as
! previously mentioned, will catch your passphrase. -m will cause pius to email
! out the keys to the respective email addresses from <your_email>.
  
  There are a variety of other options that you may want:
    * customize the tmpdir and outdir directories (-t and -o respectively)
+   * encrypt the outfiles to <filename>_ENCRYPTED.asc (-e)
    * select the signing level (-l)
    * import the unsigned keys to the default keyring (-i)
    * verbose mode (-v)
+   * customize mail hostname and port (-H and -P respectively)
+   * customize the email message (-M)
+   * don't use PGP/Mime in the email (-O, implies -e)
  
  And more! See the '-h' option for more.