mandiant / commando-vm

Complete Mandiant Offensive VM (Commando VM), a fully customizable Windows-based pentesting virtual machine distribution. commandovm@mandiant.com
https://www.mandiant.com/resources/blog/commando-vm-windows-offensive-distribution
Apache License 2.0
6.94k stars 1.3k forks source link

lonelypotato.fireeye Install Error #174

Closed syth3 closed 3 years ago

syth3 commented 4 years ago

Bug Description

When attempting to install the lonelypotato.fireeye package from Chocolatey, I receive this error: ERROR: The remote file either doesn't exist, is unauthorized, or is forbidden for url 'https://github.com/decoder-it/lonelypotato/archive/1845a19662856abd1e3f84f3ebdb9c029e93ab8d.zip'. Exception calling "GetResponse" with "0" argument(s): "The remote server returned an error: (404) Not Found." Here is my Chocolatey log relating to this install: lonelypotato.fireeye Install Log.txt

Steps To Reproduce

  1. Run the following command in an elevated PowerShell prompt: cinst -y lonelypotato.fireeye

Screenshots

lonelypotato fireeye Install Screenshot

Version

day1player commented 4 years ago

@syth3 this looks like the file may be being blocked by a proxy of sorts. Can you confirm you are not installing this behind a firewall/proxy that may be interfering?

syth3 commented 4 years ago

@day1player I am pretty certain I am not installing it behind a firewall/proxy that is prohibiting it. My current setup is a Windows 10 computer running Commando VM inside of VMWare Workstation. The Commando VM is configured to use NAT networking. My Windows 10 host computer is connected directly to my ISP-given router running their default firewall. Because of this, the only firewall/proxy that seem to be of interest are any Windows 10 firewalls running on either the Commando VM or my host machine, or the default firewall on my router. Additionally, I have tested installing this package in a different VM on a different network entirely and face the same issues. Finally, when I visit the url listed in the error message in my web browser, I also receive a HTTP 404.

day1player commented 4 years ago

Right on it looks like that was definitely removed then. We will have to update the package. I will let you know when it is done, thank you!

syth3 commented 4 years ago

Sure thing. Thanks for the help!

day1player commented 3 years ago

fixed with june update #262