Closed daniruiz closed 1 year ago
@daniruiz Good recommendations. All in 4.2. Added a check isWsl() before running unixPath2Win. I test in WSL mostly, that's where that oversight came from. Second on monospaced. Added a isKali() check for eyewitness vs PhantomJS. Once Eyewitness is more broadly available I can scrap the countercase.
Perfect thank you! ;) I've updated the package and the latest 4.3 version is now in kali: https://pkg.kali.org/pkg/legion I've found other issues that I'll try to debug later, but I'm listing them here just in case you find a solution first:
With more time I'll open a MR or an issue with more information, but just to let you know for now.
Hello! I'm a kali package maintainer and recently I've been working on the update of Kali's legion package (https://gitlab.com/kalilinux/packages/legion). Right now I'm uploading the update for version 4.1 and I would like to know your view on the changes that I've made to make it work in our system. If you could test our package in Kali and confirm that everything is working as expected that would be great too.
One major issue that I've found with the new update is that the tool is trying to write to wrong folders or to the folder where legion is installed. In one case it was just due to a missing
expanduser
function, but the others where caused by the functionunixPath2Win
, which is used in multiple places overcontroller.py
. This function is returning paths with the backslash character which linux doesn't understand, so it creates local files with a super long filename with the route of the windows path (including backslashes). This later makes legion unable to find where it has stored these output files. Just removing these functions fixed the issue.Fix missing
expanduser
in auxiliary.pyRemove
unixPath2Win
calls in controller.py:Other changes that I added to kali's package:
These are not as important but I wanted to share the other modifications that I made to Kali's legion package. Maybe some of them can be merge to upstream code.