Bug ID |
11070
|
Summary |
Error capturing/decrypting SSL/TLS traffic: "tshark: Error while capturing packets: SIOCGSTAMPNS: No such file or directory"
|
Product |
Wireshark
|
Version |
1.99.x (Experimental)
|
Hardware |
x86
|
OS |
Ubuntu
|
Status |
UNCONFIRMED
|
Severity |
Major
|
Priority |
Low
|
Component |
TShark
|
Assignee |
[email protected]
|
Reporter |
[email protected]
|
Build Information:
TShark (Wireshark) 1.99.4 (v1.99.4rc0-11-g9ca58d7 from master)
Copyright 1998-2015 Gerald Combs <[email protected]> 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 libpcap, without POSIX capabilities, without libnl, with
libz 1.2.3.4, with GLib 2.32.4, without SMI, with c-ares 1.7.5, without Lua,
with GnuTLS 2.12.14, with Gcrypt 1.5.0, without Kerberos, without GeoIP.
Running on Linux 3.11.0-26-generic, with locale en_US.UTF-8, with libpcap
version 1.8.0-PRE-GIT_2015_03_12, with libz 1.2.3.4, with GnuTLS 2.12.14, with
Gcrypt 1.5.0.
Intel(R) Core(TM) i5-3470 CPU @ 3.20GHz
Built using gcc 4.6.3.
--
Trying to capture traffic on an isolated network. Errors out when I supply a
server's private key. Using tshark 1.99.4, on Ubuntu 12.04
Command:
sudo tshark -o "ssl.desegment_ssl_records: TRUE" -o
"ssl.desegment_ssl_application_data: TRUE" -o
"ssl.keys_list:""10.1.175.50","443","http","/home/ianv/serverkey.pem" -o
"ssl.debug_file:"/home/ianv/ssl_debug"" -i eth4 -f "((src host 10.1.175.50 and
dst host 10.20.10.70) || (dst host 10.1.175.50 and src host 10.20.10.70)) &&
port 443"
Error report to stdout is:
Running as user "root" and group "root". This could be dangerous.
Capturing on 'eth4'
tshark: Error while capturing packets: SIOCGSTAMPNS: No such file or directory
Please report this to the Wireshark developers.
http://bugs.wireshark.org/
(This is not a crash; please do not report it as such.)
0 packets captured
Not sure if this is my problem or not. Output suggested filing a bug, so here
it is.
You are receiving this mail because:
- You are watching all bug changes.