You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The tool currently in the armory that uses RunspaceFactory to execute a PowerShell command to bypass AppLocker seems less compatible than powerspace.
In one of your article, John Guild discussed using sharpsh. He mentioned the need to adapt commands to the console format, which can introduce unnecessary complexity. PowerSpace, on the other hand, uses Windows-style argument parsing with the / convention. This simplifies command execution and reduces the chances of errors, making it more user-friendly, especially for those who are already familiar with Windows command-line conventions.
For instance, in Sliver, the current command structure requires passing arguments after --. With PowerSpace, this step is unnecessary because of the way arguments are parsed. Moreover, PowerSpace provides verbose debugging output, which helps in ensuring that commands are passed and executed correctly, offering better visibility into the process—this can be invaluable for troubleshooting and ensuring that everything runs smoothly. Of course, if you find having so much output annoying, I can modify this so that it only happens with a /d or /debug.
Additionally, I’ve integrated the necessary alias.json directly into the Sliver folder within the repository, making it Fork-ready.
It's mainly to see if I'm deleting this repository or if it might be of interest to you. Thank you for considering this suggestion.
Best regards,
The text was updated successfully, but these errors were encountered:
Hi maintainers 👋,
The tool currently in the armory that uses
RunspaceFactory
to execute a PowerShell command to bypass AppLocker seems less compatible thanpowerspace
.In one of your article, John Guild discussed using
sharpsh
. He mentioned the need to adapt commands to the console format, which can introduce unnecessary complexity.PowerSpace
, on the other hand, uses Windows-style argument parsing with the / convention. This simplifies command execution and reduces the chances of errors, making it more user-friendly, especially for those who are already familiar with Windows command-line conventions.For instance, in Sliver, the current command structure requires passing arguments after
--
. WithPowerSpace
, this step is unnecessary because of the way arguments are parsed. Moreover,PowerSpace
provides verbose debugging output, which helps in ensuring that commands are passed and executed correctly, offering better visibility into the process—this can be invaluable for troubleshooting and ensuring that everything runs smoothly. Of course, if you find having so much output annoying, I can modify this so that it only happens with a/d
or/debug
.Additionally, I’ve integrated the necessary alias.json directly into the Sliver folder within the repository, making it Fork-ready.
It's mainly to see if I'm deleting this repository or if it might be of interest to you. Thank you for considering this suggestion.
Best regards,
The text was updated successfully, but these errors were encountered: