| Description | Yesterday after testing out a script I was writing to download Kali packages via git.kali.org, I suddenly lost the ability to clone/pull any tools from the repository. After ruling out any network errors or possible issues on my end, I asked several colleagues and attempted to connect using various means from other networks. I tried connecting through a VPN to several locations in the US, asked friends and colleagues from other locations (3 in US, 1 in Netherlands) to attempt to clone something, and none have been able to.
We all get the same error "Connection reset by peer" |
|---|
| Steps To Reproduce | Whether it is through my script or calling git clone directly from command line, the error is the same.
Direct git clone/pull:
git clone -v git://git.kali.org/packages/commix.git
| Cloning into 'commix'...
| fatal: read error: Connection reset by peer
My script's stack trace:
git.exc.GitCommandError: Cmd('git') failed due to: exit code(128)
|cmdline: git clone -v git://git.kali.org/packages/commix.git /tmp/commix
|stderr: 'Cloning into '/tmp/commix'...
|fatal: read error: Connection reset by peer |
|---|
| Additional Information | Essentially, the error indicates that git.kali.org is not responding to any git requests and I am unable to clone/pull any packages. I noticed that in Kali news there is a new release and that several changes have occurred in how Kali packages work when using Advanced Packaging Tool with the release of kali-bleeding-edge.
I'm mostly curious if the paths have changed to clone repositories from git.kali.org or if something actually did indeed break on your guys' end. It doesn't seem likely that the git repos would just suddenly stop working, but if the paths were changed, that would make sense. |
|---|
related to
child of
duplicate of
