Debian Bug report logs - #15295
cron: give perms,user,group to savelog

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: David ROCHER <rocher@easynet.fr>

To: submit@bugs.debian.org

Subject: cron: give perms,user,group to savelog

Date: Wed, 26 Nov 1997 01:43:52 +0100

package: cron
version: 3.0pl1-40
severity: wishlist

savelog could have perms,user,group into standard.daily like this:
  savelog -g adm -m 640 -u root -c 7 setuid.changes
-- 
   David Rocher, rocher@mail.dotcom.fr
   Debian GNU/Linux - http://www.debian.org/

Message #10 received at 15295@bugs.debian.org (full text, mbox, reply):

From: Steve Greenland <steveg@rpcweb.dmccorp.com>

To: rocher@mail.dotcom.fr, 15295@bugs.debian.org

Subject: Re: Bug#15295: cron: give perms,user,group to savelog

Date: Fri, 28 Nov 1997 13:21:06 -0600

On 26-Nov-1997 01:43:52, David ROCHER <rocher@easynet.fr> wrote:
> package: cron
> version: 3.0pl1-40
> severity: wishlist
> 
> savelog could have perms,user,group into standard.daily like this:
>   savelog -g adm -m 640 -u root -c 7 setuid.changes

Yes, it could. Why? How is that different from the current result?
Experimentation on my system shows that setuid.changes{.*} all end up
640, u=root, g=adm.

Steve Greenland

-- 
Steve Greenland

Message #15 received at 15295@bugs.debian.org (full text, mbox, reply):

From: David Rocher <davroc@hplb.hpl.hp.com>

To: stevegr@master.debian.org, 15295@bugs.debian.org

Subject: Re: Bug#15295: cron: give perms,user,group to savelog

Date: Tue, 21 Apr 1998 18:49:39 +0000

On Fri, Nov 28, 1997 at 01:21:06PM -0600, Steve Greenland wrote:
> > savelog could have perms,user,group into standard.daily like this:
> >   savelog -g adm -m 640 -u root -c 7 setuid.changes
> 
> Yes, it could. Why? How is that different from the current result?
> Experimentation on my system shows that setuid.changes{.*} all end up
> 640, u=root, g=adm.

I just installed a fresh hamm with 3.0pl1-44 and I have:
-rw-r-----   1 root     root         3414 Apr 21 06:42 setuid.changes
-rw-r-----   1 root     root            0 Apr 21 06:42 setuid.changes.0
-rw-r-----   1 root     root           37 Apr 20 06:42 setuid.changes.1.gz
-rw-r-----   1 root     root         5881 Apr 19 06:42 setuid.changes.2.gz
-rw-r-----   1 root     root           37 Apr 18 06:42 setuid.changes.3.gz
-rw-------   1 root     root        78287 Apr 21 06:42 setuid.today
-rw-------   1 root     root        77873 Apr 18 06:42 setuid.yesterday

into cron.daily/standard:
savelog -c 7 setuid.changes >/dev/null

I think it should have -m 640 -u root -g adm to be sure of the perms.
--
 David Rocher

Message #20 received at 15295-close@bugs.debian.org (full text, mbox, reply):

From: Steve Greenland <stevegr@debian.org>

To: 15295-close@bugs.debian.org

Subject: Bug#15295: fixed in cron 3.0pl1-53

Date: 12 Sep 1999 18:53:15 -0000

We believe that the bug you reported is fixed in the latest version of
cron, which has been installed in the Debian FTP archive:
cron_3.0pl1-53.diff.gz
  to dists/potato/main/source/admin/cron_3.0pl1-53.diff.gz
  replacing cron_3.0pl1-52.diff.gz
cron_3.0pl1-53.dsc
  to dists/potato/main/source/admin/cron_3.0pl1-53.dsc
  replacing cron_3.0pl1-52.dsc
cron_3.0pl1-53_i386.deb
  to dists/potato/main/binary-i386/admin/cron_3.0pl1-53.deb
  replacing cron_3.0pl1-52.deb

Note that this package is not part of the released stable Debian
distribution.  It may have dependencies on other unreleased software,
or other instabilities.  Please take care if you wish to install it.
The update will eventually make its way into the next released Debian
distribution.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 15295@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Steve Greenland <stevegr@debian.org> (supplier of updated cron package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----

Format: 1.6
Date: Sat, 11 Sep 1999 18:42:37 -0500
Source: cron
Binary: cron
Architecture: source i386
Version: 3.0pl1-53
Distribution: unstable
Urgency: medium
Maintainer: Steve Greenland <stevegr@debian.org>
Description: 
 cron       - management of regular background processing
Closes: 8499 15295 23231 29909 30653 37189 37523 40312 42301 42454 43282
Changes: 
 cron (3.0pl1-53) unstable; urgency=medium
 .
   * Applied OpenBSD patches supplied Topi Miettinen. Big change is
   better handling of timekeeping (in particular, changes to/from daylight
   savings time) (closes:#8499).
   * Redirect stdin, stdout, and stderr to /dev/null.
   (closes:#37189, #23231, #30653).
   * Fixed bit_set()/bit_nset() confusion that caused @hourly to not work, so
   that functionality is now documented (closes:#43282).
   * Changed warrantee to warranty in debian/copyright (but it's still
   misspelled in the source files) (closes:#40312)
   * Adjust checksecurity and cron_daily/standard to get consistent owner/perms
   on /var/log/setuid* files. (closes:#15295)
   * Add 'coda' to the list of nfs/afs like file systems in checksecurity.conf
   (closes:#29909)
   * Fix version comparison to use dpkg --compare-versions, which is what I
   should have done in the first place (closes:#42454)
   * Add 'xfs' to the list of nfs/afs like file systems in checksecurity.conf,
   as it appears that xfs==arla and arla==xfs. If there are other file systems
   that show up as 'xfs', please let me know (closes:#37523)
   * Don't rotate wtmp and btmp (closes:#42301).
Files: 
 211e4cd7be08f94f42fb0c33dfe1e326 570 admin important cron_3.0pl1-53.dsc
 f277ff2c1c7d0aa25732b0996479e1d6 31620 admin important cron_3.0pl1-53.diff.gz
 191bc1317f6dab8fe6d81dd40082d7a6 49352 admin important cron_3.0pl1-53_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: 2.6.3ia
Charset: noconv

iQB1AwUBN9rt4GFSxbOcEsaBAQF1YwL9FfbspMs0/TdcdoZmu68qXmfzcCWQl60P
xC3xR8sMBlyqt68huO4cdimOCY/6SzchKISaWbFL10F0DZG8gdQQJu2wYAlOE3Co
6jm3tWOl8AOIT27c8TdOj6SE4OhlmkWW
=Tik+
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.