question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Github Desktop not asking for self-signed certificate password

See original GitHub issue

Description

I have a git server with existing repositories on it and SSL verification with self-signed certificates. I can clone those repositories through git command line, but I’m unable to do the same from Github Desktop, as it gets stuck on an infinite loop cloning whatever repository I specify. I’ve been through all the issues related to this problem which I’ve been able to find searching, but none of them has helped me so far. Maybe there’s an issue saying password protected self-signed certificates are not yet supported, but I haven’t found anything related to it. If it is currently supported, it’s something strange that I can clone from cmd git but not from Github Desktop, isn’t it?

Version

  • GitHub Desktop: 1.1.0
  • Operating system: Windows 10

Steps to Reproduce

I don’t have steps to reproduce it. From cmd git I can use my server but not from Github Desktop.

Expected Behavior

From cmd git I can clone and manage all repositories without any kind of problem. I expected to do the same with Github Desktop.

Actual Behavior

Github Desktop gets stuck in an infinite loop saying it is cloning the desired repository, but nothing happens. It just creats the root folder for the git repository but does not download any repository files. It also does not prompt asking for user and password credentials as cmd git does.

Additional Information

This is my .gitconfig file (I’ve edited my personal information to publish this lines):

[credential]
	helper = manager
[user]
	name = My Name
	email = my.name@mycompany.com
[filter "lfs"]
	required = true
	clean = git-lfs clean -- %f
	smudge = git-lfs smudge -- %f
	process = git-lfs filter-process
[http]
	sslVerify = true
	sslBackend = openssl
	sslCAInfo = C:\\Certificates\\ca_chain.pem
	sslPath = C:\\Certificates\\
	sslCert = C:\\Certificates\\my.name.pem

Logs

2018-03-13T15:21:37.421Z - info: [ui] [AppStore] loading 0 repositories from store
2018-03-13T15:21:37.646Z - info: [ui] launching: 1.1.0 (Windows 10.0.16299)
2018-03-13T15:21:37.647Z - info: [ui] execPath: 'C:\Users\User\AppData\Local\GitHubDesktop\app-1.1.0\GitHubDesktop.exe'
2018-03-13T15:22:06.378Z - warn: [ui] fetchRepository: 'my.name/OpenLDAP' returned a 404
2018-03-13T15:22:06.380Z - info: [ui] [AppStore.getAccountForRemoteURL] found generic credentials for 'git' and 'my.name'

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Comments:6 (4 by maintainers)

github_iconTop GitHub Comments

2reactions
ghostcommented, Sep 30, 2020

Updating information on this issue as now I can use Github Desktop with a slight change in .gitconfig:

I have changed these lines in .gitconfig:

[http]
	sslVerify = true
	sslBackend = openssl
	sslCAInfo = C:\\Certificates\\ca_chain.pem
	sslPath = C:\\Certificates\\
	sslCert = C:\\Certificates\\my.name.pem

to these lines:

[http]
	sslVerify = true
	sslBackend = schannel

This just tells Git to use the Windows Certificate Store. After this change I’ve been able to clone, pull, push without any issues. Hope this helps anyone with the same or similar setup 😄

0reactions
billygriffincommented, Nov 14, 2018

@asegursa Thanks so much for the issue and explaining your setup. We haven’t heard from very many others that supporting something like this would be useful and your configuration seems to be relatively rare. I’m going to remove the future-proposal label to indicate that we don’t intend to support this, but we’re always open to revisiting if we hear from others that support for custom certificates with passphrases would be more broadly beneficial. Thanks again!

Read more comments on GitHub >

github_iconTop Results From Across the Web

Desktop Beta Cannot login to Github Enterprise server with a ...
Our Github Enterprise server uses a certificate issued from an internal root CA which is self-signed (not something we control).
Read more >
Self Signed Certificate Chain Error - Reversion #4821 - GitHub
Fatal error 'SSL certificate problem: self signed certificate in certificate chain' for openssl and 'CertGetCertificateChain trust error ...
Read more >
Enterprise self-signed/untrusted certificate support · Issue #671
It's not uncommon for GitHub Enterprise instances to run with a self-signed certificate or certificate signed by a non-authorative CA.
Read more >
SSL certificate problem: self signed certificate in certificate chain
I am unable to push to git. I see that there have been changes and I've been upgrading to catch up, but I'm...
Read more >
Cant clone from GitHub : SSL certificate problem: unable to ...
sslbackend set to openssl , which means GitHub Desktop isn't using the Windows certificate store. Running the command git config --global http.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found