Skip to content
This repository has been archived by the owner on Nov 10, 2020. It is now read-only.

Untrusted SSL cert == "unable to ping" #36

Open
wsanchez opened this issue Jul 29, 2014 · 10 comments
Open

Untrusted SSL cert == "unable to ping" #36

wsanchez opened this issue Jul 29, 2014 · 10 comments
Assignees
Labels

Comments

@wsanchez
Copy link
Member

If the server is using an untrusted X.509 certificate (eg. a self-signed cert), then the application brings up an error dialog when attempting to connect:

screen shot 2014-07-29 at 10 41 22 am

@wsanchez wsanchez added this to the Burning Man 2014 milestone Jul 29, 2014
@wsanchez wsanchez added the Bug label Jul 29, 2014
@wsanchez wsanchez self-assigned this Jul 29, 2014
@wsanchez
Copy link
Member Author

Work-around is to connect to the server in Safari, accept the cert, then re-launch the IMS application.

@wsanchez
Copy link
Member Author

The Safari thing prevents spoofing. Not sure how to add that cert/keychain dialog into the app.

@wsanchez
Copy link
Member Author

This no longer happens, though that's because it's now not validating the cert, so that's kinda dumb.
Filed #49 for that.

@wsanchez
Copy link
Member Author

OK, fixed #49, and this is back. Re-opening.
Work-around is to visit the server with (eg.) Safari and accept the cert there; then the IMS app will work.

@wsanchez
Copy link
Member Author

ad72af4 adds code that will bypass the TLS auth, but that's back to being lame.

What I'd like is the "trust this cert?" dialog one sees in Safari, I think.

Alternatively, we could add a preference to import a trusted CA cert to the app and use certs by that CA (or import a specific cert to trust, but that's less flexible and not any easier on the user).

@flwyd
Copy link

flwyd commented Nov 13, 2015

Rather than using a self-signed cert, would a free, trusted, cert from https://letsencrypt.org/ solve the problem?

@flwyd
Copy link

flwyd commented Nov 13, 2015

(The actual-cert solution might be tricky if the client is connecting to a server's LAN address rather than a public URL.)

@wsanchez
Copy link
Member Author

Yeah, Let's Encrypt would make getting a "real" cert easier, as I think their CA should be in Apple root CA list now, but I'd still like to figure out how to get allow the client to view and accept a random cert, because I think that may be necessary on playa.

Self-signed certs are basically like SSH host keys. Trust once (ideally verify manually first), then complain when it changes. I think that model works OK in our usage.

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

No branches or pull requests

2 participants