netdev - How to file a bug against iproute2?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 16 Apr 2013 12:05:13 -0700
From:	Alex Stahl <testcore@...il.com>
To:	netdev@...r.kernel.org
Subject: How to file a bug against iproute2?

Hi Folks - Apologies in advance if this is the wrong forum for this...
I'd like to file a bug against iproute2 related to a permissions
issue, but can't find the bug tracker.

What I'm observing is that when I've added a user to the 'network'
group, that user is not actually granted permissions to manipulate
network interfaces, at least not through 'ip':

[6@11:56:05 testcore@...slim]:~>groups
network users vboxusers wireshark testcore rvm

[7@11:56:06 testcore@...slim]:~>ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
state UP mode DEFAULT qlen 1000
    link/ether 4c:72:b9:6e:1b:e8 brd ff:ff:ff:ff:ff:ff
3: wlp2s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode
DEFAULT qlen 1000
    link/ether 58:91:cf:54:4f:07 brd ff:ff:ff:ff:ff:ff

[8@11:56:15 testcore@...slim]:~>ip link set wlp2s0 up
RTNETLINK answers: Operation not permitted
code 2

I'm using arch linux w/ the latest kernel:

[9@11:56:23 testcore@...slim]:~>uname -a
Linux tc-slim 3.8.7-1-ARCH #1 SMP PREEMPT Sat Apr 13 09:01:47 CEST
2013 x86_64 GNU/Linux

According to the arch wiki, if I'm in the 'network' group I should be
able to manipulate interfaces:

https://wiki.archlinux.org/index.php/Groups#Group_list

If anyone has any suggestions on either how to fix this or where to
log it, that would be much appreciated.

Thanks,
Alex
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html