Bug#684732: unblock: nut/2.6.4-2

[Arnaud Quette <aquette.dev@gmail.com>]

Hi everybody,

sorry for the lag in answering... too many real life issues to deal with.

2012/11/26 Julien Cristau <jcristau@debian.org>

On Sun, Nov 11, 2012 at 22:42:09 +0100, Laurent Bigonville wrote:

> Le Sun, 11 Nov 2012 19:06:52 +0100,
> Julien Cristau <jcristau@debian.org> a écrit :
>
> > One more question...
> >
> > On Mon, Aug 13, 2012 at 15:36:14 +0200, Laurent Bigonville wrote:
> >
> > > +    for file in nut.conf upsmon.conf upssched.conf ; do
> > > +        if [ -f /etc/nut/$file ] ; then
> > > +            chown root:nut /etc/nut/$file
> > > +            chmod 640 /etc/nut/$file
> > > +        fi
> > > +    done
> >
> > why is this is done unconditionally on postinst configure, instead of
> > just on first install?
>
> These files could contains passwords, I guess that this is done to be
> really sure the files are not world readable? Arnaud?
>

Doing that when the file is created is fine.  But not every time
postinst runs, IMO.

this is indeed to enforce that files have still the proper permissions for the nut user, as mentioned by Laurent, since we still lack a configuration tool to assist this.  Having anything else than the above may results in NUT not being able to start or some security hole.

I don't see any specific issue with this one.

cheers,
Arnaud
-- 
NUT (Network UPS Tools) Project Leader - http://www.networkupstools.org
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.fr