Date: Tue, 1 Jun 1999 15:52:59 -0400 (EDT) From: Mikhail Teterin <mi@aldan.algebra.com> To: brian@FreeBSD.org Cc: mi@aldan.algebra.com, freebsd-bugs@FreeBSD.org Subject: Re: kern/11981: access to tunN devices not allowed to non-root despite permissions Message-ID: <199906011952.PAA46743@misha.cisco.com> In-Reply-To: <199906011939.MAA82607@freefall.freebsd.org> from "brian@FreeBSD.org" at "Jun 1, 1999 12:39:53 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
brian@FreeBSD.org once wrote: > Synopsis: access to tunN devices not allowed to non-root despite permissions > > State-Changed-From-To: open->closed > State-Changed-By: brian > State-Changed-When: Tue Jun 1 12:35:56 PDT 1999 > State-Changed-Why: > This is not a software bug. As I said in my mail, there's no point in > being able to read/write /dev/tun* because you haven't got permission > to configure the interface anyway. The fact that it's pointless (as far as you or me can see today), does not mean it should not be possible. Currently, according to your mail, the driver performs the useless check. IMHO, it should not. > As most interfaces have no associated device in /dev, there is no > facility in the kernel for anyone except root to add & remove routes > etc. > > It would be plausable to add that facility (IMHO), but the lack of > that facility doesn't constitute a bug. Agreed, that's why I put this into a separate paragraph in my PR, and said somthing like: "I would like"... > Translation: It's an enhancment - you'd need to discuss it on -hackers > and then probably implement it yourself if you want it to happen. -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199906011952.PAA46743>