Wireshark · Wireshark-bugs: [Wireshark-bugs] [Bug 12058] If checksums aren't validated, both the "checksum good" and "checksum b

Wireshark-bugs: [Wireshark-bugs] [Bug 12058] If checksums aren't validated, both the "checksum g

Date: Sat, 30 Jan 2016 22:04:32 +0000

Michael Mann changed bug 12058

What	Removed	Added
See Also		https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=8859

Comment # 5 on bug 12058 from Michael Mann

(In reply to Guy Harris from comment #4)
> Perhaps there should be a single, tri-state field with values "good", "bad",
> and "unverified".

Consistency would be good, see bug 8859.

You are receiving this mail because:

You are watching all bug changes.

References:
- [Wireshark-bugs] [Bug 12058] New: Checksums {good,bad} = False
  - From: bugzilla-daemon

Prev by Date: [Wireshark-bugs] [Bug 12058] If checksums aren't validated, both the "checksum good" and "checksum bad" flag are set to false
Next by Date: [Wireshark-bugs] [Bug 8859] Apply consistent naming convention to checksum display filter fields and expert info.
Previous by thread: [Wireshark-bugs] [Bug 12058] If checksums aren't validated, both the "checksum good" and "checksum bad" flag are set to false
Next by thread: [Wireshark-bugs] [Bug 12058] If checksums aren't validated, both the "checksum good" and "checksum bad" flag are set to false
Index(es):
- Date
- Thread