Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Why times are all different? Only "google.com" returns accurate time! #195

Open
ghost opened this issue Nov 5, 2016 · 2 comments
Open

Comments

@ghost
Copy link

ghost commented Nov 5, 2016

tlsdate -n -s -H SEREVER.FQDN.HERE -p 443 -v -V

Time is correct:
www.google.com

Time is TERRIBLE:
mail.riseup.net (UTC 1941!?)
www.torproject.org (UTC 2029!)
www.nsa.gov

When I visit these websites using a browser, it returns correct "Date:".
Why tlsdate can't detect it?

@oniGino
Copy link

oniGino commented Nov 6, 2017

I'm my understanding that as an additional security measure TLS(all versions?) now randomize the date+time it sends.. so effectively killing this project... which is really too bad since ntp really needs an solid alternative

Here is a quick blurb that sums it up well
https://security.stackexchange.com/questions/71364/tls-reliance-on-system-time

@AlexeySalmin
Copy link

which is really too bad since ntp really needs an solid alternative

That is true :( If anyone discovers an alternative please share a link here so that subscribed users can see it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants