https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5228
campbco@xxxxxxxxx changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |WORKSFORME
--- Comment #5 from campbco@xxxxxxxxx 2010-09-17 06:08:31 PDT ---
(In reply to comment #4)
> When you say "I have the same issue as root", are you referring to the issue
> mentioned in the title of the bug, or the inability to capture? The two are
> 100% completely unrelated.
> TShark (and Wireshark) do not directly capture traffic; they run dumpcap to
> capture the traffic. dumpcap is, if it's not set-UID, run with the same
> effective user ID as the one TShark or Wireshark are running with when they
> start dumpcap - and TShark, at least, surrenders any set-UID and set-GID
> privileges it has before starting dumpcap.
> If you're running it as root because you've used "su", for example, tshark
> shouldn't think it's running with elevated privileges, in the sense of its
> effective user ID being different from its real user ID, so it shouldn't
> relinquish any privileges.
> What is printed if, at the
> @@@:root root>
> prompt, you run the "id" command?
The id command shows me as root. On another note I re-installed wireshark. For
some reason it is partially working. I mean partially in tshark is working
fine, but wireshark is flaking. That's fine with me at this point I am able to
capture data and use another machine to interpet the data. I appreciate your
help.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.