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

Date Prev · Date Next · Thread Prev · Thread Next
Date Index · Thread Index · Other Months · All Mailing Lists
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Sat, 30 Jan 2016 21:56:28 +0000

Comment # 4 on bug 12058 from 
(In reply to Pierre Fortin from comment #2)
> (In reply to Michael Mann from comment #1)
> 
> > Isn't that technically correct?  Since they aren't validated it's unknown
> > whether they are good or bad.  Are you expecting a third state of "not
> > validated"?
> 
> Why be verbose to this extent?:
>         true   false
>  good     -      X
>   bad     -      X
> when checksum = {good|bad} suffices?

That's a good question, given that showing both "good = {yes,no}" and "bad =
{no,yes}" is redundant.

Perhaps there should be a single, tri-state field with values "good", "bad",
and "unverified".

You are receiving this mail because:
  • You are watching all bug changes.