xref: /minix3/crypto/external/bsd/netpgp/dist/ref/draft-ietf-openpgp-rfc2440bis-12-comments.txt (revision ebfedea0ce5bbe81e252ddf32d732e40fb633fae)
1*ebfedea0SLionel Sambuc3.2 (MPI) doesn't specify what the unused bits should be set
2*ebfedea0SLionel Sambuc  to. This may be deliberate but I think it should either say they MUST
3*ebfedea0SLionel Sambuc  be zero (which I prefer) or that their content is unspecified.
4*ebfedea0SLionel Sambuc
5*ebfedea0SLionel Sambuc4.2 refers to Content Tags, but 4.3 calls them Packet Tags.
6*ebfedea0SLionel Sambuc
7*ebfedea0SLionel Sambuc5.5.2 doesn't mention V2 keys.
8*ebfedea0SLionel Sambuc
9*ebfedea0SLionel SambucIn section 9.1, Schneier is given as the reference for DSA - why not refer to FIPS 186-2, which is freely available? Or, indeed, HAC 11.5.1, available here: http://www.cacr.math.uwaterloo.ca/hac/about/chap11.pdf.
10*ebfedea0SLionel Sambuc
11*ebfedea0SLionel SambucSimilarly 9.2, TripleDES (which, presumably is EDE 3DES - it'd be good
12*ebfedea0SLionel Sambucto be specific) is on some FIPS document which I forget or in HAC
13*ebfedea0SLionel Sambucchapter 7 (7.32 in 7.2.3 and 7.4.2).
14*ebfedea0SLionel Sambuc
15*ebfedea0SLionel Sambuc----
16*ebfedea0SLionel Sambuc
17*ebfedea0SLionel SambucIn 5.2.1:
18*ebfedea0SLionel Sambuc
19*ebfedea0SLionel Sambuc"0x10: Generic certification of a User ID and Public Key packet."
20*ebfedea0SLionel Sambuc
21*ebfedea0SLionel SambucDoes this mean that the signature is over the User ID packet and the Public Key packet, concatenated, in that order? Or what?
22*ebfedea0SLionel Sambuc
23*ebfedea0SLionel SambucAlso, what on earth does:
24*ebfedea0SLionel Sambuc
25*ebfedea0SLionel Sambuc       Note that all PGP "key signatures" are this type of
26*ebfedea0SLionel Sambuc       certification.
27*ebfedea0SLionel Sambuc
28*ebfedea0SLionel Sambucmean?
29*ebfedea0SLionel Sambuc
30*ebfedea0SLionel SambucIn 5.2.2:
31*ebfedea0SLionel Sambuc
32*ebfedea0SLionel Sambuc   "The data being signed is hashed, and then the signature type and
33*ebfedea0SLionel Sambuc   creation time from the signature packet are hashed (5 additional
34*ebfedea0SLionel Sambuc   octets)."
35*ebfedea0SLionel Sambuc
36*ebfedea0SLionel Sambucis unclear, suggest:
37*ebfedea0SLionel Sambuc
38*ebfedea0SLionel Sambuc"The concatenation of the data to be signed, the signature type and
39*ebfedea0SLionel Sambuccreation time from the signature packet (5 additional octets) is hashed."
40*ebfedea0SLionel Sambuc
41*ebfedea0SLionel SambucIn 5.9:
42*ebfedea0SLionel Sambuc
43*ebfedea0SLionel Sambuc   " - File name as a string (one-octet length, followed by file name),
44*ebfedea0SLionel Sambuc       if the encrypted data should be saved as a file."
45*ebfedea0SLionel Sambuc
46*ebfedea0SLionel Sambucbut no mention of what if it shouldn't be saved as a file. 0 length,
47*ebfedea0SLionel Sambucperhaps?
48*ebfedea0SLionel Sambuc
49*ebfedea0SLionel SambucThen:
50*ebfedea0SLionel Sambuc
51*ebfedea0SLionel Sambuc   " - A four-octet number that indicates the modification date of the
52*ebfedea0SLionel Sambuc       file, or the creation time of the packet, or a zero that
53*ebfedea0SLionel Sambuc       indicates the present time."
54*ebfedea0SLionel Sambuc
55*ebfedea0SLionel SambucI would _guess_ that it means modification date of the file if there's
56*ebfedea0SLionel Sambuca filename, the creation time if there isn't. I have no idea what zero
57*ebfedea0SLionel Sambucis supposed to mean. Nothing, would be the obvious interpretation -
58*ebfedea0SLionel Sambuc"the present time" is nonsensical.
59*ebfedea0SLionel Sambuc
60*ebfedea0SLionel SambucOnce more, when I know what its supposed to mean, I'll suggest
61*ebfedea0SLionel Sambucwording.
62*ebfedea0SLionel Sambuc
63*ebfedea0SLionel Sambuc------
64*ebfedea0SLionel Sambuc
65*ebfedea0SLionel Sambuc5.2.3.5 Issuer
66*ebfedea0SLionel Sambuc
67*ebfedea0SLionel Sambucshould be:
68*ebfedea0SLionel Sambuc
69*ebfedea0SLionel Sambuc5.2.3.5 Issuer key ID
70*ebfedea0SLionel Sambuc
71*ebfedea0SLionel SambucA tiny point, I know, but it made it hard to find.
72*ebfedea0SLionel Sambuc
73*ebfedea0SLionel SambucKey algorithms ... these are used in various contexts, and there's a
74*ebfedea0SLionel Sambuclist in 9.1 - some of these are clearly unsuitable in some contexts -
75*ebfedea0SLionel Sambucfor example, one would not expect to see RSA Ecnrpyt-Only (3) in a
76*ebfedea0SLionel Sambucsignature. But I can't find any language saying anything about
77*ebfedea0SLionel Sambucthis. Are there any rules?
78*ebfedea0SLionel Sambuc
79