Wireshark-bugs: [Wireshark-bugs] [Bug 10735] New: wireshark fails to start when run with setuid/
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Wed, 26 Nov 2014 22:15:34 +0000
Bug ID 10735
Summary wireshark fails to start when run with setuid/setgid flag
Product Wireshark
Version 1.12.2
Hardware Other
OS FreeBSD
Status UNCONFIRMED
Severity Major
Priority Low
Component Qt UI
Assignee bugzilla-admin@wireshark.org
Reporter yuri@rawbw.com 

Build Information:
FreeBSD port
--
Since wireshark requires higher than regular user privileges (at least on BSD),
it is natural to be running it with setuid/setgid.

However, when any of these flags is set, wireshark fails after the splash
screen:

Error creating proxy: Timeout was reached (g-io-error-quark, 24)
Error creating proxy: Timeout was reached (g-io-error-quark, 24)

This fails with both u+s and g+s, including when wireshark is in 'network'
group.

Actually, (at least on BSD) wireshark should be run as g+s and with 'network'
group so that users can just launch it and it will find interfaces.

Currently I have to run is 'sudo wireshark'

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