Hi Sebastian,
On 4/23/15, Sebastian Pipping <sebast...@pipping.org> wrote:
> 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?
>
ptb.de appears to be randomizing time stamps. I'm open to a new
default host for Debian or for upstream. Thoughts? A TLS enabled
debian.org host (which one?) could do the trick if it wouldn't upset
anyone.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
