<div dir="ltr"><div dir="ltr"><div class="gmail_default" style="font-family:georgia,serif">Please note in the instructions, we indicated that RSA 2048 is only acceptable with expiration date of 2020 or sooner.<br> > 3k and now >= 4k have been recommendations for some time; <br>we include RSA2048 in web of trust currently only for migration purposes.<br></div><div class="gmail_default" style="font-family:georgia,serif">(E.g., sign a new key with an old key, set to expire 2020, and sign others' with both.)<br></div><div class="gmail_default" style="font-family:georgia,serif"><br></div><div class="gmail_default" style="font-family:georgia,serif">Pursuant to that policy statement, I will not recommend signing of your 2030 expiration date RSA2048.<br></div><div class="gmail_default" style="font-family:georgia,serif">(Folks may choose to disregard my advice.)<br></div><div class="gmail_default" style="font-family:georgia,serif"><br></div><div class="gmail_default" style="font-family:georgia,serif">You may sign others' keys after participating tonight, and if you do so with both your old key and a new key longer key signed by your old key, they can choose to sign the new key.<br></div><div class="gmail_default" style="font-family:georgia,serif"><br></div><div class="gmail_default" style="font-family:georgia,serif"><span style="font-family:monospace,monospace">pub rsa2048/7493DAEC 2018-05-05 [SCA] [expires: 2030-05-05]<br>uid [ unknown] James R. Doyle <<a href="mailto:rockymtnmagic@gmail.com">rockymtnmagic@gmail.com</a>><br>sub rsa2048/2408FE78 2018-05-05 [E] [expires: 2030-05-05]<br></span><br></div></div><div style="font-family:georgia,serif" class="gmail_default">// Bill </div><br><div class="gmail_quote"><div dir="ltr">On Tue, Sep 18, 2018 at 10:31 AM Jerry Feldman <<a href="mailto:gaf@blu.org">gaf@blu.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">When: September 19, 2018 7:00PM (6:30PM for Q&A)<br>
Topic: Crypto News, plus our annual PGP/GnuPG Key-Signing Party<br>
Moderator: Bill Ricker<br>
Location: MIT Building E-51, Room 335<br>
<br>
<br>
Please note that Wadsworth St is open from Memorial Drive to Amherst St,<br>
but is closed between Amherst St to Main St. See the ling below for<br>
additional details.<br>
<a href="https://courbanize.com/projects/mit-kendall-square/updates" rel="noreferrer" target="_blank">https://courbanize.com/projects/mit-kendall-square/updates</a><br>
<br>
Summary:<br>
<br>
Bill's annual crypto talk, PGP keysigning party. Register your key in<br>
advance to participate!<br>
<br>
Abstract:<br>
Bill reviews recent crypto news from the past year, and some crypto history.<br>
<br>
Cryptography News Highlights since the last year; e.g.,<br>
top named vulnerabilities<br>
preparing for post-Quantum cryptography<br>
books on Eliz. S. Friedman released (wrto Hidden Figures)<br>
<br>
The history portion may include horse farms, pumpkin patches, IBM<br>
punch-card accounting, and catching atom spies; or the Hidden Figures<br>
book connections; or something else entirely.<br>
<br>
Following Bill's presentation, we hold our annual keysigning party.<br>
<br>
------------------------ Additional information from Bill<br>
<br>
* We will NO LONGER sign RSA or DSA 1024b keys (or shorter). Obsolete.<br>
* We will NOT sign RSA 2048b keys without expiration dates<br>
or with expiration dates beyond 2020.<br>
* Use RSA 4096 or ed25519 for gpg2 --gen-key<br>
<br>
Notes<br>
* If concerned about well-capitalized massive factoring dictionaries,<br>
subtract a small multiple of 8 bits to get a size that is not standard<br>
and thus won't be dictionaried.<br>
* Alas the one trustworthy ECC curve, ed25519, is supported only in<br>
GPG 2.1.7+ (gpg2), but if you have recent Ubuntu you you can use it now.<br>
See <a href="https://nickhu.co.uk/posts/2016-09-03-curvy-gpg/" rel="noreferrer" target="_blank">https://nickhu.co.uk/posts/2016-09-03-curvy-gpg/</a><br>
<<a href="https://nickhu.co.uk/posts/2016-09-03-curvy-gpg/" rel="noreferrer" target="_blank">https://nickhu.co.uk/posts/2016-09-03-curvy-gpg/</a>> for instructions <br>
GPG2 gives a warning that it's not yet standardized so i'm considering<br>
it still somewhat expriemental ... i'm going to try a 10y expiring on this <br>
<br>
<br>
———————-<br>
<br>
A key signing party is a get-together of people who use the PGP<br>
encryption system with the purpose of allowing those people to sign each<br>
others keys. Key signing parties serve to extend the web of trust to a<br>
great degree. Key signing parties also serve as great opportunities to<br>
discuss the political and social issues surrounding strong cryptography,<br>
individual liberties, individual sovereignty, and even implementing<br>
encryption technologies or perhaps future work on free encryption software.<br>
<br>
The basic workflow of signing someone's key is as follows:<br>
<br>
Verify that the person actually is who they claim to be;<br>
Have them verify their key ID and fingerprint;<br>
Sign their key;<br>
Send the signed key back to them<br>
<br>
At the meeting, we go through the first two steps. Each person who<br>
preregistered their key will announce their presence and then read off<br>
their key ID and fingerprint, so everyone can verify that their copy of<br>
the list of keys is correct. Once we've run down the list, we line up,<br>
and each of us examines everyone else's photo IDs to verify that they<br>
are who they claim to be. After the meeting is over, each participant<br>
can then retrieve the keys that they've personally verified, sign those<br>
keys, and send the signed keys back to their respective owners.<br>
<br>
In order to complete the keysigning in the allotted time, we follow a<br>
formal procedure as seen in V. Alex Brennen's “GnuPG Keysigning Party<br>
HOWTO”:<br>
<a href="https://cryptnet.net/fdp/crypto/keysigning_party/en/keysigning_party.html" rel="noreferrer" target="_blank">https://cryptnet.net/fdp/crypto/keysigning_party/en/keysigning_party.html</a>. <br>
It is strongly advised that if you have not been to a keysigning party<br>
before, you read this document: <a href="http://blu.org/keysignings/" rel="noreferrer" target="_blank">http://blu.org/keysignings/</a>. We're using<br>
the List-based method for this keysigning party, and the keyserver at<br>
<a href="http://subkeys.pgp.net" rel="noreferrer" target="_blank">subkeys.pgp.net</a>.<br>
<br>
<br>
It is essential that, before the meeting, you register on the signup<br>
form listed in the attachments. You should bring at least one picture ID<br>
with you. You must also bring your own printout of the report on that<br>
page, so you can check off the names/keys of the people you have<br>
personally verified.<br>
<br>
The list will be printed on Wednesday afternoon, the day of the meeting;<br>
be sure to register your key for the keysigning before that. The<br>
official cutoff time is 3:00 pm.<br>
<br>
<br>
For further information and directions please consult the BLU Web site<br>
<a href="http://www.blu.org" rel="noreferrer" target="_blank">http://www.blu.org</a><br>
<br>
Parking:<br>
MIT lots require permits after hours.<br>
All Cambridge parking meters use Passport by Phone:<br>
<a href="https://www.cambridgema.gov/traffic/Parking/paybyphone" rel="noreferrer" target="_blank">https://www.cambridgema.gov/traffic/Parking/paybyphone</a><br>
This is active on all Cambridge metered parking spaces. Meters are free<br>
after 8PM<br>
<br>
For further information and directions please consult the BLU Web site<br>
<a href="http://www.blu.org" rel="noreferrer" target="_blank">http://www.blu.org</a><br>
<br>
-- <br>
Jerry Feldman <<a href="mailto:gaf@blu.org" target="_blank">gaf@blu.org</a>><br>
Boston Linux and Unix<br>
PGP key id:3BC1EB90<br>
PGP Key fingerprint: 49E2 C52A FC5A A31F 8D66 C0AF 7CEA 30FC 3BC1 EB90<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
Announce mailing list<br>
<a href="mailto:Announce@blu.org" target="_blank">Announce@blu.org</a><br>
<a href="http://lists.blu.org/mailman/listinfo/announce" rel="noreferrer" target="_blank">http://lists.blu.org/mailman/listinfo/announce</a><br>
</blockquote></div><br clear="all"><br>-- <br><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr">Bill Ricker<br><a href="mailto:bill.n1vux@gmail.com" target="_blank">bill.n1vux@gmail.com</a><div><a href="https://www.linkedin.com/in/n1vux" target="_blank">https://www.linkedin.com/in/n1vux</a> <br></div></div></div></div>