From owner-freebsd-bugs  Tue Jun  1 12:39:54 1999
Delivered-To: freebsd-bugs@freebsd.org
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
	by hub.freebsd.org (Postfix) with ESMTP
	id 96F3015788; Tue,  1 Jun 1999 12:39:53 -0700 (PDT)
	(envelope-from brian@FreeBSD.org)
Received: (from brian@localhost)
	by freefall.freebsd.org (8.9.3/8.9.2) id MAA82607;
	Tue, 1 Jun 1999 12:39:53 -0700 (PDT)
	(envelope-from brian@FreeBSD.org)
Date: Tue, 1 Jun 1999 12:39:53 -0700 (PDT)
From: <brian@FreeBSD.org>
Message-Id: <199906011939.MAA82607@freefall.freebsd.org>
To: mi@aldan.algebra.com, brian@FreeBSD.org, freebsd-bugs@FreeBSD.org
Subject: Re: kern/11981: access to tunN devices not allowed to non-root despite permissions
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

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.

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.

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.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message