From owner-freebsd-questions@FreeBSD.ORG Fri Apr 1 18:51:12 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 84CA516A4CE for ; Fri, 1 Apr 2005 18:51:12 +0000 (GMT) Received: from smtp.knology.net (smtp.knology.net [24.214.63.101]) by mx1.FreeBSD.org (Postfix) with SMTP id F017043D2D for ; Fri, 1 Apr 2005 18:51:11 +0000 (GMT) (envelope-from dkelly@Grumpy.DynDNS.org) Received: (qmail 25252 invoked by uid 0); 1 Apr 2005 18:51:10 -0000 Received: from user-69-73-60-132.knology.net (HELO Grumpy.DynDNS.org) (69.73.60.132) by smtp2.knology.net with SMTP; 1 Apr 2005 18:51:10 -0000 Received: by Grumpy.DynDNS.org (Postfix, from userid 928) id 866A066B2; Fri, 1 Apr 2005 12:51:10 -0600 (CST) Date: Fri, 1 Apr 2005 12:51:10 -0600 From: David Kelly To: Martin McCormick Message-ID: <20050401185110.GA7808@Grumpy.DynDNS.org> References: <200504011717.j31HHE9S080897@dc.cis.okstate.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200504011717.j31HHE9S080897@dc.cis.okstate.edu> User-Agent: Mutt/1.4.2.1i cc: freebsd-questions@freebsd.org Subject: Re: Best Practice for Allowing non-root Users Access to Serial Port? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Apr 2005 18:51:12 -0000 On Fri, Apr 01, 2005 at 11:17:14AM -0600, Martin McCormick wrote: > What is the safest way to let non-root users access > /dev/ttyd0? I notice that in FreeBSD, /dev/ttydx is owned by > root:wheel. In linux, the ttySx's are in a special group so the trick > there is to add users to that group and make sure the ttyS's are group > writable. > > Here, I want the users to be able to use C-kermit to talk to a > remote device without them having to be root. Add the users to group "dialer" as this is what Kermit needs to create uucp locks. Then as others have already stated use /dev/cuaa0, the "call out" device, rather than ttyd0. -- David Kelly N4HHE, dkelly@HiWAAY.net ======================================================================== Whom computers would destroy, they must first drive mad.