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
{{ message }}
This repository has been archived by the owner on Apr 25, 2019. It is now read-only.
so the most recent update to the nethunter app for what ever reason does not save the configuration for powersploit or does not load it at run time because upon exiting and restarting the app the fields are not repopulated.
The text was updated successfully, but these errors were encountered:
I'm debating if this is really a bug or not because we previously would save the configuration into the powershell exploit itself. However, because we have to pass the shellcode now separate we don't save those settings in the ps1 file. Before regex would be used in the exploit to get those settings but we don't do that anymore.
I think it might be more of an enhancement at this point but I will let others chime in.
Why not have the shell code saved to a file when generated then read and
piped out to invoke shellcode? I bring this up because on a red team
engagement you don't always have time to sit around and wait for
shellcode to be generated, especially if you are compromising multiple
systems in a row.
On 01/28/2016 07:01 PM, binkybear wrote:
I'm debating if this is really a bug or not because we previously
would save the configuration into the powershell exploit itself.
However, because we have to pass the shellcode now separate we don't
save those settings in the ps1 file. Before regex would be used in the
exploit to get those settings but we don't do that anymore.
I think it might be more of an enhancement at this point but I will
let others chime in.
—
Reply to this email directly or view it on GitHub #121 (comment).
so the most recent update to the nethunter app for what ever reason does not save the configuration for powersploit or does not load it at run time because upon exiting and restarting the app the fields are not repopulated.
The text was updated successfully, but these errors were encountered: