[GH-ISSUE #232] Invalid Certificate in macOS 10.12 #227

Open
opened 2026-03-03 19:16:25 +03:00 by kerem · 6 comments
Owner

Originally created by @NghiaTranUIT on GitHub (Aug 2, 2019).
Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/232

Originally assigned to: @NghiaTranUIT on GitHub.

🐶 Brief

Few users on macOS 10.12 reports that the Certificate is trusted, but the app doesn't recognize it appropriately.

👑 Criteria

  • Check the Certificate detector on macOS 10.12
  • Should work
Originally created by @NghiaTranUIT on GitHub (Aug 2, 2019). Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/232 Originally assigned to: @NghiaTranUIT on GitHub. ## 🐶 Brief Few users on macOS 10.12 reports that the Certificate is trusted, but the app doesn't recognize it appropriately. ## 👑 Criteria - [x] Check the Certificate detector on macOS 10.12 - [x] Should work
Author
Owner

@NghiaTranUIT commented on GitHub (Aug 2, 2019):

🤯 Changelogs

  • Fix how the Proxyman detect Trusted Certificate on macOS 10.12
<!-- gh-comment-id:517536343 --> @NghiaTranUIT commented on GitHub (Aug 2, 2019): ## 🤯 Changelogs - [x] Fix how the Proxyman detect Trusted Certificate on macOS 10.12
Author
Owner

@ivan7wl commented on GitHub (Feb 19, 2020):

This issue still happens on my macOS 10.12.4 and Proxyman 1.16.0 (11600).

  1. Open certificate setup guide window, install using the automatic way
  2. Close and reopen the guide window, cannot detect the installed certificate
  3. Install certificate again, and open Keychain.app, there are 2 Proxyman CA's in system keychain, one is called "Proxyman CA (19 2æ%C2%9C%C2%88 2020, [computer-name].lan)", the other "Proxyman CA (19 2æ%C2%9C%C2%88 2020, [computer-name].local)"

[computer-name] is the string of my computer name

<!-- gh-comment-id:588021308 --> @ivan7wl commented on GitHub (Feb 19, 2020): This issue still happens on my macOS 10.12.4 and Proxyman 1.16.0 (11600). 1. Open certificate setup guide window, install using the automatic way 2. Close and reopen the guide window, cannot detect the installed certificate 3. Install certificate again, and open Keychain.app, there are 2 Proxyman CA's in system keychain, one is called "Proxyman CA (19 2æ%C2%9C%C2%88 2020, [computer-name].lan)", the other "Proxyman CA (19 2æ%C2%9C%C2%88 2020, [computer-name].local)" [computer-name] is the string of my computer name
Author
Owner

@ivan7wl commented on GitHub (Feb 19, 2020):

This issue still happens on my macOS 10.12.4 and Proxyman 1.16.0 (11600).

  1. Open certificate setup guide window, install using the automatic way
  2. Close and reopen the guide window, cannot detect the installed certificate
  3. Install certificate again, and open Keychain.app, there are 2 Proxyman CA's in system keychain, one is called "Proxyman CA (19 2æ%C2%9C%C2%88 2020, [computer-name].lan)", the other "Proxyman CA (19 2æ%C2%9C%C2%88 2020, [computer-name].local)"

[computer-name] is the string of my computer name

Seems like it's the CA name string problem, I switch system language and locale to US, and install CA, the detection works. The date part in CA name is "19 Feb 2020"

<!-- gh-comment-id:588023595 --> @ivan7wl commented on GitHub (Feb 19, 2020): > This issue still happens on my macOS 10.12.4 and Proxyman 1.16.0 (11600). > > 1. Open certificate setup guide window, install using the automatic way > 2. Close and reopen the guide window, cannot detect the installed certificate > 3. Install certificate again, and open Keychain.app, there are 2 Proxyman CA's in system keychain, one is called "Proxyman CA (19 2æ%C2%9C%C2%88 2020, [computer-name].lan)", the other "Proxyman CA (19 2æ%C2%9C%C2%88 2020, [computer-name].local)" > > [computer-name] is the string of my computer name Seems like it's the CA name string problem, I switch system language and locale to US, and install CA, the detection works. The date part in CA name is "19 Feb 2020"
Author
Owner

@NghiaTranUIT commented on GitHub (Feb 19, 2020):

Thank for the report @ivan7wl. It looks like the Date part is localized when storing into the KeyChain. As a result, Proxyman doesn't detect properly.

I will fix it in next release 👍

<!-- gh-comment-id:588058753 --> @NghiaTranUIT commented on GitHub (Feb 19, 2020): Thank for the report @ivan7wl. It looks like the Date part is localized when storing into the KeyChain. As a result, Proxyman doesn't detect properly. I will fix it in next release 👍
Author
Owner

@NghiaTranUIT commented on GitHub (Mar 2, 2020):

All done 🌮
BETA: https://proxyman.s3.us-east-2.amazonaws.com/beta/Proxyman_1.17.1_Could_not_install_Certificate.dmg

Changelog

  • Force US as a default local when generating the name of Proxyman Certificate because macOS Keychain couldn't store non-English characters.
<!-- gh-comment-id:593216997 --> @NghiaTranUIT commented on GitHub (Mar 2, 2020): All done 🌮 BETA: https://proxyman.s3.us-east-2.amazonaws.com/beta/Proxyman_1.17.1_Could_not_install_Certificate.dmg ## Changelog - Force US as a default local when generating the name of Proxyman Certificate because macOS Keychain couldn't store non-English characters.
Author
Owner

@NghiaTranUIT commented on GitHub (Mar 2, 2020):

@ivan7wl let check it out 🙌

<!-- gh-comment-id:593217040 --> @NghiaTranUIT commented on GitHub (Mar 2, 2020): @ivan7wl let check it out 🙌
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/Proxyman#227
No description provided.