[mats] PGP keyserver

Tuesday, 21 April, Year 7 d.Tr. | Author: Mircea Popescu

A server that :

  1. Accepts key material both via GnuPG's direct call on port 11371 or through a plain post request (armored pubkey) on port 80 ;
  2. Verifies key material so that it is RSA, at least 4096 bits ;
  3. Verifies key material through phuctor to eliminate weak keys (phuctor code does not need to be rewritten) ;
  4. Verifies key material was created by a GnuPG version ulterior to 1.4.10 and prior to 1.4.20 ;
  5. Verifies that key material is not set to expire ;
  6. Emails the contained address an error if tests 2 or 3 above are failed (all addresses involved in case of 3), and rejects the key. Emails the contained address an explicatory warning if test 4i or 5ii above is failed, but accepts the key. Emails the contained address a confirmation if no tests are failed.
  7. Answers for requests for specified keys on the normal hkp port (11371) as expected by GnuPG.
  8. Displays keys in a plain manner similar to sks-keyservers but with all the colorful joy of phuctor's css.
  9. Allows web-based searches for keys, by the various fields and by fragments of fingerprint (Allowing regexp, for instance a search for "?98.B30?" should return "EA0F AD90 985B 3025 576A 5061 454B 0FC0 BC07 B87E")
  10. Maintains the strong set, displays some statistics as to it in the manner of Penning's thing
  11. Allows the extraction of moduli in base64 (as Hanewinkel's tool) as well as the creation of encrypted messages via javascript for an arbitrary key the user selects.
  12. Provides daily back-ups of its entire key database. The backup is hashed and the hash introduced as a deed into deedbot each day.
———
  1. "PGP was originally deemed a weapon and declared a controlled export by the USG. This classification has changed, but PGP's substance has not. As its importance for a free world has grown exponentially in the past years, the efforts of the USG to quietly subvert it have increased feverishly.

    It is our considered opinion that one is ill advised to use unsupported implementations or unsupported versions of supported implementations, except in the case where that one has personally read the entire code involved and is confident in his ability to spot subtle subversion in critical cryptographic code.

    Friends don't let friends' heart bleed!" []

  2. There does not currently exist a correct implementation of time for this purpose. (If you wish to understand the problem, one path towards it would be - consider how would you go about making a system where material signed by an expired key remains valid past the key's expiration, but no further material may be signed after that date).

    There are some efforts currently underway to address this problem the only way it can be correctly addressed - through reference to the Bitcoin block number - but they will not be released as a patch for GnuPG - instead they will come as part of a complete replacement." []

Category: Job Board
Comments feed : RSS 2.0. Leave your own comment below, or send a trackback.

6 Responses

  1. should also e-mail the owner of key A whenever the submission of key B sets the phuctor off, not only key B

  2. Mircea Popescu`s avatar
    2
    Mircea Popescu 
    Tuesday, 21 April 2015

    Seemed obvious to me at the time, but there's no room for seems obvious in a spec. Fixed.

  3. I find your post really interesting. Implementing this kind of useful things sounds soemthing I would want to do, if I were more technically capable.

    That brings me to the question I'd like to ask you. What would be, in your opinion, the best way to learn to do useful and interesting things of this kind? Or any recommendations in general for someone who is quite tech savvy, but whose programming skills and experience don't go beyond writing some basic scripts.

  4. Mircea Popescu`s avatar
    4
    Mircea Popescu 
    Wednesday, 22 April 2015

    Go to b-a, read the logs for a year or so.

  1. [...] fifty terrabytes worth of broken keys on their drives. But we'll leave this discussion for when the #b-a keyserver actually comes online. [↩]No, really, this is going to work, somehow ? Somewhere [...]

  2. [...] fifty terrabytes worth of broken keys on their drives. But we'll leave this discussion for when the #b-a keyserver actually comes online. [↩]You will notice that most but not all the names in the first list [...]

Add your cents! »
    If this is your first comment, it will wait to be approved. This usually takes a few hours. Subsequent comments are not delayed.