I have installed Charles Root Certificate on my iOS device and my MacBook. However, when i use iPhone proxing by Charles, Charles fails to get HTTPS requests. It shows that
SSLHandshake: Received fatal alert: unknown_ca
My Charles version is 4.0.2 and I have installed certificate on my mac and trusted.
My iOS version is 10.3.1 and I have also installed certificate on iphone.
Can anyone help my on this? Thanks a lot.
iOS 10.3+ introduced a new setting to grant permission for certificates. Since you have the Charles certificate installed, then all you need to do is go to Settings > General > About > Certificate Trust Settings > Toggle the cert to on. Hope this helps you.
Related
I use the cool feature in Apple Shortcut to request some HTTP REST commands of my Smarthome via my Webserver. I use an apache2 with Lets Encrypt certificates.
This is working fine on my iPad and on my iPhone but unfortunately not on my Apple Watch. I get always: The certificate for this server is invalid. You might connecting to a server that is pretending to be "my.domain.com" which could put your confidential information at risk.
I use the "URL" command in Apple shortcuts with "Network".
I am not sure how to handle this. On all my Apple devices the short cuts are working but not on the Apple Watch. I restarted the watch already.
Thanks
I found the solution on myself.
First I tested the certificate with https://ssllabs.com from Qualys. This site tests the certificate. The result showed that the chainfile will not be downloaded from the apache2. The mistake was that I forgot to add the "SSLCertificateChainFile" to the configuration.
Now my apache2 SSL configuration is rate A+ and the shortcuts are working again with the Apple Watch.
Why the error only occured on the apple watch and not on the other apple devices too I don't know.
Thanks
On Charles mac app, if I go to
Help > SSL Proxying > Install Charles Root Certificate on iOS
Simulators
and then run any Simulator from Xcode I don't see Charles certificates installed on simulator.
I am using Charles v4.6.1. This was working fine on iOS Simulator 14.4. If you have any solutions please let me know.
It's a bug from Charles Proxy. You should wait until Charles Proxy fixes it.
To work around, you might manually export the certificate from Help Menu -> SSL Proxying -> Save Charles Proxy Root Certificate.
Then drag the file to iOS Simulator. Then trusting it by Going to Settings app -> General -> About -> Certificate Trust Settings.
Or You can install and trust the certificate by using simctl CLI
xcrun simctl keychain booted add-root-cert <your_certificate>
If you prefer automation work, do it with one-click, you might checkout Proxyman, which is a modern version of Charles Proxy.
It also fully supports Xcode 12.5, iOS 14.5 Simulators, Big Sur, and M1 Macbook.
Disclaimer: I develop Proxyman app. Hope that it helps you.
You can try this (for any new simulator). This process still work with simulator 14.5 and iOS 15
Open charles and configure it as its Proxy. In Charles see that, Proxy-> macOS Proxy is enabled.
From the iDevice, open https://chls.pro/ssl with Safari Browser.
It will ask to download the certificate. Just download it. The certificate will be ready to be installed
Open Settings/General/Profile/Download Profile to install the certificate (Profile link in settings appear only after downloading profile from https://chls.pro/ssl). In iOS 15, the profile can be found under Settings/General/Device Management.
Open Settings/General/About/Certificate Trust Settings to accept the newly installed certificate
No need for a workaround anymore.
Just update Charles to 4.6.2 version.
You can download it from the link above:
https://www.charlesproxy.com/download/
For some reason, Firefox today started issuing warnings about the SSL certificates on our web applications, but supplies very little information. Everything works fine in IE/Edge and Chrome. The application is at https://ps.ecco.com
How can I find out more about what's going wrong with the certificates and how do I solve the issue?
I'm facing an issue with self-signed certificate in Windows Phone 8 app. I have installed the certificate (.p7b) manually and it works fine when I browse through the site in IEMobile.
But when I visit the same, using the WebBrowser control in my hybrid app, The certificate error still shows and can't be ignored, even after tapping Continue. Isn't the Certificate installed System-wide or is it just for IE?
I have referred many links regarding this but in vain. Any help would be jighly appreciated. Thank you.
I had the same issue, and it turned out to be a hostname mismatch between what the certificate contained and the address I was using to connect to the server. If those match, and you install the P7B file on the Windows Phone device, then you should no longer see certificate warnings.
For the full details of my issues and solution, see this thread on MSDN.
I'm trying to minimize the cost of code-signing certificates necessary to develop a program for Mac OS X and Windows. As far as I can tell, I can't use a 3rd party certificate to sign my OS X program and have it get past GateKeeper, as indicated here.
Can I go the other way and use an Apple Developer certificate to sign the Windows version of my program?
Also related: Non-Apple Issued Code Signing Certificate: Can it Work with Mac OS 10.8 Gatekeeper?
Had the same idea some time ago. But I don't think it's possible, because the Apple Developer Certificate is verified (signed) by Apple and I don't think that the Apple Root Certificate is installed on average Windows machines.
Hi Joe LTNS I check the status of this question every time my Comodo CS certificate comes up for renewal, because hassle/money vs Apple's
Alas, Apple's CA still not in Windows golden list AFAIK. I checked Apple Software Update under Win10 and its cert issuer is Verisign.
OT Not a cert expert here, but if Apple concocted an intermediate cert that both the CA and Apple could vouch/revoke, not a few Windows devs would pony up for Apple's $100 Dev program for that su-weet 5 year non-MAS codesign cert (and probably dabble in App Store/ios development as a bonus)
Here is a detailed article about it: http://luminaryapps.com/blog/code-signing-and-packaging-windows-apps-on-a-mac/ and more generally about code-signing Windows apps on a Mac. I quote:
Now you need to get a Windows developer certificate. Unfortunately you can't use your Apple certificate (well, actually you can, but it doesn't help because Apple isn't a certificate authority that Windows recognizes). Here is a list of root certificate authorities recognized by Windows.
So this seems to confirm the other answers.