Comment # 5
on bug 11853
from Guy Harris
(In reply to Michael Mann from comment #4)
> (In reply to Guy Harris from comment #3)
> > Is there some reason why undoing base-64 encoding is referred to as
> > "decryption" in that preference's description? It's not as if it's a real
> > form of *encryption* as in "you can't read this unless you have the key or
> > run some cracking software on it to decrypt it without a key".
> >
> > And is there some reason why there even *is* a preference? Is there some
> > reason why we don't *always* decode it, even if we also put the undecoded
> > blob into the protocol tree?
>
> While I agree its not decryption in the general sense, it's still an "extra
> step" that effects performance. In that sense it took on the general rule
> of decryption, which is a preference disabled by default.
Reassembly is an extra step that affects performance; does that mean that it
takes on the general rule of decryption, and should be disabled by default
*and* described in the preferences pane as a form of decryption?
I will, at minimum, fix the description for the preference not to call it
decryption, because it's *NOT* decryption - it's not something for which you
have to supply a key or have Wireshark attempt to crack decryption without a
key.
You are receiving this mail because:
- You are watching all bug changes.