Your message dated Sat, 30 May 2015 18:17:05 +0000 with message-id <e1yyljh-0007pb...@franck.debian.org> and subject line Bug#783174: fixed in tlsdate 0.0.13-1~deb8u1 has caused the Debian Bug report #783174, regarding tlsdate: Sets time wrong to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 783174: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783174 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: tlsdate Version: 0.0.12-2 Severity: grave Hi, I found this in my syslog today: Apr 23 16:09:23 intrepid tlsdated[3408]: [event:action_run_tlsdate] requested re-run of tlsdate while tlsdate is running Apr 23 16:09:23 intrepid tlsdated[3408]: [event:action_tlsdate_status] invalid time received from tlsdate: 3466176706 Apr 23 16:09:39 intrepid tlsdated[3408]: [event:action_tlsdate_status] invalid time received from tlsdate: 2110302677 Apr 23 16:09:40 intrepid tlsdated[3408]: [event:action_run_tlsdate] requested re-run of tlsdate while tlsdate is running Apr 23 16:09:40 intrepid tlsdated[3408]: [event:action_tlsdate_status] invalid time received from tlsdate: 198483556 Apr 23 16:09:48 intrepid tlsdated[3408]: [event:action_tlsdate_status] invalid time received from tlsdate: 42183177 Apr 23 16:09:53 intrepid tlsdated[3408]: [event:action_tlsdate_status] invalid time received from tlsdate: 3462611409 Apr 23 16:09:58 intrepid tlsdated[3408]: [event:action_tlsdate_status] invalid time received from tlsdate: 3695382819 Apr 23 16:10:02 intrepid tlsdated[3408]: [event:action_run_tlsdate] requested re-run of tlsdate while tlsdate is running Apr 23 16:10:02 intrepid last message repeated 4 times Apr 23 16:10:02 intrepid tlsdated[3408]: [event:action_tlsdate_status] invalid time received from tlsdate: 404492764 Apr 23 16:10:03 intrepid tlsdated[3408]: [event:action_run_tlsdate] requested re-run of tlsdate while tlsdate is running Apr 23 16:10:03 intrepid tlsdated[3408]: [event:action_tlsdate_status] invalid time received from tlsdate: 2661297035 Apr 23 16:10:04 intrepid tlsdated[3408]: [event:action_tlsdate_status] invalid time received from tlsdate: 2210707233 Apr 23 16:10:04 intrepid tlsdated[3408]: [event:action_tlsdate_status] invalid time received from tlsdate: 3820078853 Apr 23 16:10:05 intrepid tlsdated[3408]: [event:action_run_tlsdate] requested re-run of tlsdate while tlsdate is running Apr 23 16:10:05 intrepid tlsdated[3408]: [event:action_run_tlsdate] requested re-run of tlsdate while tlsdate is running Oct 4 11:10:36 intrepid tlsdated[3415]: synced rtc to sysclock Oct 4 11:10:36 intrepid named[13844]: error (no valid DS) resolving 'ns2.mail.ru/A/IN': <unknown address, family 57054> Oct 4 11:10:36 intrepid tlsdated[3408]: [event:handle_time_setter] time set from the network (1570180236) Oct 4 11:10:36 intrepid named[13844]: validating @0x7fc5f88d97c0: . DNSKEY: verify failed due to bad signature (keyid=19036): RRSIG has expired Oct 4 11:10:36 intrepid named[13844]: validating @0x7fc5f88d97c0: . DNSKEY: unable to find a DNSKEY which verifies the DNSKEY RRset and also matches a trusted key for '.' Oct 4 11:10:36 intrepid named[13844]: validating @0x7fc5f88d97c0: . DNSKEY: please check the 'trusted-keys' for '.' in named.conf. That would be Oct 4 2019. Kurt
--- End Message ---
--- Begin Message ---Source: tlsdate Source-Version: 0.0.13-1~deb8u1 We believe that the bug you reported is fixed in the latest version of tlsdate, 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 783...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Holger Levsen <hol...@debian.org> (supplier of updated tlsdate 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 ftpmas...@ftp-master.debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 1.8 Date: Sat, 30 May 2015 14:55:55 +0200 Source: tlsdate Binary: tlsdate Architecture: source Version: 0.0.13-1~deb8u1 Distribution: jessie Urgency: high Maintainer: Jacob Appelbaum <ja...@appelbaum.net> Changed-By: Holger Levsen <hol...@debian.org> Description: tlsdate - secure parasitic rdate replacement Closes: 783174 783193 Changes: tlsdate (0.0.13-1~deb8u1) jessie; urgency=high . * Upload to stable to switch from www.ptb.de to www.google.com as the former is now sending randomized gmt values. (Closes: #783174, #783193) . tlsdate (0.0.13-1) unstable; urgency=high . * New upstream release . tlsdate (0.0.12-3) unstable; urgency=high . * Switch from www.ptb.de to www.google.com as the former is now sending randomized gmt values. (Closes: #783174) (Closes: #783193) Checksums-Sha1: c94431678a4813662829491e3908e9503a394d81 2064 tlsdate_0.0.13-1~deb8u1.dsc 9cda0779fe1ab894d410eb60551048d8fa53ddfe 12124 tlsdate_0.0.13-1~deb8u1.debian.tar.xz Checksums-Sha256: 0db8ba3a81b11359aa34675b0bccd0702023bfac5d1a0dbca5b72c5857fa9498 2064 tlsdate_0.0.13-1~deb8u1.dsc 4c50529c1d6adfc23b307cd192e6b4a22a84d7aacf60e24a32597ab9251ed693 12124 tlsdate_0.0.13-1~deb8u1.debian.tar.xz Files: 8635bce29953a82a488b8a09297ab791 2064 net extra tlsdate_0.0.13-1~deb8u1.dsc cde04bfa32f66cef6b2222a4f1000024 12124 net extra tlsdate_0.0.13-1~deb8u1.debian.tar.xz -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iQIVAwUBVWnEjAkauFYGmqocAQr7rQ/+LhFMZquJgq0C0YMsoPzeG4qmieAaQA/z b9GUVlBWcwiXub+s525UZLt6Nhp3SEy8arV1mepEuqcC90JtNixAoUcwFSQYE0/S G2Sd4EWt/4zqsw2WKz9yWVhdH5+G/31b0VaVoPU+gX7j1ffA+4BdnnJgEPU4arTX X4XxgJvLsmhSNa8qFmdtRxwQBcvBLmjwa8jNjq/q+Gdng7m9pF8rOJX5mUT7vQ4s aURO14fd7mg65AQ0spafnIwX3UWO9N8cgqEsFmXs8subLhEAEEwEzCpok+hwCZf1 yC3ZTZiW3iL91XQvZoWIOPniAXNyH+E5dprn0EVGMZVKyIBtYh4JftCD+KdRffFs doez7hFzWM9AP8AhoH5UEgSiM/ARTvbeV4qL312q2+sYJyan1eQugLU2IgqDQi3V MWTuOO1avdy9JrKT/28BY1QiK75g/cW/AAYerC9iHBIBt6dUUOgYWdSjmenoM1AS gTCoU71ryZ1efvvLktsKaTJrRwDUn4wmukDZqbr1g+jvJt3xrXAfeL3OC9yYYQjC /7P7t2MxRpVmXqr0RJqCb0ebzisF1rBFz11UEzoIJrbUjji4GF8HBAnwUWS/+wQf 5H1q4ulhOfIogt1kxedo4mwiFHNYlj7shvIOPAXMu9jFJsVK9kevSwDksmbDKPKR M02wNy+kp1o= =Fsn2 -----END PGP SIGNATURE-----
--- End Message ---
