https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4002
--- Comment #8 from Stephen Fisher <steve@xxxxxxxxxxxxxxxxxx> 2009-09-15 08:35:12 PDT ---
(In reply to comment #7)
> Do you think it'd make sense to implement a decryption functionality? If so,
> how should Wireshark get the required password(s)? The original daemon uses a
> username/password file (similar to Apache's htpasswd files) for this.
>
> I'm having basically two ideas:
> - Specify that password map in the preferences pane and implement
> reading of that file in the dissector, too (it's easy enough, I think).
> - Implement a “Decrypt / Verify …” context menu (you know, when
> right-clicking
> on the encrypted / signed part). When clicked, a password box appears which
> the user can use to provide the necessary password.
Yes, decryption can be very helpful in debugging. The preference pane is
probably the best place to put this information keeping in line with other
protocols that Wireshark can decrypt (such as SSL). SSL points to external key
files, but it sounds like we wouldn't need to if a simple password is needed.
If you would like to discuss this further, it would probably be best to move
the discussion to the wireshark-dev@xxxxxxxxxxxxx mailing list.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
