| Bug ID |
10267
|
| Summary |
Connection to RPCAP daemon for fetching interface capabilities is always attempted with null authentication
|
| Classification |
Unclassified
|
| Product |
Wireshark
|
| Version |
1.10.8
|
| Hardware |
x86
|
| OS |
Windows XP
|
| Status |
UNCONFIRMED
|
| Severity |
Minor
|
| Priority |
Low
|
| Component |
GTK+ UI
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Build Information:
Compiled (32-bit) with GTK+ 2.24.14, with Cairo 1.10.2, with Pango 1.30.1, with
GLib 2.34.1, with WinPcap (4_1_3), with libz 1.2.5, without POSIX capabilities,
without libnl, with SMI 0.4.8, with c-ares 1.9.1, with Lua 5.1, without Python,
with GnuTLS 2.12.18, with Gcrypt 1.4.6, with MIT Kerberos, with GeoIP, with
PortAudio V19-devel (built Jun 12 2014), with AirPcap.
Running on Windows XP Service Pack 3, build 2600, with WinPcap version 4.1.3
(packet.dll version 4.1.0.2980), based on libpcap version 1.0 branch 1_0_rel0b
(20091008), GnuTLS 2.12.18, Gcrypt 1.4.6, without AirPcap.
Intel(R) Xeon(R) CPU E31230 @ 3.20GHz, with 1023MB of physical
memory.
Built using Microsoft Visual C++ 10.0 build 40219
--
When I try to add remote interfaces via rpcap with authentication, I get pop
warning messages that the link type was not specified. As I understand this
causes the problem: The first rpcap connection uses the right authentication
information to get the interface list. But after that the following rpcap
connections (to get the interface capabilities) are attempted with null
authentication.
You are receiving this mail because:
- You are watching all bug changes.