Always trust certificates? about telegraph HOT 6 CLOSED

realized if you "trust always" and don't recompile it should trust always. I was getting this a lot since my service is a WIP

from telegraph.

You can add the PKCS#12 (.p12) file to the keychain.
Then double click on the key and change access to Allow all applications to access this item.

That should take care of the Keychain prompts.

from telegraph.

Will trusting it on your machine before compiling enable it to work when you distribute it?

from telegraph.

@MikeyLew Self-signed certificates need to be added to the machines that will run the webserver. Unfortunately it isn't possible to compile this into the app, because that would allow developers to override system certificates.

Malicious apps would for example be able to include a certificate for google.com and break into Gmail and your web searches.

If you deploy your app using an installer, you can probably add logic to deploy a root certificate for your own certificate authority. This link might provide some useful info.

from telegraph.

Thanks for this, so we can't use Telegraph as a HTTPS server within an App distributed on the App store then? Thanks for clarifying 👍

from telegraph.

@MikeyLew You are free to use Telegraph as an HTTPS server in App Store apps.

For Mac apps it would probably be best if you add a configuration dialog where the user can select the certificate that is going to be used by the server.

For iOS apps you could create your own Certificate Authority. But it would require installation of the certificates on the devices.

If you control the client app you can also perform manual HTTPS certificate validation. See this section of the README on how to do that.

from telegraph.