Wireshark-bugs: [Wireshark-bugs] [Bug 13115] New: sshdump configuration dialog does not accept a
Date: Wed, 09 Nov 2016 20:19:29 +0000
Bug ID 13115
Summary sshdump configuration dialog does not accept any value for "Path to SSH private key"
Product Wireshark
Version 2.2.1
Hardware x86
OS other
Status UNCONFIRMED
Severity Minor
Priority Low
Component Qt UI
Assignee bugzilla-admin@wireshark.org
Reporter thurstylark@gmail.com

Build Information:
Wireshark 2.2.1

Copyright 1998-2016 Gerald Combs <gerald@wireshark.org> and contributors.
License GPLv2+: GNU GPL version 2 or later
<http://www.gnu.org/licenses/old-licenses/gpl-2.0.html>
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 Qt 5.7.0, with libpcap, with POSIX capabilities (Linux),
with libnl 3, with GLib 2.50.1, with zlib 1.2.8, without SMI, with c-ares
1.12.0, with Lua 5.2.4, with GnuTLS 3.4.16, with Gcrypt 1.7.3, with MIT
Kerberos, with GeoIP, with QtMultimedia, without AirPcap.

Running on Linux 4.8.6-1-ARCH, with locale en_US.UTF-8, with libpcap version
1.8.1, with GnuTLS 3.4.16, with Gcrypt 1.7.3, with zlib 1.2.8.
Intel(R) Core(TM) i5-6300HQ CPU @ 2.30GHz (with SSE4.2)

Built using gcc 6.2.1 20160830.

--
Any value in the "Path to SSH private key" box is rejected when attempting to
configure sshdump using a through the QT gui.

Steps to reproduce:
1. Start Wireshark to the default setup
2. Click on gear icon next to sshdump interface to open the Edit Interface
Settings dialog box
3. Use the Open File dialog box to select any file

Result:
The box containing the selected path remains red, the start button is not
selectable, and prevents starting the capture.

Expected Result:
The box containing the selected path has no background color, and provided the
rest of the necessary fields are filled, capture can be started.

Additional Info:
If used standalone, sshdump works as intended with --sshkey=/path/to/keyfile
set. 
This behavior does not occur in the GTK gui.


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