| 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
| ||
|
Message-ID: <4746469c0708172256g164049f0qeaf02462aebd6d27@mail.gmail.com> Date: Fri, 17 Aug 2007 22:56:04 -0700 From: "Mike Mohr" <akihana@...il.com> To: linux-kernel@...r.kernel.org Subject: group ownership of tun devices -- nonfunctional? Per the post here: http://lkml.org/lkml/2007/6/18/228 it appears that the group ownership patch has made it into .23. I am using these patches, amongst which the kernel component appears to be identical: http://sigxcpu.org/unsorted-patches/0001-allow-tun-ownership-by-group.patch http://sigxcpu.org/unsorted-patches/tunctl_gid.diff I can create devices that are owned by my user account (tunctl -u `whoami` -t tap0) and it works fine. However, if I use group permissions with -g it stops working. In all cases, if I pass -g <group>, the interface is created correctly but it is unusable as a non-root user. So my question is: am I doing something wrong? If I am, I don't see it. Assuming then that I am not doing anything wrong on my end, I assume then that there is something missing from the kernel patch I applied. I read over it and I can't see any issues, especially considering that tunctl comes back without error (even with -g) and creates an interface. Just wondering if this was an issue that should be looked into-- Mike - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists