- #IPHONE MUMBLE CERTIFICATE PC#
- #IPHONE MUMBLE CERTIFICATE WINDOWS 8#
- #IPHONE MUMBLE CERTIFICATE FREE#
It only gives me back a single item, signalling that only the "identity" (cert and private key) was imported, but no intermediates or roots were processed.Īt this point, I haven't dug deeper than the SecPKCS12Import function, so I can't really get detailed errors on a certificate level as of yet, but the next step will be to to try and parse the intermediates with SecCertificateCreateWithData. The error is in Apple's SecPKCS12Import function. Once I selected my StartSSL certificate and attempted to connect, once again, to my test server, the server aborted the handshake for the same reason you cited above. D'oh! My apologies for being a dumbass.Īnyway. Seemingly, I must have imported my StartSSL cert and attempted to connect to my test server with my usual certificate, and was unable to reproduce the error. Then, I saw the previous StartSSL certificate I had imported (earlier in this issue thread), but noticed something was amiss: its intermediates weren't actually present in my certificate store at all! Once I got to the part where I needed to import it into the iOS app, I wanted to make sure I did not have any other certificates in the store that could conflict with it. I went through creating a new StartSSL identity in an attempt to reproduce the issue. I returned to this issue today, and took a look at it with a fresh set of eyes. p12 file you used when importing? Windows's certificates panel? OS X keychain? OpenSSL?ĭo you by any chance have a certificate with a similar Common Name in your Mumble app's keychain already? If that happens, the iOS keychain will fail to import. subject=/C=IL/O=StartCom Ltd./OU=Secure Digital Certificate Signing/CN=StartCom Class 1 Primary Intermediate Client CA.Issuer=/C=IL/O=StartCom Ltd./OU=Secure Digital Certificate Signing/CN=StartCom Certification Authority subject=/C=IL/O=StartCom Ltd./OU=Secure Digital Certificate Signing/CN=StartCom Certification Authority.
subject=/description=fKlZsPyXcDzq3hIA/CN= Ltd./OU=Secure Digital Certificate Signing/CN=StartCom Class 1 Primary Intermediate Client CA.Seemingly the same certificates as yours, although openssl CLI prints them in a weird order for me: p12 file with encrypted private key, exported via Windows's cert tool, into Mumble for iOS. 20:49:19.495 1 => 24:(-1) SSL Error: The root CA certificate is not trusted for this purpose Snippet of the server log from a failed iPad connection:
#IPHONE MUMBLE CERTIFICATE FREE#
In this case the third party certificate I am using was one of the free email certificates supplied by Comodo, although ones I use for other purposes from StartSSL ( ) do not work either.
#IPHONE MUMBLE CERTIFICATE PC#
The PC client has no issues using the third party certificate to connect to the server. Both the PC and iOS clients can connect to the server using self-signed certificates made by the PC client, and the iOS client can connect using its own generated certificate if none is supplied. The iPad client seems to be unable to connect to servers with third party signed certificates.
#IPHONE MUMBLE CERTIFICATE WINDOWS 8#
Murmur 1.2.4 running on Windows 8 () with OpenSSL 1.0.1c. Windows 8 running Mumble 1.2.4 and Murmur 1.2.4 (from the standard windows installer, no modifications made to either) IPad 4th Gen with Retina Display running latest version of iOS
0 kommentar(er)
