> ..what Addressing Modes are.
I'd say, it's only about parsing the syntax.
The registers ( ds, cs , .. ), depending on the architecture,
have to be stored anyways.
Furthermore, I didn't get so close yet,
but the MIPS architecture/assembly seems to be a good target as intermediate language between c and perl.
(according to schmorp, who chose the architecture cause it's simplicity for his emulator
http://blog.schmorp.de/2015-07-01-emulating-linux-mips-in-perl-3.html)
Oh, and I did find the movfuscator,
which "compiles programs into "mov" instructions, and only "mov" instructions. Arithmetic, comparisons, jumps, function calls, and everything else a program needs are all performed through mov operations; there is no self-modifying code, no transport-triggered calculation, and no other form of non-mov cheating."
:)) haven't got the thing to compile yet.
And I can't imagine yet, how this should work at all.
But this would not only solve the problem of addressing the pseudo ram,
it might render the resulting code close to undebuggable.
As long as there is no tool, which translates back into "normal" code.
When this is possible at all.
| [reply] |
| [reply] |
> ... but this doesn't matter much because your approach(es) are far away from what I would ever consider. :)
;) That's close to challenging me.
Admittedly, the whole approach is not exactly, what I'd consider good programming practice.
But since I've got a special goal, this might justify the .special. tools.
And an assembly interpreter could be of some use; for debugging, e.g.
Oh, about reverse engineering and the obfuscator,
youtube: REcon 2015 - The movfuscator (Christopher Domas) 33m20s
--nope. :)
There are a few parts, the password hashing, salting and storage to be exact, where this is exactly what I need.
I still don't really get, how a program consisting of only mov instructions can work.
But this seems perfect.
Albeit I again have to reread the encryption algorithms now, I must find a way to separate the "secret" passphrase from the rest of the algorithm.
Movfusculating the whole enc-/decryption algorithm might be a tiny little bit hungry for resources.
Even this is great for a cryptographic tool. But the process should finish within, say, a few minutes..
| [reply] |