From owner-freebsd-questions Thu Jan 19 22:23:25 1995 Return-Path: questions-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id WAA03723 for questions-outgoing; Thu, 19 Jan 1995 22:23:25 -0800 Received: from hp.com (hp.com [15.255.152.4]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id WAA03717 for ; Thu, 19 Jan 1995 22:23:24 -0800 Received: from hpautow.aus.hp.com by hp.com with SMTP (1.37.109.14/15.5+ECS 3.3) id AA242912999; Thu, 19 Jan 1995 22:23:19 -0800 Message-Id: <199501200623.AA242912999@hp.com> Received: by hpautow.aus.hp.com (1.38.193.4/16.2) id AA13808; Fri, 20 Jan 1995 17:22:25 +1100 From: "M.C Wong" Subject: copy disabled filesystem To: freebsd-questions@freefall.cdrom.com (freebsd-questions@freefall.cdrom.com) Date: Fri, 20 Jan 1995 17:22:25 EDT X-Mailer: Elm [revision: 109.14.c] Sender: questions-owner@FreeBSD.org Precedence: bulk OK, I am no great Novell fan nor user, but really like the idea of being able to read a file but not allowing copy permission. How difficult can this kind of feature be implemented on Unix ? I meant, you may need to allower user to be able to read/open some libraries but not giving them the right to copy/steal a copy of it, and you probably don't want to write wrapper around whatever compiler, loader you have to change uid to open some particular files for read (ie to disable user from read but still need to have them use it, strange idea ? Not!). I guess the tricky part of this feature is that one can easily cat the file to a different name and hence bypass the copy-disabled feature to achieve the act. But there got to be a better way of achieving this sort of goals? -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ M.C Wong Email: mcw@hpato.aus.hp.com Australian Telecom Operation Voice: +61 3 272 8058 Hewlett-Packard Australia Ltd Fax: +61 3 898 9257 31 Joseph St, Blackburn 3130, Australia OS: FreeBSD-1.1.5.1 http://hpautow.aus.hp.com:9999/~mcw/mcw.html (or http://hpautorf/~mcw)