This allows you to encode, decode or hash text.
Add New Tab - Adds a new tab to the dialog.
Remove Selected Tab - Removes the selected (or current) tab from the dialog.
Add Output Panel to Current Tab - Adds an output panel to the current tab.<<???>> to PDw/Pz8+Pg== while Base64URL will convert it to PDw_Pz8-Pg.
Açores would be encoded as %u0041%u00e7%u006f%u0072%u0065%u0073.
"piñata" would be encoded as "piñata".
<script> would be encoded as <script>
"2¢" would be encoded as \"2\uFFE0\".
%u0041%u00e7%u006f%u0072%u0065%u0073 would be decoded as Açores.
SOS SOS would be encoded as ... --- .../... --- ....
"piñata" would be decoded as "piñata".
\"2\uFFE0\" would be decoded as "2¢".
... --- .../... --- ... would be encoded as SOS SOS.
EncodeDecodeResult objects as indicated by the templates. However,
in the event that users aren't careful in doing so will return other data types leveraging their toString() implementation (which may or may not be useful/obvious at first glance).
Tĥïŝ ĩš â fůňķŷ Šťŕĭńġ: fi. étrange. becomes This is a funky String: fi. etrange..>br>鸟儿 becomes an empty string (all characters are dropped).
printf "dir"| iconv -t UTF-16LE | base64 -w 0 -
$command = 'dir'
$bytes = [System.Text.Encoding]::Unicode.GetBytes($command)
$encodedCommand = [Convert]::ToBase64String($bytes)
echo $encodedCommand
ZABpAHIA.
Which can be leveraged via something like the following (where $encodedCommand is set to the encoded value ZABpAHIA):
powershell -exec bypass -enc $encodedCommand
| Tools menu 'Encode/Decode/Hash...' item | |
| Many text areas such as the Output tab, Scripts console, Request and Response panels via 'Encode/Decode/Hash...' right click menu item |