ietf-openpgp
[Top] [All Lists]

Re: More draft comments

1997-12-05 01:18:15
* Tony Mione wrote:
[Signatures]
      Why is the keyID needed? It should be present in the actual
signature packet at the end of the message (in an Issuer ID subpacket
within the actual signature packet). Isn't this a waste of space? Also,

No. The additional package nac provide more bits of the fingerprint (aka key
ID) that the fixed size field. But this is truly optional.

what if you are setting up one pass signing for multiple keys? Do you need
multiple one pass signature packets if all of the other information is the
same (pk algorithm, sig type, hash alg, etc)?

No, only for the hashes.

[Secret key]
      Why are p and q saved? My understanding was that these are not
needed should be thrown away after the keypair is generated. If the secret
key exponent is saved in addition to the public exponent, then there is no
need for these pieces of data. Or am I totally missing something?

There are several shortcuts in modular arithmetics which requires p, q, and
some modular inverses.

      How about a new packet type for all certificates. Internally, it
can included a certificate type (PGP Classic = 1, OpenPGP = 2, X.509 = 3,
SPKI = 4, etc.) followed by certificate-specific contents (ASN.1 crud
for X.509, s-expression for SPKI, etc).

You like to introduce an other layer. But OpenPGP defines only the PGP layer
not a framework on top of such layers.

      In each case, exactly what material is the key signing? The
signature packet says which subpackets are included in the signed material,
however, what parts of the preceding packets are hashed and signed:

      - The entire public key packet followed by the entire user-id packet?
      - The MPIs from the pk packet + user-id data?
      - only the actual key material from the pk packet + the user-id data?

Quote from my proposal:
   13 - Key certification, positive ID. Heavy-duty identification efforts,
        photo ID, direct contact with personal friend, etc. Material
        signed is public key pkt and User ID pkt.
        MUST be supported.

      Ok, now I'm confused. How does this relate to the public key
packet? If this is not a packet, but rather a stored structure, then why is
it in a document on Message Formats?

Im confused, too. My major problem is, that the current draft status is
unavailable. I do not know what's edited and what's not.

<Prev in Thread] Current Thread [Next in Thread>