Bug#679751: please clarify package account and home directory location in policy

2012-07-04 Thread Stephen Gran
This one time, at band camp, Marc Haber said: The package itself caters only for presenter and collector on the same machine, which is done to give a working setup after installation. The package is not likely to be used in this configuration in any productive environment. ssh is one of the

Bug#679751: please clarify package account and home directory location in policy

2012-07-03 Thread Marc Haber
On Mon, Jul 02, 2012 at 02:29:53PM -0700, Russ Allbery wrote: Marc Haber mh+debian-packa...@zugschlus.de writes: On Mon, Jul 02, 2012 at 09:50:37AM -0700, Russ Allbery wrote: I'm not sure that I understand the use case. I've never needed to create an authorized_keys file for a system

Bug#679751: please clarify package account and home directory location in policy

2012-07-03 Thread Russ Allbery
Marc Haber mh+debian-packa...@zugschlus.de writes: On Mon, Jul 02, 2012 at 02:29:53PM -0700, Russ Allbery wrote: Ah, okay. For that use case, the only thing that you would care about the user home directory containing is the authorized_keys file, correct? known_hosts and the key itself.

Bug#679751: please clarify package account and home directory location in policy

2012-07-03 Thread Bill Allombert
On Tue, Jul 03, 2012 at 10:04:45AM -0700, Russ Allbery wrote: Marc Haber mh+debian-packa...@zugschlus.de writes: On Mon, Jul 02, 2012 at 02:29:53PM -0700, Russ Allbery wrote: Ah, okay. For that use case, the only thing that you would care about the user home directory containing is the

Bug#679751: please clarify package account and home directory location in policy

2012-07-03 Thread Russ Allbery
Bill Allombert bill.allomb...@math.u-bordeaux1.fr writes: On Tue, Jul 03, 2012 at 10:04:45AM -0700, Russ Allbery wrote: Oh, right, for the client. Yes, yes. Well, personally I would not consider either the client's key or the known_hosts file to be configuration files. In some common

Bug#679751: please clarify package account and home directory location in policy

2012-07-03 Thread Marc Haber
On Tue, Jul 03, 2012 at 10:04:45AM -0700, Russ Allbery wrote: Marc Haber mh+debian-packa...@zugschlus.de writes: On Mon, Jul 02, 2012 at 02:29:53PM -0700, Russ Allbery wrote: Ah, okay. For that use case, the only thing that you would care about the user home directory containing is the

Bug#679751: please clarify package account and home directory location in policy

2012-07-03 Thread Marc Haber
On Tue, Jul 03, 2012 at 10:52:26AM -0700, Russ Allbery wrote: I think it's perfectly acceptable to have an admin drop data into a /var/lib directory for non-default configurations of packages. Is this documented in policy? Greetings Marc, really reluctant to spend days to change a package in a

Bug#679751: please clarify package account and home directory location in policy

2012-07-03 Thread Russ Allbery
Marc Haber mh+debian-packa...@zugschlus.de writes: On Tue, Jul 03, 2012 at 10:52:26AM -0700, Russ Allbery wrote: I think it's perfectly acceptable to have an admin drop data into a /var/lib directory for non-default configurations of packages. Is this documented in policy? Greetings Marc,

Bug#679751: please clarify package account and home directory location in policy

2012-07-02 Thread Marc Haber
On Sun, Jul 01, 2012 at 10:08:40AM -0700, Russ Allbery wrote: Marc Haber mh+debian-packa...@zugschlus.de writes: In quite a few packages, the system user's home directory might accumulate dotfiles and/or ssh (keys|known_hosts) files, so this decision is not quite easy to take. If those

Bug#679751: please clarify package account and home directory location in policy

2012-07-02 Thread Russ Allbery
Marc Haber mh+debian-packa...@zugschlus.de writes: On Sun, Jul 01, 2012 at 10:08:40AM -0700, Russ Allbery wrote: If those files are intended to be persistant, then either /etc/package or /var/lib/package are pretty much your only options. The semantics of the other locations you mention

Bug#679751: please clarify package account and home directory location in policy

2012-07-02 Thread Marc Haber
On Mon, Jul 02, 2012 at 09:50:37AM -0700, Russ Allbery wrote: I'm not sure that I understand the use case. I've never needed to create an authorized_keys file for a system account created by a package. Maybe you could explain more about what you're doing that makes this a reasonable thing to

Bug#679751: please clarify package account and home directory location in policy

2012-07-02 Thread Russ Allbery
Marc Haber mh+debian-packa...@zugschlus.de writes: On Mon, Jul 02, 2012 at 09:50:37AM -0700, Russ Allbery wrote: I'm not sure that I understand the use case. I've never needed to create an authorized_keys file for a system account created by a package. Maybe you could explain more about

Bug#679751: please clarify package account and home directory location in policy

2012-07-01 Thread Marc Haber
Package: debian-policy Severity: normal Hi, many packages have to create system accounts on installation. Unfortunately, Debian policy is not quite clear on how to handle these. On the other hand, Debian QA is keen on addressing issues in account handling, which frequently leads to discussions

Bug#679751: please clarify package account and home directory location in policy

2012-07-01 Thread Russ Allbery
Marc Haber mh+debian-packa...@zugschlus.de writes: Unfortunately, Policy is not clear on where a system accounts' home directory is to be placed. Thus, a maintainer trying to fix the bug that a home directory was placed *gasp* in /home is risking to do it wrong again when choosing between