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
Marc Haber 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, really reluctant to spe
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
On Tue, Jul 03, 2012 at 10:04:45AM -0700, Russ Allbery wrote:
> Marc Haber 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, c
Bill Allombert 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 situation, the known_hosts is c
On Tue, Jul 03, 2012 at 10:04:45AM -0700, Russ Allbery wrote:
> Marc Haber 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, c
Marc Haber 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.
Oh, right, for the client.
On Mon, Jul 02, 2012 at 02:29:53PM -0700, Russ Allbery wrote:
> Marc Haber 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
> >>
Marc Haber 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 what you're doing that
>> ma
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
Marc Haber 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 don't allow for those sorts o
On Sun, Jul 01, 2012 at 10:08:40AM -0700, Russ Allbery wrote:
> Marc Haber 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 files are intended to
Marc Haber 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 /etc/package(/home) and
> /
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 ab
14 matches
Mail list logo
