Cloning encrypted Git repository does not work inside WSL
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- PR merge metrics
- PR metrics pending
Description
Created a tet repository with `git.exe` on Windows command line (`cmd.exe`), added and commited a test file to this repository. Working with this repository in Windows works without issues (add, commit, push, pull, clone, etc...), not so much inside WSL:
```
C:\tmp>"C:\Program Files\Git\bin\git.exe" clone keybase://private/rfgamaral/test-repository
Cloning into 'test-repository'...
Initializing Keybase... done.
Syncing with Keybase... done.
Counting: 211 bytes... done.
Cryptographic cloning: (100.00%) 211/211 bytes... done.
```
```
Ricardo@LP5J44QH2:/tmp$ git clone keybase://private/rfgamaral/test-repository
Cloning into 'test-repository'...
Initializing Keybase... done.
Syncing with Keybase... done.
Counting: 211 bytes... done.
Cryptographic cloning: (100.00%) 211/211 bytes... done.
fatal: bad object f4692747bbd26ca19b734eed456f13cd856b082b
fatal: remote did not send all necessary objects
```
my log id: 18c4e16951930d469f65bf1c
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the WSL command `git clone keybase://private/rfgamaral/test-repository` and compare it with the Windows `git.exe` clone shown in the report. Trace the clone path until the bad object error occurs; done means an encrypted repository clones successfully inside WSL without missing-object errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git
- Domain
- cli, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100