From owner-freebsd-hackers Sun May 31 18:05:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA28330 for freebsd-hackers-outgoing; Sun, 31 May 1998 18:05:59 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mozart.canonware.com (canonware.com [206.184.206.112]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA28315 for ; Sun, 31 May 1998 18:05:39 -0700 (PDT) (envelope-from jasone@canonware.com) Received: from localhost (jasone@localhost) by mozart.canonware.com (8.8.8/8.8.7) with SMTP id SAA13935; Sun, 31 May 1998 18:03:45 -0700 (PDT) (envelope-from jasone@canonware.com) X-Authentication-Warning: mozart.canonware.com: jasone owned process doing -bs Date: Sun, 31 May 1998 18:03:45 -0700 (PDT) From: Jason Evans To: David Greenman cc: Terry Lambert , abial@nask.pl, freebsd-hackers@FreeBSD.ORG Subject: Re: Signed executables, safe delete etc. In-Reply-To: <199806010018.RAA09016@implode.root.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 31 May 1998, David Greenman wrote: > >> Second, there is no "SYSPRIV" privilege. There is a "SYSPRV" > >> privilege, however, that allows the holder access system resources as if > >> he had a system UIC. One does not have to have a system UIC to change > >> file permissions (including the executable flag); all one needs is to be > >> the owner of the file - just like it is in Unix. > As I mentioned above, the SYSPRIV privilege allows the process to access ^^^^^^^ > resources as if he had a system UIC. There are 4 sets of permissions bits > in VMS: user, system, group, and world. A system UIC is (usually) a UIC that > has a group number that is less than 9. If you have a system UIC or you > have SYSPRIV, then you can access files and directories using the "system" ^^^^^^^ > permissions bits, which usually default to RWED (all access). If your program > required SYSPRIV, then you apparantly had some sort of permissions problem - ^^^^^^^ > perhaps you created the file with the wrong permissions to start with (no > user/group/world access) and this caused the subsequant syscall to set the > file exectuable to fail. One Can Only Imagine. ? =) Jason (head spinning) Jason Evans Email: [jasone@canonware.com] Web: [http://www.canonware.com/~jasone] Home phone: [(650) 856-8204] Work phone: [(408) 774-8007] Quote: ["Invention is 1% inspiration and 99% perspiration" - Thomas Edison] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message