Add support for encoded mode #508
Conversation
| * If we are in encoded mode, then send our data to | ||
| * the target in base64 encoded form. | ||
| */ | ||
| script_runner.on_stdin (Base64.encode (buf[:n])); |
There was a problem hiding this comment.
No need to encode it, post() has a data argument which supports binary data. It's passed to the message handler in the second argument. But we should improve the RPC API (built on top of send() + recv()) so it supports binary data in parameters and not only in the return value. The GumJS implementation can be found here. We could basically use a special marker, like ['frida:oob', offset, size], which specifies the offset into the data argument, and the size of the region.
There was a problem hiding this comment.
I think I had the same problem on output. Sending ansi control codes to the stdout. Is it possible for frida core to work as a dumb byte pump rather than dealing with strings?
There was a problem hiding this comment.
That's only a matter of returning an ArrayBuffer instead of a string.
There was a problem hiding this comment.
Can binary data only be sent/received by post and it's return value? Is there an ability to make an RPC to send bytes during the handling of the post? Or so they all have to be collated and sent by return?
|
Superseded by #525 |
Support sending base64 between the TTY and the script to prevent extended ascii sequences getting converted into multibyte UTF-8 characters.