Bug ID: 14432
Summary: sshdump does not exit tcpdump
OS: Windows 10
Target Milestone: ---
Wireshark 2.4.4 (v2.4.4-0-g90a7be11a4)
Copyright 1998-2018 Gerald Combs <ger...@wireshark.org> and contributors.
License GPLv2+: GNU GPL version 2 or later
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.6.3, with WinPcap (4_1_3), with GLib 2.42.0, with
zlib 1.2.8, with SMI 0.4.8, with c-ares 1.12.0, with Lua 5.2.4, with GnuTLS
3.4.11, with Gcrypt 1.7.6, with MIT Kerberos, with GeoIP, with nghttp2 1.14.0,
with LZ4, with Snappy, with libxml2 2.9.4, with QtMultimedia, with AirPcap,
SBC, with SpanDSP.
Running on 64-bit Windows 10, build 17074, with Intel(R) Core(TM) i7-7700K CPU
4.20GHz (with SSE4.2), with 8143 MB of physical memory, with locale
English_Canada.1252, with WinPcap version 4.1.3 (packet.dll version
based on libpcap version 1.0 branch 1_0_rel0b (20091008), with GnuTLS 3.4.11,
with Gcrypt 1.7.6, without AirPcap.
Built using Microsoft Visual C++ 14.0 build 24215
after capturing packets for 5 minutes and pressing stop in wireshark the
capture stops but on the remote machine the tcpdump process is still running
which could eat up memory if a user forgets to exit it
You are receiving this mail because:
You are watching all bug changes.
Sent via: Wireshark-bugs mailing list <email@example.com>