Opened 15 years ago

Closed 15 years ago

#28 closed clarification (fixed)

Clarify that DH parameters are unsigned

Reported by: pasi.eronen@… Owned by:
Priority: minor Milestone: milestone1
Component: draft-ietf-tls-rfc4346-bis Version: 02
Severity: Keywords:
Cc:

Description

http://www1.ietf.org/mail-archive/web/tls/current/msg01101.html

On a related note, my large integer code prepends a leading
zero byte if the most significant bit is a one to prevent it
from appearing to be negative.  So when transferring the
Diffie-Hellman p, g, Ys, and Yc, they might have a leading
zero byte.  I haven't noticed any problems with this, but
wondered if this should be clarified to either always do it,
never do it, or leave it up to the implementer.

http://www1.ietf.org/mail-archive/web/tls/current/msg01105.html

Good catch! Perhaps we should add something like this to
Section 7.4.3?

   "The modulus (and other Diffie-Hellman parameters) are
   sent as unsigned integers (i.e., leading zero octets are
   not required even if the most significant bit is set)."

Change History (2)

comment:1 Changed 15 years ago by pasi.eronen@…

  • Milestone set to milestone1

comment:2 Changed 15 years ago by ekr@…

  • Resolution set to fixed
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.