Re: [PROPOSAL] (Ch.16 FHS) be more specific on file/dir permissions
I hope we can fix it that way:
o The system must grant to the application the permissions needed
to use all system interfaces (ABIs) mentioned in the LSB document
and included standards.
Lets test this with Alans examle:
Chapter 15.1 (User Database) does not mention the shadow password file.
There is the sentence:
The passwd(5) user database should only be read and
updated form the following APIs: ....
This explicitly makes passwd a "non interface". By not even mentioning it,
the shadow file is made a "non interface" too, implicitly.
On Thu, Jan 04, 2001 at 05:50:14PM +0000, Alan Cox wrote:
> > > > o The system must grant the permissions needed to use them
> > > > to all libraries, executables and data files mentioned in the
> > > > LSB document, and included standards.
> > > Stop a moment. Grant to whom ? Do I grant perl the ability to the shadow
> > > password file for example ;)
> > OK, let "reword" this paragraph.
> >
> > o The system must grant to the application the permissions needed
> > to use all libraries, executables and data files mentioned in the
> > LSB document and included standards.
> That still says I have to give it /etc/shadow ;) Perhaps we need to define
> public/private files ?
> --
>
> To UNSUBSCRIBE, email to lsb-spec-request@lists.linuxbase.org
> with subject of "unsubscribe". Trouble? Email listmaster@lists.linuxbase.org
--
______ ___
/ ___/__/ / Caldera (Deutschland) GmbH
/ /_/ _ / /__ Naegelsbachstr. 49c, 91052 Erlangen, Germany
/_____/_/ /____/ software developer / lsb project
==== /____/ ===== Dipl. Inf. Johannes Poehlmann, mail: jhp@caldera.de
Caldera OpenLinux phone: ++49 9131 7192 336, fax: ++49 9131 7192 399
Reply to: