desktop: The revocation function is unable to check revocation for the certificate.
Description
I am running behind a corporation that self-signs its certificates, which means that I get this issue when I try to push any changes.
fatal: unable to access 'https://github.com/glenndevenish/[repo]/': schannel: next InitializeSecurityContext failed: Unknown error (0x80092012) - The revocation function was unable to check revocation for the certificate.
Version
GitHub Desktop version: 0.7.2
OS version: Microsoft Windows [Version 10.0.10586]
Steps to Reproduce
(You will probably be unable to reproduce since you have to be in the corporation, although any self-signing corp. might have the same issue)
- Click publish branch
- Error message pops up.
Expected behavior: Update to occur successfully
Actual behavior: Repo was created, but no files were created.
Reproduces how often: Every time.
Logs
2017-08-15T13:38:44.759Z - info: [ui] Executing fetch: git -c credential.helper= fetch --progress --prune origin (took 1.196s)
2017-08-15T13:38:44.761Z - error: [ui] `git -c credential.helper= fetch --progress --prune origin` exited with an unexpected code: 128.
fatal: unable to access 'https://github.com/glenndevenish/[repo].git/': schannel: next InitializeSecurityContext failed: Unknown error (0x80092012) - The revocation function was unable to check revocation for the certificate.
Additional Information
None.
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Reactions: 5
- Comments: 19 (5 by maintainers)
Copy cert path from configuration git
Add to global configuration
git config --global http.sslverify “false” this statement resolved issue
@glenndevenish thank you for your issue!
We haven’t gotten a response to the questions in our comment here. With only the information that is currently in the issue, we don’t have enough information to take action. I’m going to close this but don’t hesitate to reach out if you have or find the answers we need, we’ll be happy to reopen the issue.
This Worked for me also, thanks.
@robertmryan you can verify your connections using openssl to see what certificate chain it does find:
@shiftkey Okay, good to know. Git for Windows wasn’t installed by default, so that needed sorting.
I used
git config http.sslCAInfo /path/to/certificate.crtwith the certificate I’d saved from the Windows key manager.@shiftkey Thanks, that identified the offending certificate, namely a Kaspersky cert installed as part of their suite, and once I removed that and rebooted, I can now use git desktop. Thanks!
@shiftkey Sorry, I wasn’t aware of your comment, for some reason! I managed to solve it myself though, by: