From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.2 Received: from minnie.tuhs.org (minnie.tuhs.org [45.79.103.53]) by inbox.vuxu.org (OpenSMTPD) with ESMTP id 743984bd for ; Wed, 31 Jul 2019 17:29:26 +0000 (UTC) Received: by minnie.tuhs.org (Postfix, from userid 112) id 12CFA9BA1C; Thu, 1 Aug 2019 03:29:25 +1000 (AEST) Received: from minnie.tuhs.org (localhost [127.0.0.1]) by minnie.tuhs.org (Postfix) with ESMTP id 979D1949CB; Thu, 1 Aug 2019 03:29:09 +1000 (AEST) Authentication-Results: minnie.tuhs.org; dkim=pass (1024-bit key; unprotected) header.d=kilonet.net header.i=@kilonet.net header.b="XXNt0ySX"; dkim-atps=neutral Received: by minnie.tuhs.org (Postfix, from userid 112) id 0AE11949CB; Thu, 1 Aug 2019 03:29:08 +1000 (AEST) Received: from p3plsmtpa07-09.prod.phx3.secureserver.net (p3plsmtpa07-09.prod.phx3.secureserver.net [173.201.192.238]) by minnie.tuhs.org (Postfix) with ESMTPS id 5B3A2948EB for ; Thu, 1 Aug 2019 03:29:07 +1000 (AEST) Received: from medusa.kilonet.net ([72.69.11.12]) by :SMTPAUTH: with ESMTPA id ssPRhMguvxKQ1ssPShaXK9; Wed, 31 Jul 2019 10:29:06 -0700 Received: from [10.10.25.202] (dellray.kilonet.net [10.10.25.202]) by medusa.kilonet.net (8.14.8/8.15.1) with ESMTP id x6VHT4Gw016756 for ; Wed, 31 Jul 2019 13:29:04 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kilonet.net; s=default; t=1564594144; bh=2ksoxWkUV/6YbZeJRhgLl+JeFB5alHHe7oWJH+lgcWA=; h=Subject:To:References:From:Date:In-Reply-To; b=XXNt0ySX0tSfFZ6bijh9NeFsQNKwbfA40ui0qdiC5YbxuaDg5CM9uOCYrjGBhi1C2 veCkSFwc1id8uwOcaE7Zr1+7MsiD9ZXB0dYC1ptHr/YdG1n7kDBkRcpLsxwrTpD3N7 NCOPQcRYCyvq2q/nf4CAWAtP2eipy8JGVi+37RV8= To: tuhs@minnie.tuhs.org References: From: Arthur Krewat Message-ID: Date: Wed, 31 Jul 2019 13:29:16 -0400 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-CMAE-Envelope: MS4wfApwno+9aXM7KyhS4Il26fHXXi+j25VaXh+5obUMiAuKqw6GhHnVeV5qt5vekuDJU7YFDZOkxEW1xMxSgDKBTOvlwMw3O245CP+JAqsBKykR/Dd5j953 QDG0XeB48GJRCu+q38m36YI15ct8maMIfgU2WRme3i1DVLY58q8+tVhT Subject: Re: [TUHS] Who's behind the UNIX filesystem permission implementation X-BeenThere: tuhs@minnie.tuhs.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: The Unix Heritage Society mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: tuhs-bounces@minnie.tuhs.org Sender: "TUHS" On 7/31/2019 12:49 PM, Rodrigo G. López wrote: > Multics had modes per file (https://multicians.org/fjcc4.html) but i > don't know about the origins. the simpler approach of > owner/group/other is a purely Unix creation and i would bet Ken > Thompson is behind it all. TOPS-10 had a 3 octal digit file protection code: - - Logins are PPNs - [Project, Programmer] - So if I was [76,5], another user with [76,10] was in the same project. Much like UNIX groups. Owner Protection Codes 7*, 6* - You can execute, read, or change the protection code of the file. 5* - You have unlimited access to the file, except for renaming it. 4* - You have unlimited access to the file. 3 - You can execute, read, or change the protection code of the file. 2 - You have unlimited access to the file, except for renaming it. 1, 0 - You have unlimited access. * The File Daemon is called on a protection failure on this file (my memory is a little fuzzy on this, but I believe it allowed finer grained protections). Protection Codes for Fields 2 and 3 7 - The user cannot access the file. 6 - The user can only execute the file. 5 - The user can execute or read the file. 4 - The user can execute, read, or append to the file. 3 - The user can execute, read, append to, or update the file. 2 - The user can execute, read, append to, update, and write to the file. 1 - The user can execute, read, append to, update, write to, and rename the file. 0 - Unlimited access, including changing the protection code of the file. The name TOPS-10 was first used in 1970, but the monitor itself dates back to 1964. I'm not sure when these protection codes came into being, though.