What's happening here is that some TLS implementations and servers started randomizing their timestamps. Seems this happened on www.ptb.de.
Other distributions sometimes have www.google.com set as their timesource. This is more reliable because google itself is using tlsdate for chromeos. On the long term the tls timestamp will probably go away anyway. An alternative is to use the HTTP header time. (or fix ntp, which is currently being done, but that's another story) I'd suggest debian patches tlsdate to use www.google.com. Reported upstream as well: https://github.com/ioerror/tlsdate/issues/172
pgpZ7KsNuERnr.pgp
Description: OpenPGP digital signature
