Wireshark-bugs: [Wireshark-bugs] [Bug 8186] New: Invalid path in .wireshark/ssl_keys throws a wa
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Wed, 09 Jan 2013 16:13:13 +0000
Bug ID 8186
Summary Invalid path in .wireshark/ssl_keys throws a warning then empties out the corresponding configuration dialog preventing removal
Classification Unclassified
Product Wireshark
Version 1.6.7
Hardware x86-64
OS Ubuntu
Status UNCONFIRMED
Severity Minor
Priority Low
Component Wireshark
Assignee bugzilla-admin@wireshark.org
Reporter mark@g.foster.cc 

Created attachment 9795 [details]
Warning dialog for invalid RSA key

Build Information:
Version 1.6.7

Copyright 1998-2012 Gerald Combs <gerald@wireshark.org> 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 (64-bit) with GTK+ 2.24.10, with GLib 2.32.0, with libpcap (version
unknown), with libz 1.2.3.4, with POSIX capabilities (Linux), without libpcre,
with SMI 0.4.8, with c-ares 1.7.5, with Lua 5.1, without Python, with GnuTLS
2.12.14, with Gcrypt 1.5.0, with MIT Kerberos, with GeoIP, with PortAudio
V19-devel (built Dec 10 2011 11:43:10), without AirPcap.

Running on Linux 3.2.0-35-generic, with libpcap version 1.1.1, with libz
1.2.3.4, GnuTLS 2.12.14, Gcrypt 1.5.0.

--
Repro.
1. Run wireshark and configure a valid key under
Edit->Preferences->Protocols->SSL->RSA Keys List->Edit
2. Quitt wireshark
3. Remove the key file from the filesystem, or rename the file
4. Run wireshark
5. Observe the warning
Error loading table 'SSL Decrypt': ssl_keys:2: File '/path/to/ssl.key' does not
exist or access is denied.
6. Attempt to edit the RSA Keys List, it will be *empty*.

Workarounds: 
1. edit the ~/.wireshark/ssl_keys file by hand to remove the offending key, or
2. rename the file to ssl_keys.old

I suggest proper behavoir would be to have the key be listed in the
configuration screen so the path can be fixed within the application, or the
key can be removed from there. Or, offer to go straight to the RSA Keys List
edit screen from the warning dialog.

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