Re: compile-time configuration, etc.

Dear Paul,

in my opinion the tar ball of a package should only contain data in
<.../package> and <.../src>. This gives an installer, e.g. sp-install,
the possibility to ENSURE that extracting the package does not overwrite
important data.

E.g.: Suppose Eve creates package 'trojan' such that it contains
   /etc/inetd.conf and /etc/passwd. After unpacking it in / she may enter
   the local system from remote computers. If unpacking is confined to
   <.../package> and <.../src> this is not possible.

   Also Fool's package may overwrite <.../conf/individual-edited>, etc.

Of course, if the program code contains a trojan part, security is
endangered, too. If you compile as a special user for each package
(or each package version) this danger would be confined, too.

Alternativly, you can unpack und compile as a special user. But this
does not help with Fool's package.

Paul Jarc (Mon, Nov 03, 2003 at 11:49:25AM -0500):
> Stefan Karrmann <[email protected]> wrote:
> > If package foo should not change data in compile-conf then even the
> > defaults in ./conf-compile must NOT belong to the tar-ball. The defaults
> > may reside in ./package/defaults.
> 
> On second thought, I think this is a good idea, except that I would
> put the defaults in conf-compile/defaults/.  I think it will be easier
> on the user to have the defaults as close as possible to where they
> make their changes.  I'm working on changes for sp-install to handle
> this.  Any other ideas about where the defaults should be, before I
> release the new version?
> 
> 
> paul

Regards,
-- 
Stefan Karrmann