Wireshark-bugs: [Wireshark-bugs] [Bug 10219] New: RSVP message with Integrity object may have al
| Bug ID |
10219
|
| Summary |
RSVP message with Integrity object may have all 0 checksum
|
| Classification |
Unclassified
|
| Product |
Wireshark
|
| Version |
1.99.x (Experimental)
|
| Hardware |
x86
|
| OS |
Mac OS X 10.8
|
| Status |
UNCONFIRMED
|
| Severity |
Normal
|
| Priority |
Low
|
| Component |
Dissection engine (libwireshark)
|
| Assignee |
bugzilla-admin@wireshark.org
|
| Reporter |
kszarkowicz@gmail.com
|
Created attachment 12840 [details]
RSVP message with INTEGRITY object and checksum 0
Build Information:
[kszarkowicz-mbp15:chapters/09/configs] kszarkowicz% wireshark -v
wireshark 1.99.0-526-gf5e2b42 (v1.99.0-rc1-526-gf5e2b42 from unknown)
Copyright 1998-2014 Gerald Combs <gerald@wireshark.org> 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 (64-bit) with Qt 5.2.1 with GLib 2.36.0, with libpcap, with libz
1.2.3,
without POSIX capabilities, with SMI 0.4.8, without c-ares, without ADNS, with
Lua 5.1, with GnuTLS 2.12.19, with Gcrypt 1.5.0, with MIT Kerberos, with GeoIP,
without PortAudio, with AirPcap.
Running on Mac OS X 10.8.5, build 12F45 (Darwin 12.5.0), with locale
en_US.UTF-8, with libpcap version 1.1.1, with libz 1.2.5, GnuTLS 2.12.19,
Gcrypt
1.5.0, without AirPcap.
Intel(R) Core(TM) i7-3615QM CPU @ 2.30GHz (with SSE4.2)
Built using llvm-gcc 4.2.1 (Based on Apple Inc. build 5658) (LLVM build
2336.9.00).
--
Dear experts,
according to RFC 2747, section 1:
The RSVP checksum MAY be disabled (set to zero) when the INTEGRITY
object is included in the message, as the message digest is a much
stronger integrity check.
and section 4.1:
(1) The RSVP checksum field is set to zero. If required, an RSVP
checksum can be calculated when the processing of the
INTEGRITY object is complete.
despite this, Wireshark considers such RSVP messages (that contain INTEGRITY
object) with checksum=0 as wrong.
Attached is one captured packet.
Best regards,
Krzysztof Szarkowicz
You are receiving this mail because:
- You are watching all bug changes.
