[Bug 2264] New: RekeyLimit option does not allow '4G' value when UINT_MAX is 0xffffffff

[bugzilla-daemon at mindrot.org]

https://bugzilla.mindrot.org/show_bug.cgi?id=2264

            Bug ID: 2264
           Summary: RekeyLimit option does not allow '4G' value when
                    UINT_MAX is 0xffffffff
           Product: Portable OpenSSH
           Version: 6.6p1
          Hardware: Other
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: sshd
          Assignee: unassigned-bugs at mindrot.org
          Reporter: glee at ciena.com

When value '4G' is used to specify the RekeyLimit value, the
configuration file parsing function, scan_scaled(), converts the 4G
into value 4294967296 (in readconf.c and in servconf.c alike).

On systems where UINT_MAX is 0xffffffff, we are not able to configure
value '4G' due to the 4294967296 being greater than 4294967295.  This
appears to be a bug since one would expect a value of 4G to be able to
be specified on a 32-bit OS.  The way in which the function
set_newkeys() sets the value of max_blocks, it seems like openssh
should be able to allow value 4G and perform the math to determine
number of blocks before rekey takes place.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.