On Mon, 14 May 2007 08:30:41 -0700 Daniel Burrows wrote: > On Sun, May 13, 2007 at 11:36:36PM +0200, Francesco Poli > <[EMAIL PROTECTED]> was heard to say: > > I've just found out where the problem lies. [...] > Glad to here what the problem was. I think, though, that I can do > what other programs apparently do and manually chmod the pkgstates > file after I create it. There's nothing very security-sensitive in > pkgstates (and you can cut off access to the /var/lib/aptitude > directory if you really want to hide it to normal users).
That would be *very* useful, I think, as I would be able to set a more restrictive umask for root, without losing any aptitude functionality intended for regular users. Indeed, if explicit permission setting is actually common practice for other programs, it would be a nice thing to have for aptitude too... -- http://frx.netsons.org/doc/nanodocs/testing_workstation_install.html Need to read a Debian testing installation walk-through? ..................................................... Francesco Poli . GnuPG key fpr == C979 F34B 27CE 5CD8 DC12 31B5 78F4 279B DD6D FCF4
pgp1kMLBMEPNe.pgp
Description: PGP signature
