From owner-freebsd-sparc64@FreeBSD.ORG Tue Apr 8 14:26:48 2008 Return-Path: Delivered-To: freebsd-sparc64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AD40F1065674 for ; Tue, 8 Apr 2008 14:26:48 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 9A9078FC31 for ; Tue, 8 Apr 2008 14:26:48 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from zion.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by elvis.mu.org (Postfix) with ESMTP id 3EEF01A4D82; Tue, 8 Apr 2008 07:26:48 -0700 (PDT) From: John Baldwin To: "Aijaz Baig" Date: Tue, 8 Apr 2008 09:45:02 -0400 User-Agent: KMail/1.9.7 References: <101a1afc0804070654g7f4d09b6re3a8a6e928b0974b@mail.gmail.com> <200804071031.49628.jhb@freebsd.org> <101a1afc0804071413r5c780432tcbf5f0e70fb4118@mail.gmail.com> In-Reply-To: <101a1afc0804071413r5c780432tcbf5f0e70fb4118@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200804080945.02792.jhb@freebsd.org> Cc: freebsd-sparc64@freebsd.org Subject: Re: sudeors file not affecting user privileges X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Apr 2008 14:26:48 -0000 On Monday 07 April 2008 05:13:29 pm Aijaz Baig wrote: > Hello, > > Well..thanks for the advice. However even after using a sudo to issue the > command from the users account, I get the same error message as before > which reads: > > *sudo: /usr/local/etc/sudoers is mode 0644, should be 0440 > > *Well..what exactly is mode 0644 and how can I make sure that my users who > have been permitted to excute this command are in mode 0440? What exactly > are these modes and what do they mean? > > Will something like *chmod 0440 sudoers* work to solve this issue? I am a > bit wary of experimenting with this so Id rather ask before doing it? Yes, that will fix it. -- John Baldwin