Wireshark-bugs: [Wireshark-bugs] [Bug 4768] New: Check for max value of range type preference is
Date: Sat, 15 May 2010 12:20:35 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4768

           Summary: Check for max value of range type preference is
                    incorrect
           Product: Wireshark
           Version: 1.2.7
          Platform: Other
        OS/Version: Windows XP
            Status: NEW
          Severity: Normal
          Priority: Low
         Component: Wireshark
        AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
        ReportedBy: carunach@xxxxxxxxx


Build Information:
Version 1.3.6Arun-h264

Copyright 1998-2010 Gerald Combs <gerald@xxxxxxxxxxxxx> and contributors.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Compiled with GTK+ 2.16.6, (32-bit) with GLib 2.22.4, with WinPcap (version
unknown), with libz 1.2.3, without POSIX capabilities, without libpcre, with
SMI
0.4.8, with c-ares 1.7.1, with Lua 5.1, without Python, with GnuTLS 2.8.5, with
Gcrypt 1.4.5, with MIT Kerberos, with GeoIP, with PortAudio V19-devel (built
May
11 2010), with AirPcap, with new_packet_list.

Running on Windows XP Service Pack 2, build 2600, with WinPcap version 4.1.1
(packet.dll version 4.1.0.1753), based on libpcap version 1.0 branch 1_0_rel0b
(20091008), GnuTLS 2.8.5, Gcrypt 1.4.5, without AirPcap.

Built using Microsoft Visual C++ 8.0 build 50727

Wireshark is Open Source Software released under the GNU General Public
License.
--
When we define preference value of type "range" with a maximum value of say N, 
wireshark does not provide any error when user enters a value N+1.

Example : "TCP ports" parameter for HTTP dissector will take values greater 
than max value of 65535.

This patch fixes this problem by comparing the user entered value with 
max_value rather than G_MAXUINT32.

-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.