RE: BobDHEncryptByCarl.cer

It is correct that these keys are not geneated according to RFC 2631.  I
have a question into our local experts if that is a problem or not.

Does the list feel that the keys need to be generate according to that spec,
or merely work?  This is after all a draft on the message format and not DH
key generation.

jim


-----Original Message-----
From: Hemma Prafullchandra [mailto:[email protected]]
Sent: Friday, October 08, 1999 3:56 PM
To: [email protected]
Subject: BobDHEncryptByCarl.cer



Has anyone verified the parameters in this cert ?

The DH publickey in this certificate is:
p: 
  EC 2C CD A4 EF 9A 26 2F 62 A7 BB 23 4D DF 2B 25 
  C1 68 D2 9E A9 45 5B 36 F1 94 89 1A AF 7D 11 24 
  9D 3D B9 3C 29 E8 D7 23 80 33 A6 9E 45 02 BB AA 
  CC 9E 28 05 95 A0 B3 17 76 C1 F7 25 35 61 02 41 
  92 27 0C 5E AE 48 E5 F3 6E 38 EF 91 D1 CF 37 FE 
  9A 40 97 C8 2D 35 9E 9D 93 C6 F8 15 AF 3F DA 74 
  3A B7 C4 93 B5 B9 BB 76 6C 1F A8 7E BC 3A AA 43 
  0A 81 64 FC 63 F0 7B 71 98 FA C0 38 79 10 1A 33 
g: 
  BA 0B D7 74 3D E7 34 E5 4C 13 A7 95 96 BB F1 E4 
  61 37 08 FB 12 C7 FB 9C 91 77 06 99 35 F0 48 24 
  96 33 12 01 7E 8D EC 0B F6 B2 C0 63 A7 15 C5 5E 
  95 86 A2 73 C5 49 46 37 79 60 FD 77 05 09 48 9B 
  70 8D 3C 05 F6 CE 44 2C 7F 7D 1B 2B 15 DD F3 05 
  2F BE 85 20 8F 8D F9 B4 A0 45 74 2B F4 3B 9D 42 
  62 34 27 27 81 8E 6F 0F 5E 62 85 89 CC ED 21 C3 
  91 70 06 54 EE 70 A8 92 55 5B 6E 19 22 4D 62 A7 
q: 
  C3 AB 4A 30 79 B3 D3 97 4E CA F5 A2 7D C7 70 A3 
  45 F3 B3 A2 86 05 D2 3E 49 F9 9F D9 0A B3 BE BD 
j: 
  01 34 FE C2 33 48 EB F6 3B 97 D9 E4 97 A7 60 A5 
  25 69 34 FB FD 46 2A D6 C9 C4 C5 F7 D6 F4 04 19 
  8D 94 D9 8A 37 68 69 67 55 FB F2 6B 0E 47 C5 5B 
  0B 4B 0E 1C 1A 8B 7B 75 B7 AA C3 AA D7 EB 3B DA 
  2A 8D 02 87 37 47 83 D7 31 B4 25 A8 AC BB 11 88 
  53 1C 11 92 B6 69 E7 2E 90 C1 7A FC 87 F4 F6 D7 
  1A 
seed: 
  B9 FF 1C 93 44 67 37 D1 B2 F8 57 9A 32 4A C9 4A 
  FF 3B EC 1E 
counter: 29
Y: 6fd4f6cd949a6eaf5b57179675bb0fb948e990370d1520c2551e13e2ae
   711784c30e74ae8a557f287d8bd728229c7646d73b4f9dd14d1bb2db51
   94c56d549640388a3881634a8cc31e098974a658d5c85a3dcfbbb8237f
   9c1f7d78fa9ef9909e91e74bc2a4be45067842583d9f632cef84d467e5
   fbc66da23629679046db4e48


According to the algorithm in rfc2631 for param generation,
m = length of q = 256 then the seed needs to be at least the
length of m or greater. In this case the seed is only 160 bits
-- is that allowed ?

Thanks, Hemma