Your message dated Fri, 29 May 2015 16:51:08 +0000
with message-id <e1yynuy-0002tv...@franck.debian.org>
and subject line Bug#783174: fixed in tlsdate 0.0.13-1
has caused the Debian Bug report #783174,
regarding tlsdate: Time retrieved from default host (www.ptb.de) jumping all
over the place?
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~bpo70+1
Severity: normal
When using debian.org for a host, time is somewhat stable:
$ for i in {1..10}; do tlsdate --dont-set-clock --showtime -H debian.org ; done
Thu Apr 23 13:06:59 CEST 2015
Thu Apr 23 13:06:58 CEST 2015
Thu Apr 23 13:06:58 CEST 2015
Thu Apr 23 13:06:59 CEST 2015
Thu Apr 23 13:07:00 CEST 2015
Thu Apr 23 13:07:01 CEST 2015
Thu Apr 23 13:07:03 CEST 2015
Thu Apr 23 13:07:01 CEST 2015
Thu Apr 23 13:07:02 CEST 2015
Thu Apr 23 13:07:03 CEST 2015
However, the default host "www.ptb.de" off pristine /etc/tlsdate/tlsdated.conf
shows different behavior:
$ for i in {1..10}; do tlsdate --dont-set-clock --showtime -H www.ptb.de ; done
| sed 's|CET|CET |'
Thu Jan 18 00:20:52 CET 1973
Sun Apr 22 21:45:01 CEST 2018
Thu Nov 25 03:42:48 CET 1971
Wed Oct 23 06:20:11 CEST 1996
Tue Jan 29 07:36:25 CET 2104
Wed Aug 2 08:54:05 CEST 2017
Sat Jan 13 03:44:29 CET 2046
Fri Jan 28 04:20:04 CET 2101
Sun Dec 27 03:11:09 CET 2105
Fri Feb 8 05:32:52 CET 2013
I am unsure if that's a bug in tlsdate or broken/compromised setup at
www.ptb.de. Any ideas?
Best, Sebastian
-- System Information:
Debian Release: 7.8
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages tlsdate depends on:
ii libc6 2.13-38+deb7u8
ii libevent-2.0-5 2.0.19-stable-3+deb7u1
ii libssl1.0.0 1.0.1e-2+deb7u16
tlsdate recommends no packages.
Versions of packages tlsdate suggests:
pn apparmor <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: tlsdate
Source-Version: 0.0.13-1
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.
Jacob Appelbaum <ja...@appelbaum.net> (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: Thu, 28 May 2015 19:02:28 +0000
Source: tlsdate
Binary: tlsdate
Architecture: source
Version: 0.0.13-1
Distribution: unstable
Urgency: high
Maintainer: Jacob Appelbaum <ja...@appelbaum.net>
Changed-By: Jacob Appelbaum <ja...@appelbaum.net>
Description:
tlsdate - secure parasitic rdate replacement
Closes: 783174 783193
Changes:
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:
93a15a223c6c8f614740e0da783231466bb77d56 2036 tlsdate_0.0.13-1.dsc
223d92599151a9e23a0cdd980d29eaa9078e0e19 220080 tlsdate_0.0.13.orig.tar.xz
eb3351c1bf0259ab3118a661a220afb3ddb048b2 12064 tlsdate_0.0.13-1.debian.tar.xz
Checksums-Sha256:
524c8ce3120fa87781ef2f247ef297ec8be69502cb11ef704d0967fbe76a17d5 2036
tlsdate_0.0.13-1.dsc
39dbafdf1572b6e4d3f91f89295e0f026d06115666f76a5f4c9fd9d067b8fdac 220080
tlsdate_0.0.13.orig.tar.xz
276d305cc345ada1e59481961390afc9e6277aff1e994bca77d99599c8e764dc 12064
tlsdate_0.0.13-1.debian.tar.xz
Files:
05c50ac99007516b395c8df5f3fc4210 2036 net extra tlsdate_0.0.13-1.dsc
48017a5e9c67e3b369c92e9d49ef4883 220080 net extra tlsdate_0.0.13.orig.tar.xz
f06f000a5d53f13d606ce8e59a4a6278 12064 net extra tlsdate_0.0.13-1.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iQIVAwUBVWiTuQkauFYGmqocAQoDhA/+KyABzFfE1lAlQm5N67nRZFDdksVyrQnQ
Axa2rhBey5rqJtlEpbEgz5V3zWk5yUK3k7c2ObQykWuvwLZOT5BPG1E9xL9B9lhO
tw162753+L5AbvGL9BXteZhtTfT1wLOeU1swxW0fUculheSaSeeOs20mDyDLGJiO
ossl/D42pQ3nuHRTiJLJ//VZl3vllTEKhWrwlqIy25BkvNn1ZMFW0n5A6AtHuq4c
tgMlro9f737nTssKt91Wpys2mIwYqMXExdTP+0G7LVENx4Mus0A7lAzXS9zagjod
nU5VcMEmXoljfaTs5AQzxPpMNMb3bxqlUoU7+l3GaMbjte5Qgd/a4QrTAD5zTBcD
XuckwtLQEgC1Yrbx4cpNplDUlxsEbL+tZa7nbBwr2krCTASzhQ2PjjpNhAV+YRCx
EUvazUZDsK6PtNJWZDaRLt2KkiEe1zV/MXC0jftYuy1wWKLLiNoT+LOJ0vDa7YNC
zl+DStTiBed4r2sGgGnRXIuGTBWbuf0VijVZQwp/NCVeLdnFSxXEAuctOUr1DpIB
Nl2CWXPGq9QdKbcqa7B9uvJrDgmOavT7A8QvoF60ozwjnuUKKX+j+A4vmAF6HsKz
pn25DtmXrPM3oRv9M7Ga0orvs4GmEHvQoGGauHU4BaRZ1VnC2Xmukok5KJwYkkKB
Q+1vqgR3xnQ=
=yUFL
-----END PGP SIGNATURE-----
--- End Message ---
