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

tlsdate + SNI = sadness #161

Open
Spindel opened this issue Nov 5, 2014 · 0 comments
Open

tlsdate + SNI = sadness #161

Spindel opened this issue Nov 5, 2014 · 0 comments

Comments

@Spindel
Copy link

Spindel commented Nov 5, 2014

Based on empirical testing of 0.0.8 (debian) it seems that tlsdate does not support SNI.

Test setup:
default certificate of the host is always localhost.localdomain ,selfsigned certificate
All public-facing hostnames are on SNI only.
This is both for our test & production environment, to make sure that our code isn't accidentally depending on a default value somewhere.

Currently, tlsdate will refuse to use the assigned hostnames public certificate, as it gets the self-signed localhost cert when connecting without using SNI.

Proper time is gathered if you disable certificate checking, which isn't quite what we are after.

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

1 participant