Bug ID |
9045
|
Summary |
openSAFETY: Fixing heuristic detection
|
Classification |
Unclassified
|
Product |
Wireshark
|
Version |
SVN
|
Hardware |
All
|
OS |
All
|
Status |
UNCONFIRMED
|
Severity |
Enhancement
|
Priority |
Low
|
Component |
Dissection engine (libwireshark)
|
Assignee |
[email protected]
|
Reporter |
[email protected]
|
Created attachment 11390 [details]
openSAFETY: Fixing heuristic detection
Build Information:
TShark 1.11.0 (SVN Rev 51390 from master)
Copyright 1998-2013 Gerald Combs <[email protected]> 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 GLib 2.36.0, with libpcap, with libz 1.2.7, with POSIX
capabilities (Linux), without libnl, with SMI 0.4.8, with c-ares 1.9.1, with
Lua
5.1, without Python, with GnuTLS 2.12.23, with Gcrypt 1.5.0, with MIT Kerberos,
with GeoIP.
Running on Linux 3.8.0-26-generic, with locale de_DE.UTF-8, with libpcap
version
1.3.0, with libz 1.2.7.
Intel(R) Core(TM)2 Quad CPU Q8400 @ 2.66GHz
Built using gcc 4.7.3.
--
Various fixes for dissection bugs:
- Expert info for CRC 0x5935 got wrongly attached to Slim SSDO packages
- SPDO Data Requests that fit in the last bytes of a frame got missed
- Slim SSDOs got detected, that actually are not Slim SSDOs, to prevent this
in the future, two checks have been added
- The reported length of a Slim SSDO must be larger than 0 (correct
Slim SSDOs allways have at least 1 byte)
- Both crc's must differ from another. There is a very unlikely
possibility, that they may collide, but in such a case openSAFETY
in itself would be flauted by design.
The change was fuzz-tested and randpkt tested, and the checks from src/tools
where run.
You are receiving this mail because:
- You are watching all bug changes.