tlsdate default settings set time to random value

Bug #1448629 reported by Hanno Böck
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
tlsdate (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

tlsdate sets the time based on a TLS timestamp from a TLS server.

The tlsdate tool comes preconfigured with the server www.ptb.de. However that server now randomizes the timestamp, possibly causing lots of trouble. A possibility to fix this would be to use www.google.com. As google itself uses tlsdate it's to be expected that they don't change the setting to ramdomize the tls timestamp.

Please note: This is preconfigured in two places. Once for the tlsdate tool in the tool itself and once in the tlsdated.conf daemon config file.

Upstream bug:
https://github.com/ioerror/tlsdate/issues/172

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in tlsdate (Ubuntu):
status: New → Confirmed
Revision history for this message
Frank (a-frank) wrote :

Can we tag this with security? People who've installed this package, and rely on it to set the correct date, will have incorrect dates. Incorrect dates lead to all kinds of strange security stuff.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.