Update psexec.md

bug/bundler_fix
wchen-r7 2016-03-01 19:06:40 -06:00
parent f27d24fd60
commit 876a5b55f9
1 changed files with 5 additions and 5 deletions

View File

@ -116,17 +116,17 @@ otherwise it uses the natvie upload. Each target is explained below.
**Powershell Target**
The Powershell target forces the psexec module to run a Powershell command with a payload embedded
in it. Since this approach does not leave anything on disk, this is a very powerful way to evade
antivirus, however, older Windows machines might not support Powershell by default.
in it. Since this approach does not leave anything on disk, it is a very powerful way to evade
antivirus. However, older Windows machines might not support Powershell by default.
Ideally, you probably want to use the Automatic target setting instead of this since it will check
if Powershell is possible first.
**Native Upload Target**
By default, the Native target will attempt to upload the payload (executable) to SYSTEM32, and then
execute it with psexec. This approach is rather reliable, but has a high chance of getting caught
by antivirus on the target.
By default, the Native target will attempt to upload the payload (executable) to SYSTEM32
(modifiable with the SHARE datastore option) , and then execute it with psexec. This approach is
rather reliable, but has a high chance of getting caught by antivirus on the target.
**MOF Upload Target**