View Single Post
Originally Posted by jbrown View Post
Apple asked us to switch to their public API for approving untrusted certificates in 1.6.1. The warning you're seeing is a normal part of the API, and once you select "Trust always", shouldn't ask you to approve again (unless you turn off Bonjour sync, then turn it back on, since you're effectively generating a new self-signed certificate). Hope this clears things up!
Not providing some way of identifying whether the certificate in question is one you should trust is a problem. Displaying a certificate fingerprint in both the mac and iPhone client would solve this. If this isn't supported as a consequence of the Apple API, they need some beating on to understand that.