https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5906
Summary: todo/wish: better RSA key list management
Product: Wireshark
Version: 1.4.6
Platform: All
OS/Version: All
Status: NEW
Severity: Enhancement
Priority: Low
Component: Wireshark
AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
ReportedBy: franta@xxxxxxxxxxx
Created an attachment (id=6329)
--> (https://bugs.wireshark.org/bugzilla/attachment.cgi?id=6329)
actual 1.4.6 protocol properties window
Build Information:
TShark 1.4.6
Copyright 1998-2011 Gerald Combs <gerald@xxxxxxxxxxxxx> 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 (32-bit) with GLib 2.26.0, with libpcap 1.1.1, without libz, without
POSIX capabilities, without libpcre, with SMI 0.4.8, without c-ares, without
ADNS, with Lua 5.1, without Python, with GnuTLS 2.8.6, with Gcrypt 1.4.5, with
MIT Kerberos, with GeoIP.
Running on Linux 2.6.35.12-90.fc14.i686.PAE, with libpcap version 1.1.1.
Built using gcc 4.5.1 20100924 (Red Hat 4.5.1-4).
--
As rather modest wireshark user I'm quite satisfied with wireshark
possibilities.
But one thing IMO should be slightly better: RSA key list setting (Edit ->
Preferences... -> Protocols ->SSL). As now lot of protocols has its SSL/TLS
version, for their decode it is needed set lot of
IPAddr/port/protocol/decryption_key items. And for setting them is in dialog
only small rectangle box, insufficient for only one combination setting -
although area on right (protocol properties) side is big - see attachment. Thus
there should not be problem set bigger, well-arranged, multiline box for key
list set. And even better - permit store this list in external file (e.g. one
IPAddr/port/proto/key on line), in addition to present list. And for best -
something as when right-clicking to SSL packet list item, then offer some
method RSA key path selection (e.g. in case when proper key isn't found in
actual setting).
I know, there is possible have several profiles, e.g. for each captured host or
protocol one, but it isn't easy to take in, nor maintain it.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.