Suddenly getting NET::ERR_CERT_COMMON_NAME_INVALID on Chrome for SSL sites
- Dominant language
- JavaScript
- Stars
- 7.9k
- Forks
- 1.2k
- PR merge metrics
- No merged PRs in 30d
Description
Plese fill the template when you reporting a new issue, thanks!
#### Which platform are you running AnyProxy
Mac
#### The version of the AnyProxy
3.10.4
So anyproxy was working fine until Chrome 58. Now suddenly I get this error when browsing HTTPS sites.
I think it is related to this: https://www.chromestatus.com/feature/4981025180483584 https://alexanderzeitler.com/articles/Fixing-Chrome-missing_subjectAltName-selfsigned-cert-openssl/
Is there any known way around this for anyproxy?
Thanks!
Contributor guide
No contributing guide indexed for this repository
Research direction
No source file or test is named. Start by reproducing the Chrome 58 HTTPS failure on macOS with AnyProxy 3.10.4, then trace the HTTPS certificate-generation entry point and review the linked Chrome and OpenSSL references. Done means HTTPS sites no longer produce NET::ERR_CERT_COMMON_NAME_INVALID.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- networking, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100