guessnet requires root privileges when it shouldn't

Bug #175425 reported by Andrew on 2007-12-11
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
guessnet (Ubuntu)
Undecided
Unassigned
libnet (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: guessnet

Guessnet 0.42-1 requires root privileges. According to the debian bugs, this was supposed to be fixed in debian version 0.26-1:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=224910

Running as non-root user fails with this message:

$> cat /dev/null | guessnet -i eth0
libnet_init(): UID or EUID of 0 required
. Context: opening link interface
You can try invoking guessnet as user root instead of currentuser

Andrew (andrew-rw-robinson) wrote :

Note: found in Xubuntu Gutsy

Also the debian bug mentions the limitation of libnet1, so I added that package to this bug as well

Changed in libnet:
assignee: nobody → schwitzd
Changed in libnet:
assignee: schwitzd → nobody
Changed in guessnet:
assignee: nobody → schwitzd
Changed in guessnet:
assignee: schwitzd → nobody
Daniel T Chen (crimsun) wrote :

Is this symptom still reproducible in 8.10?

Changed in libnet:
status: New → Incomplete
Andrew (andrew-rw-robinson) wrote :

Yup, still broken

Andrew (andrew-rw-robinson) wrote :

Error is slightly different now:
cat /dev/null | guessnet -i eth0
socket: Operation not permitted. Context: initializing pcap packet capture library
You can try invoking guessnet as user root instead of anrobins

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in guessnet (Ubuntu):
status: New → Confirmed
Stefanos Harhalakis (v13) wrote :

Not sure if this going to be fixed in libnet, but you can always use fakeroot.

I.e: cat /dev/null | fakeroot guessnet -i eth0

WebDawg (webdawg) wrote :

I just add the user to netdev and libnet works.

WebDawg (webdawg) wrote :

I lied. I cannot understand what happened. Was working fine and had to to a restart of the proc that calls it and it does not work again.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers