Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
I still had the scripts of the past few years, but I found on my system, I have sendmail disabled because of port forwarding, and the resulting shar did not work, so the script I am using uses the mailx client. On 09/25/2011 09:36 PM, John Abreau wrote: > Apparently some people didn't receive the attached bash script I had sent > to the list, so I've added it to the BLU website. You can find it at > > http://blu.org/meetings/2011/09/email-signed-keys.txt > > The script scrapes the BLU website to find the date of the most recent > BLU keysigning party, and uses the first email address it finds on your > signing key as the sender address. The script will walk you through the > process of signing each keyid you specify on the command line, fetching > each key from subkeys.php.net before asking if you want to sign it. > The script then generates a Batch-SMTP shar archive file containing > email messages to send each key to the email addresses found on the > key's uids, after exporting and encrypting the key so that only someone > with access to the corresponding secret key can read the message. > > > > On Sun, Sep 25, 2011 at 8:39 AM, Bill Bogstad <bogstad at pobox.com> wrote: >> Err, I don't use PGP, but I didn't see an attachment at my end. >> Perhaps the list software strips attachments? >> >> Bill Bogstad >> >> On Sun, Sep 25, 2011 at 5:38 AM, John Abreau <jabr at blu.org> wrote: >>> Attached is my bash script for signing keys after a BLU keysigning party. >>> Usage: >>> >>> email-signed-keys.sh [ --local-user keyid ] keyid keyid keyid .... >>> >>> If you want to sign with a secret key other than your default secret key, >>> use the "--local-user" option. >>> >>> The script prompts you to sign each key listed on the command line, >>> then produces a BSMTP (batch smtp) shar archive to email the >>> signed and encrypted keys to their owners so that only the person >>> who has each secret key can read the corresponding email. >>> >>> To avoid having to retype your pass phrase multiple times, it helps >>> to run gpg-agent to cache the pass phrase. >>> >>> >>> >>> -- >>> John Abreau / Executive Director, Boston Linux & Unix >>> Email jabr at blu.org / WWW http://www.abreau.net / PGP-Key-ID 0xD5C7B5D9 >>> PGP-Key-Fingerprint 72 FB 39 4F 3C 3B D6 5B E0 C8 5A 6E F1 2C BE 99 >>> >>> _______________________________________________ >>> Discuss mailing list >>> Discuss at blu.org >>> http://lists.blu.org/mailman/listinfo/discuss >>> >>> > > -- Jerry Feldman <gaf at blu.org> Boston Linux and Unix PGP key id:3BC1EB90 PGP Key fingerprint: 49E2 C52A FC5A A31F 8D66 C0AF 7CEA 30FC 3BC1 EB90
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |