github / github/app

Allow configuring certificate revocation checks for GitHub App marketplace plugin installation

Open
#3,852 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

triage
Dominant language
No language data
Stars
2.1k
Forks
157
PR merge metrics
No merged PRs in 30d

Description

Feature summary

Provide an option to control certificate revocation checking when GitHub App installs plugins from GitHub Marketplace repositories. This would help enterprise environments where TLS inspection or corporate certificate authorities prevent successful revocation verification.

What problem are you trying to solve?

Failed to install plugin
Failed to fetch marketplace: Failed to fetch GitHub marketplace github/copilot-plugins: Command failed: git clone --depth 1 --progress https://github.com/github/copilot-plugins.git C:\Users\test\AppData\Local\copilot\marketplaces\github-copilot-plugins
Cloning into 'C:\Users\test\AppData\Local\copilot\marketplaces\github-copilot-plugins'...
fatal: unable to access 'https://github.com/github/copilot-plugins.git/': schannel: next InitializeSecurityContext failed: CRYPT_E_NO_REVOCATION_CHECK (0x80092012)

Proposed solution

Add one of the following options: 1. Respect local Git certificate settings (for example http.schannelCheckRevoke) 2. Allow configuration of revocation checking behavior in the application settings 3. Provide an enterprise policy to control certificate validation during marketplace plugin downloads Default behavior can remain secure, while allowing administrators to support environments with non-standard PKI infrastructure.

Workflow impact

The repository itself is reachable and GitHub services are available.

The failure occurs because Windows Schannel cannot complete certificate revocation validation for certificates issued by corporate security solutions (for example TLS inspection proxies, Global Secure Access, enterprise PKI, etc.).

Currently there appears to be no way to:

Disable revocation checking for marketplace downloads
Configure an alternative certificate validation mode
Use existing Git settings related to Schannel revocation behavior

As a result, plugin installation is blocked in affected enterprise environments even though network connectivity and certificate trust are otherwise valid.

Installation context
Image
Additional context

The issue occurs only when certificates issued by Microsoft Global Secure Access are present.

GitHub Marketplace access is available and network connectivity works correctly.

The failure is caused by Windows Schannel revocation validation returning:

CRYPT_E_NO_REVOCATION_CHECK (0x80092012)

Other Git operations can be made to work by disabling revocation checks through Git configuration, but GitHub App marketplace installation currently does not provide a similar option.

Image

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the marketplace plugin installation flow that invokes git clone, and reproduce the Windows Schannel error described in the issue. Review whether local Git certificate settings are used during marketplace downloads, then determine how an application setting or enterprise policy could control revocation behavior. Done means affected installations can proceed with the configured behavior while the secure default remains unchanged.

Written by the indexing model from the issue text.

Assessment

Tech stack
git, github
Domain
desktop, security
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.