-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cannot run armory command #1826
Comments
I'm having same issue as well. |
Usually caused by internet connection problems, or Github has banned your IP from accessing the Github APIs for one reason or another. |
i have this probleme sliver > armory install all panic: runtime error: invalid memory address or nil pointer dereference goroutine 294 [running]: |
sliver > armory install all ? Install 21 aliases and 141 extensions? Yes goroutine 1 [running]: |
https://github.com/cobbr/Covenant/wiki/Installation-And-Startup check this out easy to get running and learn |
[] Fetching 1 armory index(es) ... done!
[] Fetching package information ... panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x10 pc=0xfba0a7]
goroutine 231 [running]:
github.com/bishopfox/sliver/client/command/armory.downloadRequest({0x0, 0x0, 0x0, 0xd18c2e2800, 0x0}, {0xc0013c2120, 0x5c}, 0xc00114eab1?)
github.com/bishopfox/sliver/client/command/armory/parsers.go:439 +0x167
github.com/bishopfox/sliver/client/command/armory.GithubArmoryPackageParser(0x17ea9e0?, 0xc000aa50e0, 0x1, {0x0, 0x0, 0x0, 0xd18c2e2800, 0x0})
github.com/bishopfox/sliver/client/command/armory/parsers.go:318 +0x30f
github.com/bishopfox/sliver/client/command/armory.fetchPackageSignature(0xc001012c70?, 0xa5ebe40, 0xc000aa50e0, {0x0, 0x0, 0x0, 0xd18c2e2800, 0x0})
github.com/bishopfox/sliver/client/command/armory/armory.go:487 +0x3f4
created by github.com/bishopfox/sliver/client/command/armory.fetchPackageSignatures in goroutine 1
github.com/bishopfox/sliver/client/command/armory/armory.go:445 +0x127
The text was updated successfully, but these errors were encountered: