pgpius-commit Mailing List for PGP Individual UID Signer (Page 3)
Brought to you by:
jaymzh
Menu
▾
▴
pgpius-commit — Commit messages
You can subscribe to this list here.
| 2009 |
Jan
|
Feb
(12) |
Mar
(4) |
Apr
(3) |
May
|
Jun
|
Jul
|
Aug
|
Sep
(4) |
Oct
|
Nov
|
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2010 |
Jan
|
Feb
(5) |
Mar
(8) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(3) |
Oct
|
Nov
|
Dec
|
| 2011 |
Jan
|
Feb
|
Mar
(10) |
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2012 |
Jan
(3) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2013 |
Jan
|
Feb
|
Mar
(2) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Phil D. <ja...@us...> - 2009-02-07 00:52:26
|
Update of /cvsroot/pgpius/pius In directory ddv4jf1.ch3.sourceforge.com:/tmp/cvs-serv24958 Modified Files: Changelog README Log Message: Rolling 1.7 Index: README =================================================================== RCS file: /cvsroot/pgpius/pius/README,v retrieving revision 1.1 retrieving revision 1.2 diff -u -d -r1.1 -r1.2 --- README 5 Feb 2009 21:36:34 -0000 1.1 +++ README 7 Feb 2009 00:52:20 -0000 1.2 @@ -52,12 +52,16 @@ 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 all the keyids to sign. You probably also want to automatically send off +emails with the encrypted signatures to all of the UIDs that you verify. In +that case you want: + $ pius -A -e -m <your_email> -r </path/to/keyring.gpg> -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. +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 -e flag says to +encrypt the exported keyfile and the -m flag says to email it using the +provided address as the From. There are a variety of other options that you may want: * customize the tmpdir and outdir directories (-t and -o respectively) Index: Changelog =================================================================== RCS file: /cvsroot/pgpius/pius/Changelog,v retrieving revision 1.1 retrieving revision 1.2 diff -u -d -r1.1 -r1.2 --- Changelog 6 Feb 2009 23:35:51 -0000 1.1 +++ Changelog 7 Feb 2009 00:52:20 -0000 1.2 @@ -1,5 +1,5 @@ 1.7 -Released: +Released: 02/06/09 ph...@ip... - Adjust regex for email address to be much less restrictive |
|
From: Phil D. <ja...@us...> - 2009-02-07 00:49:19
|
Update of /cvsroot/pgpius/pius In directory ddv4jf1.ch3.sourceforge.com:/tmp/cvs-serv24389 Modified Files: Tag: pius_2_x_branch README pius Added Files: Tag: pius_2_x_branch COPYING Changelog Log Message: README: - Update for the new options/behaviors pius: - Remove extraneous comments - Order the imports - Fix the version - Change default tmp/out directories - Fix handling of -p, -i, and -a and thus simplify some option parsing - Make -p default - Add prompt about sending email if user didn't specify - Move import of keyring to end - add another TODO - from 1.7: Adjust regex for email address to be much less restrictive COPYING: - from 1.7: add license Changelog: - from 1.7: add changelog - add 2x stuff -phil Index: README =================================================================== RCS file: /cvsroot/pgpius/pius/README,v retrieving revision 1.1.2.1 retrieving revision 1.1.2.2 diff -u -d -r1.1.2.1 -r1.1.2.2 --- README 5 Feb 2009 23:08:08 -0000 1.1.2.1 +++ README 7 Feb 2009 00:49:10 -0000 1.1.2.2 @@ -1,5 +1,6 @@ PIUS: The PGP Individual UID Signer + INTRODUCTION PIUS started life as a group of bad shell scripts I had thrown together through @@ -36,23 +37,16 @@ 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. +keyid. -There are two other modes which you can enter by using -p or -a. The -p option -causes PIUS to prompt for your passpharse at startup and feed it to gpg when -needed. The passphrase is only stored in memory, but since we don't require -root (or setuid) we don't lock memory. This may raise security issues if there -are untrusted individuals on the system (but for single user desktops shouldn't -be an issue). The -a mode will attempt to use gpg-agent. This is the most -secure and convenient method, but sometimes gpg-agent can be flaky. +Note this default mode will prompt for your passphrase and cache it for the life +of the execution so that it can provide it to GnuPG. There are other options, +please see the SECURITY IMPLICATIONS section below. 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> + $ pius -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 @@ -64,7 +58,7 @@ * 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) + * 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) @@ -73,6 +67,31 @@ And more! See the '-h' option for more. +SECURITY IMPLICATIONS + +The default mode for pius, starting in 2.0.0 is 'cache_passphrase' mode. This +means that pius will ask you for your passphrase at startup, verify this +passphrase is correct, and then feed it GnuPG everytime it needs it. The +passphrase is stored in memory and only for the life of the execution of pius. +For most users this should be relatively safe. However, it is worth noting that +if you are on a machine whose system administrators you don't trust, there is a +small danger of them reading this memory while pius is running. + +There are two alternatives for people not comfortable with this. The first is to +use the agent mode. By specifying -a, pius will ask gpg to get the passphrase +from an gpg-agent. You will need to have your gpg-agent setup and running. +However, gpg-agent can be rather flaky, so we recommend you pre-seed by doing +something that requires your private keys so it can cache your keys before you +run pius. + +Finally we have 'interactive mode' which can be entered using -i. This will use +pexpect to handle most of the signing interactions and then drop you into the +'gpg --edit-key' shell whenever gpg needs a passphrase. Using this you can enter +your passphrase directly into gpg. This mode has two main disadvantages. The +first is that the pexpect code is quite fragile, and the second is that you'll +have to type your passphrase for every key-UID combination. + + A NOTE ON SENDING EMAILS When PIUS emails out keys it BCC's you, so you will get a copy of every email @@ -84,8 +103,15 @@ option to forcefully override the TO in the envelope of the email. When doing this *only* the address specified as an argument to -n will get the email. + LICENSE PIUS is released under the GNU Public License v2 and is Copyright Phil Dibowitz <ph...@ip...>. + +Phil Dibowitz +ph...@ip... + + +# vim:shiftwidth=2:tabstop=2:expandtab:textwidth=80:softtabstop=2:ai: Index: pius =================================================================== RCS file: /cvsroot/pgpius/pius/pius,v retrieving revision 1.7.2.1 retrieving revision 1.7.2.2 diff -u -d -r1.7.2.1 -r1.7.2.2 --- pius 5 Feb 2009 22:10:46 -0000 1.7.2.1 +++ pius 7 Feb 2009 00:49:10 -0000 1.7.2.2 @@ -3,17 +3,6 @@ # vim:shiftwidth=2:tabstop=2:expandtab:textwidth=80:softtabstop=2:ai: # -# This script was made from a shoddy group of shell scripts that tried to make -# this work easier. However, gpg doesn't give the nicest interface for -# automation, and this evolved into a much more complex script. -# -# Wherever possible we use the --*-fd options to gpg for automation rather -# than screenscraping (using pexpect) since it's more resiliant. However, -# until working with gpg-agent is full working the 'interactive' mode (which -# requires pexpect) will remain in the code. -# -# Note that the only way to specify a UID is in --edit-key, without --batch. -# # Copyright (c) 2008 - 2009 Phil Dibowitz (ph...@ip...) # # This program is free software; you can redistribute it and/or @@ -22,15 +11,16 @@ # # TODO: # - Offer ability to "pick up where we left off" +# - Add TLS/auth support to SMTP # from email import MIMEBase from email import MIMEMultipart from email import MIMEText from email.Utils import formatdate -import getpass -from optparse import OptionParser, Option, OptionValueError from copy import copy +from optparse import OptionParser, Option, OptionValueError +import getpass import os import pexpect import re @@ -40,7 +30,7 @@ import sys import time -VERSION = '1.6+DEV' +VERSION = '2.0.0-BETA' debug_on = False MODE_INTERACTIVE = 0 @@ -49,8 +39,8 @@ DEFAULT_GPG_PATH = '/usr/bin/gpg' DEFAULT_KEYRING = '~/.gnupg/pubring.gpg' -DEFAULT_TMP_DIR = '/tmp' -DEFAULT_OUT_DIR = '/tmp' +DEFAULT_TMP_DIR = '/tmp/pius_tmp' +DEFAULT_OUT_DIR = '/tmp/pius_out' DEFAULT_MAIL_HOST = 'localhost' DEFAULT_MAIL_PORT = 25 @@ -958,7 +948,7 @@ return value def check_email(option, opt, value): - m = re.match('\w+@\w+\.\w+', value) + m = re.match('.+@.+\..+', value) if not m: raise OptionValueError('Option %s: Value %s does not appear like a well' ' formed email address' % (opt, value)) @@ -990,9 +980,6 @@ if not options.signer: parser.error('You must specify a keyid to sign with.') - if options.cache_passphrase and options.agent: - parser.error('You can only select one (or none) of -a or -p') - if options.keyring: options.keyring = os.path.expanduser(options.keyring) if not os.path.exists(options.keyring): @@ -1023,16 +1010,18 @@ ' %prog [options] -A -r <keyring_path> -s <signer_keyid>') parser = OptionParser(usage=usage, version='%%prog %s' % VERSION, option_class=MyOption) - parser.set_defaults(gpg_path=DEFAULT_GPG_PATH, + parser.set_defaults(mode=MODE_CACHE_PASSPHRASE, + gpg_path=DEFAULT_GPG_PATH, out_dir=DEFAULT_OUT_DIR, tmp_dir=DEFAULT_TMP_DIR, keyring=DEFAULT_KEYRING, mail_host=DEFAULT_MAIL_HOST, mail_port=DEFAULT_MAIL_PORT, sign_level='3') - parser.add_option('-a', '--use-agent', action='store_true', dest='agent', + parser.add_option('-a', '--use-agent', action='store_const', const=MODE_AGENT, + dest='mode', help='Use pgp-agent instead of letting gpg prompt the' - ' user for every UID.') + ' user for every UID. [default: false]') parser.add_option('-A', '--all-keys', action='store_true', dest='all_keys', help='Sign all keys on the keyring. Requires -r.') parser.add_option('-b', '--gpg-path', dest='gpg_path', metavar='PATH', @@ -1045,7 +1034,11 @@ help='Enable debugging output.') parser.add_option('-H', '--mail_host', dest='mail_host', metavar='HOSTNAME', nargs=1, help='Hostname of SMTP server. [default: %default]') - parser.add_option('-i', '--import', action='store_true', + parser.add_option('-i', '--interactive', action='store_const', + const=MODE_INTERACTIVE, dest='mode', help='Use the pexpect' + ' module for signing and drop to the gpg shell for' + ' entering the passphrase. [default: false]') + parser.add_option('-I', '--import', action='store_true', dest='import_keyring', help='Also import the unsigned keys from the keyring' ' into the default keyring. Ignored if -r is not' @@ -1075,11 +1068,11 @@ parser.add_option('-O', '--no-pgp-mime', action='store_true', dest='no_pgp_mime', help='Do not use PGP/Mime when sending email.') - parser.add_option('-p', '--cache_passphrase', action='store_true', - dest='cache_passphrase', + parser.add_option('-p', '--cache_passphrase', action='store_const', + const=MODE_CACHE_PASSPHRASE, dest='mode', help='Cache private key passphrase in memory and provide' ' it to gpg instead of letting gpg prompt the user' - ' for every UID.') + ' for every UID. [default: true]') parser.add_option('-P', '--mail_port', dest='mail_port', metavar='PORT', nargs=1, type='int', help='Port of SMTP server. [default: %default]') @@ -1111,18 +1104,23 @@ # Check input to make sure users want sane things check_options(parser, options, args) - - mode = MODE_INTERACTIVE - if options.cache_passphrase: - mode = MODE_CACHE_PASSPHRASE - elif options.agent: - mode = MODE_AGENT - p = uids_signer(options.signer, mode, options.keyring, options.gpg_path, - options.tmp_dir, options.out_dir, options.encrypt_outfiles, - options.sign_level, options.mail, options.verbose, - options.mail_text, options.override_email, options.mail_host, - options.mail_port, options.no_pgp_mime) + # Check to see if the user wants to send email if they didn't specify + if not options.mail: + ans = raw_input('Would you like to automatically send the signed UIDs to' + ' their owners using\nPGP/Mime encryption as you sign each' + ' one? ') + if ans in ('y', 'Y', 'yes', 'YES', 'Yes'): + ans = raw_input('What email address should we send from? ') + check_email(parser, '-m', ans) + options.mail = ans + print + + p = uids_signer(options.signer, options.mode, options.keyring, + options.gpg_path, options.tmp_dir, options.out_dir, + options.encrypt_outfiles, options.sign_level, options.mail, + options.verbose, options.mail_text, options.override_email, + options.mail_host, options.mail_port, options.no_pgp_mime) if options.all_keys: list = p.get_all_keyids() @@ -1134,16 +1132,8 @@ else: list = args - if options.import_keyring: - if ((not options.keyring) or (options.keyring == DEFAULT_KEYRING)): - print ('WARNING: Ignoring -i: Either -r wasn\'t specified, or it was' - ' the same as the default keyring.') - else: - p.import_unsigned_keys() - - if options.cache_passphrase: - print ('WARNING: Using the -p option may have negative security' - ' implications!') + if options.mode == MODE_CACHE_PASSPHRASE: + print ('NOTE: See the README about security implications.') while not p.passphrase_confirmed: p.get_passphrase() if not p.verify_passphrase(): @@ -1156,6 +1146,14 @@ print 'Signing all UIDs on key %s' % key p.sign_all_uids(key) + # If the user asked, import the keys + if options.import_keyring: + if ((not options.keyring) or (options.keyring == DEFAULT_KEYRING)): + print ('WARNING: Ignoring -i: Either -r wasn\'t specified, or it was' + ' the same as the default keyring.') + else: + p.import_unsigned_keys() + p.cleanup() main() --- NEW FILE: COPYING --- Copyright (C) 2007 Phil Dibowitz (ph...@ip...) This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, version 2. Note that the only valid version of the GPL as far as this software is concerned is _this_ particular version of the license (ie v2, not v2.2 or v3.x or whatever), unless explicitly otherwise stated. - Phil Dibowitz ------------------------------------------------------------------------- GNU GENERAL PUBLIC LICENSE Version 2, June 1991 Copyright (C) 1989, 1991 Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. Preamble The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users. This General Public License applies to most of the Free Software Foundation's software and to any other program whose authors commit to using it. (Some other Free Software Foundation software is covered by the GNU Lesser General Public License instead.) You can apply it to your programs, too. When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs; and that you know you can do these things. To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to surrender the rights. These restrictions translate to certain responsibilities for you if you distribute copies of the software, or if you modify it. For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the rights that you have. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights. We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which gives you legal permission to copy, distribute and/or modify the software. Also, for each author's protection and ours, we want to make certain that everyone understands that there is no warranty for this free software. If the software is modified by someone else and passed on, we want its recipients to know that what they have is not the original, so that any problems introduced by others will not reflect on the original authors' reputations. Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that redistributors of a free program will individually obtain patent licenses, in effect making the program proprietary. To prevent this, we have made it clear that any patent must be licensed for everyone's free use or not licensed at all. The precise terms and conditions for copying, distribution and modification follow. GNU GENERAL PUBLIC LICENSE TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION 0. This License applies to any program or other work which contains a notice placed by the copyright holder saying it may be distributed under the terms of this General Public License. The "Program", below, refers to any such program or work, and a "work based on the Program" means either the Program or any derivative work under copyright law: that is to say, a work containing the Program or a portion of it, either verbatim or with modifications and/or translated into another language. (Hereinafter, translation is included without limitation in the term "modification".) Each licensee is addressed as "you". Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program). Whether that is true depends on what the Program does. 1. You may copy and distribute verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and give any other recipients of the Program a copy of this License along with the Program. You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee. 2. You may modify your copy or copies of the Program or any portion of it, thus forming a work based on the Program, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions: a) You must cause the modified files to carry prominent notices stating that you changed the files and the date of any change. b) You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License. c) If the modified program normally reads commands interactively when run, you must cause it, when started running for such interactive use in the most ordinary way, to print or display an announcement including an appropriate copyright notice and a notice that there is no warranty (or else, saying that you provide a warranty) and that users may redistribute the program under these conditions, and telling the user how to view a copy of this License. (Exception: if the Program itself is interactive but does not normally print such an announcement, your work based on the Program is not required to print an announcement.) These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Program, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it. Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Program. In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on the Program) on a volume of a storage or distribution medium does not bring the other work under the scope of this License. 3. You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following: a) Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or, b) Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or, c) Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for noncommercial distribution and only if you received the program in object code or executable form with such an offer, in accord with Subsection b above.) The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable. However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable. If distribution of executable or object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place counts as distribution of the source code, even though third parties are not compelled to copy the source along with the object code. 4. You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense or distribute the Program is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance. 5. You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Program (or any work based on the Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Program or works based on it. 6. Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties to this License. 7. If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Program at all. For example, if a patent license would not permit royalty-free redistribution of the Program by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Program. If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply and the section as a whole is intended to apply in other circumstances. It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system, which is implemented by public license practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice. This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License. 8. If the distribution and/or use of the Program is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Program under this License may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this License. 9. The Free Software Foundation may publish revised and/or new versions of the General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. Each version is given a distinguishing version number. If the Program specifies a version number of this License which applies to it and "any later version", you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation. 10. If you wish to incorporate parts of the Program into other free programs whose distribution conditions are different, write to the author to ask for permission. For software which is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally. NO WARRANTY 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. END OF TERMS AND CONDITIONS How to Apply These Terms to Your New Programs If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms. To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively convey the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found. <one line to give the program's name and a brief idea of what it does.> Copyright (C) <year> <name of author> This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA. Also add information on how to contact you by electronic and paper mail. If the program is interactive, make it output a short notice like this when it starts in an interactive mode: Gnomovision version 69, Copyright (C) year name of author Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'. This is free software, and you are welcome to redistribute it under certain conditions; type `show c' for details. The hypothetical commands `show w' and `show c' should show the appropriate parts of the General Public License. Of course, the commands you use may be called something other than `show w' and `show c'; they could even be mouse-clicks or menu items--whatever suits your program. You should also get your employer (if you work as a programmer) or your school, if any, to sign a "copyright disclaimer" for the program, if necessary. Here is a sample; alter the names: Yoyodyne, Inc., hereby disclaims all copyright interest in the program `Gnomovision' (which makes passes at compilers) written by James Hacker. <signature of Ty Coon>, 1 April 1989 Ty Coon, President of Vice This General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Lesser General Public License instead of this License. --- NEW FILE: Changelog --- 2.0.0 Released: ph...@ip... - Add support for PGP/Mime, make it default - Significant improvement to error checking and handling of gpg calls - Minimize keys in import - Better input checking - Various code cleanups - Support named interpolation in email templates - Use proper extension for our tmp keyring - Change default tmp/out directories to something more sane - Fix handling of mode (-p, -i, -a) - Make cache_passphrase mode default - Add prompt about sending email if user didn't specify - Move import of keyring to end 1.7 Released: ph...@ip... - Adjust regex for email address to be much less restrictive 1.6 Released: 02/02/09 ph...@ip... - fix a debug line - fix a bug where we think a key is bad just because it has one expired subkey. 1.5 Released: 02/01/09 ph...@ip... - don't include full file path in mime headers, just filename - add configuration for specifying mail server host/port - clean up some error messages - add some hints to the option parser - use parser.error instead of print/exit for option issues - Significantly better checking on commandline options - Handle bad UIDs passed by the user smoothly - Some code refactoring 1.4 Released: 01/28/09 ph...@ip... - don't try to email if encryption failed. 1.3 Released: 01/28/09 ph...@ip... - add propfer filename to mime headers -phil - fix a warning - add some spacing and comments - adding support for utf8/paryn/whatever in comments - More fixes for UTF-8/special chars - handle expired subkeys nicely - When using override_email, make sure we put that in the headers not just the envelope - some helpful info in help 1.2 Released: 11/22/08 ph...@ip... - encrypt to ascii-armored - add option to import keyring - add todo - Handle UIDs without email addresses - Add option to try signing all keys on a keyring (-A) - Add 'quit' option to the "Have you verified this user/key?" prompt - Significantly improve parsing in get_uids() - Name files for conflicting emails *much* better (foo_2.asc, foo_3.asc, instead of foo.asc_2, foo.asc_2_2) - Name encrypted files MUCH better (foo_ENCRYPTED.asc instead of foo.asc.asc) - Better error handling on encryption errors - When getting all keys from the keyring (-A) use short keyid - a few additional fixes for UIDs without email addresses - much better help messages for options - fix buggy error message on keyring not existing - Add abaility to email off signed keys to respective emails - allow users to use tilde-expansion in keyring paths - update TODO list - alphabetize imports - update TODO - Put default email text in a variable - Add ability to override email text - Add ability to print default email text - Add ability to override email To - Add doc strings - Abstract commonly used gpg options into variables - minor cleanups in sign_all_uids() - remove unused code - separate printing of filenames into --verbose option 1.1 Released 11/20/08 ph...@ip... - get FD stuff working for -p - start working on FD stuff for -a - fix a variety of pathing bugs - make sign_uid_expect return the right vals - fix output to use --no-tty where necessary - tons of cleanups - add new use-agent mode (-a) - tmpdir is now configurable (-t) - outdir is now configurable (-o) - gpg bin is now configurable (-b) - sig level is now configurable (-l) - pius can now optionally encrypt the files for you (-e) - stop using the special word 'file' as a variable - better debugging - handle PGP2 keys better - cleanup all tmp files and keyrings - fix usage info 1.0 ph...@ip... - Original version... floating around in various forms for a long time |
|
From: Phil D. <ja...@us...> - 2009-02-06 23:38:15
|
Update of /cvsroot/pgpius/pius In directory ddv4jf1.ch3.sourceforge.com:/tmp/cvs-serv10193 Modified Files: pius Added Files: COPYING Log Message: COPYING - Adding copy of GPLv2 pius - comment cleanup Index: pius =================================================================== RCS file: /cvsroot/pgpius/pius/pius,v retrieving revision 1.7 retrieving revision 1.8 diff -C2 -d -r1.7 -r1.8 *** pius 5 Feb 2009 21:51:04 -0000 1.7 --- pius 6 Feb 2009 23:38:11 -0000 1.8 *************** *** 4,18 **** # - # This script was made from a shoddy group of shell scripts that tried to make - # this work easier. However, gpg doesn't give the nicest interface for - # automation, and this evolved into a much more complex script. - # - # Wherever possible we use the --*-fd options to gpg for automation rather - # than screenscraping (using pexpect) since it's more resiliant. However, - # until working with gpg-agent is full working the 'interactive' mode (which - # requires pexpect) will remain in the code. - # - # Note that the only way to specify a UID is in --edit-key, without --batch. - # # Copyright (c) 2008 - 2009 Phil Dibowitz (ph...@ip...) # --- 4,7 ---- *************** *** 41,45 **** import time ! VERSION = '1.6' debug_on = False --- 30,34 ---- import time ! VERSION = '1.7' debug_on = False *************** *** 728,732 **** def check_email(option, opt, value): ! m = re.match('\w+@\w+\.\w+', value) if not m: raise OptionValueError('Option %s: Value %s does not appear like a well' --- 717,721 ---- def check_email(option, opt, value): ! m = re.match('.+@.+\..+', value) if not m: raise OptionValueError('Option %s: Value %s does not appear like a well' --- NEW FILE: COPYING --- Copyright (C) 2007 Phil Dibowitz (ph...@ip...) This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, version 2. Note that the only valid version of the GPL as far as this software is concerned is _this_ particular version of the license (ie v2, not v2.2 or v3.x or whatever), unless explicitly otherwise stated. - Phil Dibowitz ------------------------------------------------------------------------- GNU GENERAL PUBLIC LICENSE Version 2, June 1991 Copyright (C) 1989, 1991 Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. Preamble The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users. This General Public License applies to most of the Free Software Foundation's software and to any other program whose authors commit to using it. (Some other Free Software Foundation software is covered by the GNU Lesser General Public License instead.) You can apply it to your programs, too. When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs; and that you know you can do these things. To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to surrender the rights. These restrictions translate to certain responsibilities for you if you distribute copies of the software, or if you modify it. For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the rights that you have. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights. We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which gives you legal permission to copy, distribute and/or modify the software. Also, for each author's protection and ours, we want to make certain that everyone understands that there is no warranty for this free software. If the software is modified by someone else and passed on, we want its recipients to know that what they have is not the original, so that any problems introduced by others will not reflect on the original authors' reputations. Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that redistributors of a free program will individually obtain patent licenses, in effect making the program proprietary. To prevent this, we have made it clear that any patent must be licensed for everyone's free use or not licensed at all. The precise terms and conditions for copying, distribution and modification follow. GNU GENERAL PUBLIC LICENSE TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION 0. This License applies to any program or other work which contains a notice placed by the copyright holder saying it may be distributed under the terms of this General Public License. The "Program", below, refers to any such program or work, and a "work based on the Program" means either the Program or any derivative work under copyright law: that is to say, a work containing the Program or a portion of it, either verbatim or with modifications and/or translated into another language. (Hereinafter, translation is included without limitation in the term "modification".) Each licensee is addressed as "you". Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program). Whether that is true depends on what the Program does. 1. You may copy and distribute verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and give any other recipients of the Program a copy of this License along with the Program. You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee. 2. You may modify your copy or copies of the Program or any portion of it, thus forming a work based on the Program, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions: a) You must cause the modified files to carry prominent notices stating that you changed the files and the date of any change. b) You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License. c) If the modified program normally reads commands interactively when run, you must cause it, when started running for such interactive use in the most ordinary way, to print or display an announcement including an appropriate copyright notice and a notice that there is no warranty (or else, saying that you provide a warranty) and that users may redistribute the program under these conditions, and telling the user how to view a copy of this License. (Exception: if the Program itself is interactive but does not normally print such an announcement, your work based on the Program is not required to print an announcement.) These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Program, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it. Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Program. In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on the Program) on a volume of a storage or distribution medium does not bring the other work under the scope of this License. 3. You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following: a) Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or, b) Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or, c) Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for noncommercial distribution and only if you received the program in object code or executable form with such an offer, in accord with Subsection b above.) The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable. However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable. If distribution of executable or object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place counts as distribution of the source code, even though third parties are not compelled to copy the source along with the object code. 4. You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense or distribute the Program is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance. 5. You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Program (or any work based on the Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Program or works based on it. 6. Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties to this License. 7. If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Program at all. For example, if a patent license would not permit royalty-free redistribution of the Program by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Program. If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply and the section as a whole is intended to apply in other circumstances. It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system, which is implemented by public license practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice. This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License. 8. If the distribution and/or use of the Program is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Program under this License may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this License. 9. The Free Software Foundation may publish revised and/or new versions of the General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. Each version is given a distinguishing version number. If the Program specifies a version number of this License which applies to it and "any later version", you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation. 10. If you wish to incorporate parts of the Program into other free programs whose distribution conditions are different, write to the author to ask for permission. For software which is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally. NO WARRANTY 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. END OF TERMS AND CONDITIONS How to Apply These Terms to Your New Programs If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms. To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively convey the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found. <one line to give the program's name and a brief idea of what it does.> Copyright (C) <year> <name of author> This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA. Also add information on how to contact you by electronic and paper mail. If the program is interactive, make it output a short notice like this when it starts in an interactive mode: Gnomovision version 69, Copyright (C) year name of author Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'. This is free software, and you are welcome to redistribute it under certain conditions; type `show c' for details. The hypothetical commands `show w' and `show c' should show the appropriate parts of the General Public License. Of course, the commands you use may be called something other than `show w' and `show c'; they could even be mouse-clicks or menu items--whatever suits your program. You should also get your employer (if you work as a programmer) or your school, if any, to sign a "copyright disclaimer" for the program, if necessary. Here is a sample; alter the names: Yoyodyne, Inc., hereby disclaims all copyright interest in the program `Gnomovision' (which makes passes at compilers) written by James Hacker. <signature of Ty Coon>, 1 April 1989 Ty Coon, President of Vice This General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Lesser General Public License instead of this License. |
|
From: Phil D. <ja...@us...> - 2009-02-06 23:35:57
|
Update of /cvsroot/pgpius/pius In directory ddv4jf1.ch3.sourceforge.com:/tmp/cvs-serv9647 Added Files: Changelog Log Message: Add a changelog --- NEW FILE: Changelog --- 1.7 Released: ph...@ip... - Adjust regex for email address to be much less restrictive 1.6 Released: 02/02/09 ph...@ip... - fix a debug line - fix a bug where we think a key is bad just because it has one expired subkey. 1.5 Released: 02/01/09 ph...@ip... - don't include full file path in mime headers, just filename - add configuration for specifying mail server host/port - clean up some error messages - add some hints to the option parser - use parser.error instead of print/exit for option issues - Significantly better checking on commandline options - Handle bad UIDs passed by the user smoothly - Some code refactoring 1.4 Released: 01/28/09 ph...@ip... - don't try to email if encryption failed. 1.3 Released: 01/28/09 ph...@ip... - add propfer filename to mime headers -phil - fix a warning - add some spacing and comments - adding support for utf8/paryn/whatever in comments - More fixes for UTF-8/special chars - handle expired subkeys nicely - When using override_email, make sure we put that in the headers not just the envelope - some helpful info in help 1.2 Released: 11/22/08 ph...@ip... - encrypt to ascii-armored - add option to import keyring - add todo - Handle UIDs without email addresses - Add option to try signing all keys on a keyring (-A) - Add 'quit' option to the "Have you verified this user/key?" prompt - Significantly improve parsing in get_uids() - Name files for conflicting emails *much* better (foo_2.asc, foo_3.asc, instead of foo.asc_2, foo.asc_2_2) - Name encrypted files MUCH better (foo_ENCRYPTED.asc instead of foo.asc.asc) - Better error handling on encryption errors - When getting all keys from the keyring (-A) use short keyid - a few additional fixes for UIDs without email addresses - much better help messages for options - fix buggy error message on keyring not existing - Add abaility to email off signed keys to respective emails - allow users to use tilde-expansion in keyring paths - update TODO list - alphabetize imports - update TODO - Put default email text in a variable - Add ability to override email text - Add ability to print default email text - Add ability to override email To - Add doc strings - Abstract commonly used gpg options into variables - minor cleanups in sign_all_uids() - remove unused code - separate printing of filenames into --verbose option 1.1 Released 11/20/08 ph...@ip... - get FD stuff working for -p - start working on FD stuff for -a - fix a variety of pathing bugs - make sign_uid_expect return the right vals - fix output to use --no-tty where necessary - tons of cleanups - add new use-agent mode (-a) - tmpdir is now configurable (-t) - outdir is now configurable (-o) - gpg bin is now configurable (-b) - sig level is now configurable (-l) - pius can now optionally encrypt the files for you (-e) - stop using the special word 'file' as a variable - better debugging - handle PGP2 keys better - cleanup all tmp files and keyrings - fix usage info 1.0 ph...@ip... - Original version... floating around in various forms for a long time |
|
From: Phil D. <ja...@us...> - 2009-02-05 23:08:16
|
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. |
