Closed Grezzo closed 1 year ago
@Grezzo we are working at open-sourcing all of the fireeye packages currently. We are targetting to have them all released before the end of the year but until then it's kind of up to us to get them all fixed. I have noted all of these and they are on the chopping block :-)
Don't know if it's worth mentioning here, or a separate issue; however libraries.python2.fireeye is now also failing; Microsoft has pulled the vcpython2.7 download link used in that package.
hello, just thought I ask if the packages are still being worked on I am getting failures on the following:
Failures
@Grezzo we are working at open-sourcing all of the fireeye packages currently. We are targetting to have them all released before the end of the year but until then it's kind of up to us to get them all fixed. I have noted all of these and they are on the chopping block :-)
I made a new bug post before seeing this....I've added the links to the ones that i could find to maybe make it a little easier to update.
Hi all, we are releasing Commando 3.0 and with it, all of Commando-VM packages have been open-sourced to the https://github.com/mandiant/VM-Packages repo.
We currently have fixed versions of sharphound and mimikatz, but the other packages have not been put on the todo list yet. If you would like to see specific packages, please create an issue on https://github.com/mandiant/VM-Packages.
The following packages fail installation:
I assume orca and ruby2.devkit are not under your control. I wanted to try to fix the broken fireeye packages, but I can't find the source repository in order to update them and create a pull request. Is this something I can help with, or are those packages not community-updatable?