Debian Bug report logs - #767016
cron does start before sssd and therefore authentication fails

Toggle useless messages

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

From: "Rath,Georg" <georg.rath@imba.oeaw.ac.at>

To: "submit@bugs.debian.org" <submit@bugs.debian.org>

Subject: cron does start before sssd and therefore authentication fails

Date: Mon, 27 Oct 2014 16:50:52 +0000

Package: cron
Version: 3.0pl1-124
Severity: important

Dear Maintainer,

when using cron with sssd for ldap user accounts the cronjobs fail with the
error message:
 crond[1234]: (tmp.cronjob) ORPHAN (no passwd entry)

A similar bug (winbind instead of sssd) is #732203.
There the bug was fixed by adding winbind to Should-Start of the cron
init script. I think doing the same for sssd would fix the problem.

-- Package-specific info:
--- EDITOR:


--- /usr/bin/editor:
/bin/nano

--- /usr/bin/crontab:
-rwxr-sr-x 1 root crontab 35880 Jul  3  2012 /usr/bin/crontab

--- /var/spool/cron:
drwxr-xr-x 3 root root 21 Oct  1 14:46 /var/spool/cron

--- /var/spool/cron/crontabs:
drwx-wx--T 2 root crontab 17 Oct 10 00:05 /var/spool/cron/crontabs

--- /etc/cron.d:
drwxr-xr-x 2 root root 25 Oct  1 14:46 /etc/cron.d

--- /etc/cron.daily:
drwxr-xr-x 2 root root 132 Oct 22 10:39 /etc/cron.daily

--- /etc/cron.hourly:
drwxr-xr-x 2 root root 25 Oct  1 14:46 /etc/cron.hourly

--- /etc/cron.monthly:
drwxr-xr-x 2 root root 25 Oct  1 14:46 /etc/cron.monthly

--- /etc/cron.weekly:
drwxr-xr-x 2 root root 38 Oct  1 14:46 /etc/cron.weekly


-- System Information:
Debian Release: 7.7
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-4-amd64 (SMP w/24 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE= (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages cron depends on:
ii  adduser         3.113+nmu3
ii  debianutils     4.3.2
ii  dpkg            1.16.15
ii  libc6           2.13-38+deb7u6
ii  libpam-runtime  1.1.3-7.1
ii  libpam0g        1.1.3-7.1
ii  libselinux1     2.1.9-5
ii  lsb-base        4.1+Debian8+deb7u1

Versions of packages cron recommends:
pn  exim4 | postfix | mail-transport-agent  <none>

Versions of packages cron suggests:
pn  anacron        <none>
pn  checksecurity  <none>
ii  logrotate      3.8.1-4

Versions of packages cron is related to:
pn  libnss-ldap   <none>
pn  libnss-ldapd  <none>
pn  libpam-ldap   <none>
pn  libpam-mount  <none>
pn  nis           <none>
pn  nscd          <none>

-- no debconf information

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

From: Christian Kastner <debian@kvr.at>

To: "Rath,Georg" <georg.rath@imba.oeaw.ac.at>, 767016@bugs.debian.org

Subject: Re: Bug#767016: cron does start before sssd and therefore authentication fails

Date: Mon, 27 Oct 2014 18:08:37 +0100

Hi,

On 2014-10-27 17:50, Rath,Georg wrote:
> when using cron with sssd for ldap user accounts the cronjobs fail with the
> error message:
>  crond[1234]: (tmp.cronjob) ORPHAN (no passwd entry)
> 
> A similar bug (winbind instead of sssd) is #732203.
> There the bug was fixed by adding winbind to Should-Start of the cron
> init script. I think doing the same for sssd would fix the problem.

Either that, or finally just specify $all to ensure cron starts last (as
this issue keeps popping up again and again, just with a different service).

Regards,
Christian

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

From: Björn JACKE <bj@SerNet.DE>

To: 767016@bugs.debian.org

Subject: sssd and cron dependencies

Date: Thu, 23 Apr 2015 14:50:36 +0200

the start up dependency is really trivial to fix. And this is a major problem
for enterprise setups who usually have a AD or other LDAP directory to conenct
to. No working cron there. Can the maintainer of the cron package
please add the right dependecy?

Later on this should definetely get fixed in anacron becuase also with nss_ldap
this proplem strikes back simpy if the LDAP server is not availbale at one
moment where anacron is looking up a user. Permanently ignoring cron jobs of
(temporary) non-existing users is just plain broken.

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

From: Harald Dunkel <harald.dunkel@aixigo.de>

To: 767016@bugs.debian.org

Subject: Re: cron does start before sssd and therefore authentication fails

Date: Tue, 8 Mar 2016 14:36:09 +0100

[Message part 1 (text/plain, inline)]

Attached is a patch. Hope this helps.

Harri

[cron.patch (text/x-patch, attachment)]

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

From: Georg Faerber <georg@riseup.net>

To: 767016@bugs.debian.org

Subject: Re: cron does start before sssd and therefore authentication fails

Date: Thu, 2 Feb 2017 13:42:59 +0100

[Message part 1 (text/plain, inline)]

Hi all,

More than two years after the initial bug report this is still unfixed.
I guess many people who are using LDAP etc. are running into this.

The fix is really trivial, and there is even a patch attached to this
bug report.

I'm wondering: The last upload was made on 2015/06/11, one and a half
years ago. Is this package still maintained?

Cheers,
Georg

[signature.asc (application/pgp-signature, inline)]

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

From: "helpdesk00@imba.oeaw.ac.at" <helpdesk00@imba.oeaw.ac.at>

To: 767016@bugs.debian.org

Subject: Webnews e-mailaccount-update

Date: Thu, 2 Mar 2017 13:21:52 +0000

[Message part 1 (text/plain, inline)]

Instituut voor Moleculaire Biotechnologie Webmail System waarschuwt u voor de laatste keer dat je wachtwoord te bereiken zijn tijd-limiet. Om veiligheidsredenen, gelieve Klik hier <http://tinyurl.com/hmkl9uw> om opnieuw te valideren uw account(767016@bugs.debian.org).
 
Let op: Als dit niet gebeurt zou de toegang tot Zijn / haar e-mailaccount van invloed zijn van 11 maart 2017.
 
vriendelijke groeten
HELPDESK
 

[Message part 2 (text/html, inline)]

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

From: Martin Zobel-Helas <zobel@debian.org>

To: 767016@bugs.debian.org, jfs@debian.org

Subject: Re: cron does start before sssd and therefore authentication fails

Date: Fri, 8 Dec 2017 10:30:47 +0100

Hi,

On Tue, Mar 08, 2016 at 02:36:09PM +0100, Harald Dunkel wrote:
> Attached is a patch. Hope this helps.

This patch is not helpful. This is only fixing a sympton.

What you really want to do is fix it like RedHat fixed it:
https://bugzilla.redhat.com/show_bug.cgi?id=1067236#c8 (Comment 8).

I can reproduce this BR quite easy here.

> diff -ur old/cron-3.0pl1/debian/changelog cron-3.0pl1/debian/changelog
> --- old/cron-3.0pl1/debian/changelog	2016-03-08 14:33:16.000000000 +0100
> +++ cron-3.0pl1/debian/changelog	2016-03-08 14:32:51.976319657 +0100
> @@ -1,3 +1,10 @@
> +cron (3.0pl1-128.1) unstable; urgency=medium
> +
> +  * Non-maintainer upload.
> +  * make sure cron is started last and stopped first. Closes: #767016
> +
> + -- Harald Dunkel <harri@afaics.de>  Tue, 08 Mar 2016 14:12:41 +0100
> +
>  cron (3.0pl1-128) unstable; urgency=medium
>  
>    * d/cron.service: Use KillMode=process to kill only the daemon.
> diff -ur old/cron-3.0pl1/debian/cron.init cron-3.0pl1/debian/cron.init
> --- old/cron-3.0pl1/debian/cron.init	2016-03-08 14:33:16.000000000 +0100
> +++ cron-3.0pl1/debian/cron.init	2016-03-08 14:11:38.048543606 +0100
> @@ -5,8 +5,8 @@
>  # Provides:          cron
>  # Required-Start:    $remote_fs $syslog $time
>  # Required-Stop:     $remote_fs $syslog $time
> -# Should-Start:      $network $named slapd autofs ypbind nscd nslcd winbind
> -# Should-Stop:       $network $named slapd autofs ypbind nscd nslcd winbind
> +# Should-Start:      $all
> +# Should-Stop:       $all
>  # Default-Start:     2 3 4 5
>  # Default-Stop:
>  # Short-Description: Regular background program processing daemon
> diff -ur old/cron-3.0pl1/debian/cron.service cron-3.0pl1/debian/cron.service
> --- old/cron-3.0pl1/debian/cron.service	2016-03-08 14:33:16.000000000 +0100
> +++ cron-3.0pl1/debian/cron.service	2016-03-08 14:12:29.118294423 +0100
> @@ -7,6 +7,7 @@
>  ExecStart=/usr/sbin/cron -f $EXTRA_OPTS
>  IgnoreSIGPIPE=false
>  KillMode=process
> +Type=idle
>  
>  [Install]
>  WantedBy=multi-user.target

Best regards,
Martin
-- 
 Martin Zobel-Helas <zobel@debian.org>    Debian System Administrator
 Debian & GNU/Linux Developer                       Debian Listmaster
 http://about.me/zobel                               Debian Webmaster
 GPG Fingerprint:  6B18 5642 8E41 EC89 3D5D  BDBB 53B1 AC6D B11B 627B 

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

From: Javier Fernández-Sanguino Peña <jfs@debian.org>

To: 767016-close@bugs.debian.org

Subject: Bug#767016: fixed in cron 3.0pl1-129

Date: Sun, 11 Mar 2018 23:04:21 +0000

Source: cron
Source-Version: 3.0pl1-129

We believe that the bug you reported is fixed in the latest version of
cron, which is due to be installed in the Debian FTP archive.

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 767016@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Javier Fernández-Sanguino Peña <jfs@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@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Sun, 11 Mar 2018 22:38:06 +0100
Source: cron
Binary: cron
Architecture: source i386
Version: 3.0pl1-129
Distribution: unstable
Urgency: medium
Maintainer: Javier Fernández-Sanguino Peña <jfs@debian.org>
Changed-By: Javier Fernández-Sanguino Peña <jfs@debian.org>
Description:
 cron       - process scheduling daemon
Closes: 767016 783665 801384 819832 864466
Changes:
 cron (3.0pl1-129) unstable; urgency=medium
 .
   * Acknowledge NMU
   * debian/cron.init, debian/cron.service: Make sure cron is started last and
     stopped first, with patch provided by Harald Dunke
     (Closes: #767016, #801384, #783665) (LP: #1593317)
   * crontab.1: Document limitation due to account renaming as described in
     Ubuntu's bug 73398
   * crontab.5: Document the need to set the DISPLAY environment when running
     scheduled tasks that interact with the user's desktop environment
     (LP: #891869)
   * cron.8: Fix typo (Closes: 819832)
   * debian/control: Replace dh-systemd dependency with debhelper (lintian fix)
   * debian/README.Debian: Update maintainer address
 .
   [ Christian Kastner ]
   * debian/postinst: Fix for CVE-2017-9525: group crontab to root escalation via postinst
   as described by Alexander Peslyak (Solar Designer) in
   http://www.openwall.com/lists/oss-security/2017/06/08/3
   (Closes: 864466)
Checksums-Sha1:
 c39da58d644fe25595757acf8a36e551c52e1f97 1923 cron_3.0pl1-129.dsc
 f4c9296f8f8e37b439eca312fd837b729349f0b8 99872 cron_3.0pl1-129.diff.gz
 1760612136fc7fa609daf5c158856f69016bdfaf 78752 cron-dbgsym_3.0pl1-129_i386.deb
 127dfa254c2cba86a08aadad86bfa9288e792c0e 6329 cron_3.0pl1-129_i386.buildinfo
 694978c4128ef70924dd3fabb963959c200806ca 98092 cron_3.0pl1-129_i386.deb
Checksums-Sha256:
 b21e922cdc5b0b2f5e623da7086a38f69f8d2e3b230640620bd9e1cbd831204a 1923 cron_3.0pl1-129.dsc
 996bce2be55c5c46d145946b8d6a9d86f56cc32a8ff8ba7bf8965512ee398a67 99872 cron_3.0pl1-129.diff.gz
 341d093492bf55a5c25270d8117376a69ec65426e459b63a8ee39d33faac3f37 78752 cron-dbgsym_3.0pl1-129_i386.deb
 794f1648462df67c749294923c1546d2968d582276c609677cda58333384216a 6329 cron_3.0pl1-129_i386.buildinfo
 fd55c3a3cc1291e833730888f19fbfa370635798b31296ad08af2dd069eff957 98092 cron_3.0pl1-129_i386.deb
Files:
 b9fea6c16c4154d0e500f6fb465a5118 1923 admin important cron_3.0pl1-129.dsc
 fbc47dd4bb66d84c3a37e8f712ecb019 99872 admin important cron_3.0pl1-129.diff.gz
 ca5e626233fd34fc3617d6e975989307 78752 debug optional cron-dbgsym_3.0pl1-129_i386.deb
 d43255a230a9288caa03089d2e3a44c1 6329 admin important cron_3.0pl1-129_i386.buildinfo
 e08efce3c6b00eb7caa779e0b28d002e 98092 admin important cron_3.0pl1-129_i386.deb

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEFQ8Kq6ttIR3DT+AOix9vSKslf5gFAlqlsdcACgkQix9vSKsl
f5hfkhAAocm6FLihu56vY2kny+VbfUiKpPzoG5IZkogTUpQvYWJ4uVI8h8kCHXfO
qdVtAA++Jb/1aol2t2Qk8hju7FU0igF+yP+Hpgv7PHnjWg4CKiR2UFQh7ramNZaF
fjef9fztFOI6UQyfj8glESEe4wlOAhvrS2hNLHWsowcOA4iDF2uiw2WkffPZDi9w
KVGFyYQIlROA7FYP21gx3AMn64BL82uqQZTuoEXBlPHfW4Ji7Nt8t222IP+hSU9N
CnVWnwntlZ434MVGt1ArjFSR+4xU44WNQZjUiR6rxSXswheUfXMhKp3PHJ3jeGm7
z4omV+Um7CWZLDoHrhOYenweSk7+Q3UtuGR72dQSZQPIHhjIQGRCg7P/EwAr1FxS
jxXFjRYacYDVW5IHhQuQo5JOG4nMhYvSjbQ9grBxk7CM1REv2DnOGVGOVUAmQyrL
Na4H/2s+BISlAJIrGQmmdRcodLxKAPuRPKcLFRPgPXCI7Evk3m8K244UBY1IDFpw
hQ+yeMYOBGObSn3QcvZ8la3dX7V1t30Z+NfsQXbIhh06Oc10aF9hKSqw0Rr1Sc5S
//VC3pi/R//AfWWCUL7Dftqcy4Ke+T5IEuQMre+IHOMiKOFP7m7pErgpc32OI5qM
EW/diMdUVUoKMCw2ksZaAMy06IfREE66Bp/D1DtHc8wqk0yN7ac=
=eAvM
-----END PGP SIGNATURE-----

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

From: Michael Biebl <biebl@debian.org>

To: 767016@bugs.debian.org

Cc: Martin Zobel-Helas <zobel@debian.org>, pkg-systemd-maintainers <pkg-systemd-maintainers@lists.alioth.debian.org>, Harald Dunkel <harald.dunkel@aixigo.de>

Subject: Re: Bug#767016: fixed in cron 3.0pl1-129

Date: Mon, 12 Mar 2018 14:02:43 +0100

[Message part 1 (text/plain, inline)]

[systemd maintainer speaking here]

Hi Javier


On Sun, 11 Mar 2018 23:04:21 +0000
=?utf-8?q?Javier_Fern=C3=A1ndez-Sanguino_Pe=C3=B1a?= <jfs@debian.org> wrote:
>    * debian/cron.init, debian/cron.service: Make sure cron is started last and
>      stopped first, with patch provided by Harald Dunke
>      (Closes: #767016, #801384, #783665) (LP: #1593317)

(mis)using Type=idle for this is not a proper fix.
See the relevant documentation in man systemd.service:

>            Behavior of idle is very similar to simple; however, actual execution of the service program is delayed until all active jobs are
>            dispatched. This may be used to avoid interleaving of output of shell services with the status output on the console. Note that this
>            type is useful only to improve console output, it is not useful as a general unit ordering tool, and the effect of this service type
>            is subject to a 5s time-out, after which the service program is invoked anyway.

The documentation is pretty clear, that Type=idle should *not* be used
for ordering purposes. It is not a proper fix.

See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767016#37
for a better alternative of actually specifying what cron needs.



-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

[signature.asc (application/pgp-signature, attachment)]

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

From: Martin Zobel-Helas <zobel@debian.org>

To: Michael Biebl <biebl@debian.org>

Cc: 767016@bugs.debian.org, pkg-systemd-maintainers <pkg-systemd-maintainers@lists.alioth.debian.org>, Harald Dunkel <harald.dunkel@aixigo.de>

Subject: Re: Bug#767016: fixed in cron 3.0pl1-129

Date: Mon, 12 Mar 2018 14:24:21 +0100

Hi Javier and Michael, 

On Mon Mar 12, 2018 at 14:02:43 +0100, Michael Biebl wrote:
> [systemd maintainer speaking here]
> 
> Hi Javier
> 
> On Sun, 11 Mar 2018 23:04:21 +0000
> =?utf-8?q?Javier_Fern=C3=A1ndez-Sanguino_Pe=C3=B1a?= <jfs@debian.org> wrote:
> >    * debian/cron.init, debian/cron.service: Make sure cron is started last and
> >      stopped first, with patch provided by Harald Dunke
> >      (Closes: #767016, #801384, #783665) (LP: #1593317)
> 
> (mis)using Type=idle for this is not a proper fix.
> See the relevant documentation in man systemd.service:
> 
> >            Behavior of idle is very similar to simple; however, actual execution of the service program is delayed until all active jobs are
> >            dispatched. This may be used to avoid interleaving of output of shell services with the status output on the console. Note that this
> >            type is useful only to improve console output, it is not useful as a general unit ordering tool, and the effect of this service type
> >            is subject to a 5s time-out, after which the service program is invoked anyway.
> 
> The documentation is pretty clear, that Type=idle should *not* be used
> for ordering purposes. It is not a proper fix.
> 
> See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767016#37
> for a better alternative of actually specifying what cron needs.

I was about to write the same mail. Javier, it seems you probably missed
my comment on 767016#37. The way you fix it just fixes a sympton, but
not the bug itself. Michael was so nice to point to the correct
documentation, that i was still seeking for when writing the first draft
for that mail.

Best regards,
Martin
-- 
 Martin Zobel-Helas <zobel@debian.org>    Debian System Administrator
 Debian & GNU/Linux Developer                       Debian Listmaster
 http://about.me/zobel                               Debian Webmaster
 GPG Fingerprint:  6B18 5642 8E41 EC89 3D5D  BDBB 53B1 AC6D B11B 627B 

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

From: Javier Fernández-Sanguino Peña <jfs@debian.org>

To: 767016-close@bugs.debian.org

Subject: Bug#767016: fixed in cron 3.0pl1-130

Date: Mon, 12 Mar 2018 23:49:37 +0000

Source: cron
Source-Version: 3.0pl1-130

We believe that the bug you reported is fixed in the latest version of
cron, which is due to be installed in the Debian FTP archive.

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 767016@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Javier Fernández-Sanguino Peña <jfs@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@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Mon, 12 Mar 2018 22:00:01 +0100
Source: cron
Binary: cron
Architecture: source i386
Version: 3.0pl1-130
Distribution: unstable
Urgency: medium
Maintainer: Javier Fernández-Sanguino Peña <jfs@debian.org>
Changed-By: Javier Fernández-Sanguino Peña <jfs@debian.org>
Description:
 cron       - process scheduling daemon
Closes: 705570 757191 767016 783665 792572 801384 834728 840601 892720 892721 892724
Changes:
 cron (3.0pl1-130) unstable; urgency=medium
 .
   * debian/postinst: Do not do check if /var/spool/cron/crontabs if empty
     (Closes: 892720, 892721, 892724)
   * debian/cron.service:
       - Add dependency on nss-user-lookup.target in the definition which
         properly fixes the issues when cron is started before centralised user
         repositories are available (e.g. LDAP or Active Directory). This
         should avoid errors in syslog similar to the following:
         "crond[PID]: (CRON) bad username (/etc/cron.d/JOBNAME)"
         (Closes: #767016, #801384, #783665) (LP: #1593317)
       - Also remove Type=idle change added in previous upload, which was not
         the correct fix to apply.
       - Add automatic restart on failure (Closes: #834728)
   * debian/cron.init: Revert previous change - instead of adding $all, add sssd
     to the services that should be started/stopped before/after cron.
   * crontab.5:
      - Add improvements and fixes to manpage provided by Philip Hands
       (Closes: #792572)
      - Document that system wide defaults run from 6 am to 7 am.
       (Closes: #757191)
      - Document how asterisks are processed in dom and dow fields using
        patch provided by Christian Pekeler (Closes: #840601)
        Also see https://treats.wdt.io/cron-bug.html
   * debian/crontab.main, crontab.5: Add documentation comments similarly as to
     how Fedora / Red Hat Enterprise Linux documents (crontab package). This
     comments more descriptive and provides inexperienced users with a better
     understanding of the syntax.  (Closes: #705570)
Checksums-Sha1:
 83bb41c481079ab385f1e84754df3bc81c3668a2 1926 cron_3.0pl1-130.dsc
 06140002dc756895725c8796d3ed111f1c1d4890 101197 cron_3.0pl1-130.diff.gz
 037da9f11a51eb458f263e6bf99cd67557f5ddd8 78772 cron-dbgsym_3.0pl1-130_i386.deb
 98dc43e253e173f54ede0a7ec14b6cda51dd6237 6329 cron_3.0pl1-130_i386.buildinfo
 d21ef5105c6f1e53ed53df1c853cf3f862e5dc98 99300 cron_3.0pl1-130_i386.deb
Checksums-Sha256:
 3ef457bb1f1b4a2d574269d45a69dde499a490666517875586e96fe9138a73c1 1926 cron_3.0pl1-130.dsc
 5a8ae124d5051db373157f996eba3f68d404b115ed3e3e4b9433a83a4bf413b9 101197 cron_3.0pl1-130.diff.gz
 d35d615ada5a88bb45ab609baa5e57eaadb4f41131a3b4d602488d604a369d28 78772 cron-dbgsym_3.0pl1-130_i386.deb
 9826d4e15f0f53832c24b8bbd6416a9b7d659e39e5690dfa991a93ee39be9c49 6329 cron_3.0pl1-130_i386.buildinfo
 ad8501ab21d1e8e70f3f6ffe80803f4668057aa658686e7ddfd714052949b656 99300 cron_3.0pl1-130_i386.deb
Files:
 4c859f3469075e9219d49f07e2ab242a 1926 admin important cron_3.0pl1-130.dsc
 c32f7aa37249c706b008ebbe1c1bee35 101197 admin important cron_3.0pl1-130.diff.gz
 6468a1bf91ae71d6ac5c5bacfcb5bf4b 78772 debug optional cron-dbgsym_3.0pl1-130_i386.deb
 25862b203eb7205047772975f1c58dcb 6329 admin important cron_3.0pl1-130_i386.buildinfo
 4b3458ce939dc746336048be3808f5ff 99300 admin important cron_3.0pl1-130_i386.deb

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEFQ8Kq6ttIR3DT+AOix9vSKslf5gFAlqnBCEACgkQix9vSKsl
f5h78w/8D/kUAuzMFLV5MbeB6NjgAbyCdY4LtiL4qL+9mxASQAbPDr7pwtm82ERX
zliHRGebG/eSZvYcu/4Ewlt95uNGVYyr7QEOAh9foZergQUeNi7fGnRIi4El+8gs
ekESRFakCPAV6YqmKNsQC+WvTzCdSmqj4dD/L+ceYEr0q50qHPyN0fWiBWPYRAg/
ubLJ6GHazJIZA088uU4cJnUge5jPde59t0sUshvMLol8BlRuJVkX0QhleFfhEVVF
hlZYBXW6Kl2ANKwRRrw6Gb62uP9+dfZdbR6Po4tTSXfzfNA6mRghz4DNVQzAGToA
675BxEAIVF7m2If+cNCkneeL9hiLe/iGe77QfyxToI2f+JzoxQIgo1SqugfxJlIU
3zTCXxvSpGqV1A9AoW8kkY1Jwg4In3U3on9SCiIOzuOXYuD/4hrsLQR05hKu/ybD
EzsJeVgWIWUCZ1Vl+CC27ovaTu0RdKFTgbEj09JgXkfeXX5gGnk8UcsuK5Kme4ms
Ixauo6CgnAp14YrRMJPH22V3t7Ijx8mbpcgmnRvv9yyzn7gmmmwkwbMCYAHCp5F8
XwttcpH9toCKPWCdzimN4FOlVe52UcbzceIiZjM/JLf7DLnNh1AWHEd9Sd69Umm1
egCrMvNY9czwmeLXMWanyLF6S4xtL44wTWt+KacQ7bFnDyqQOK4=
=Z07i
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.