Re:Movfuscator – Single instruction C compiler
by Legogris on Thursday January 24, 2019 @03:00PM
(#18992350)
Considering that the floating point library is big enough to be disabled by default tells me you might run out of disk space compiling a single application.
That being said, if this can increase difficulty of sidechannel attacks and branch prediction, maybe it'd actually make sense for very isolated parts of some services.
Re:Movfuscator – Single instruction C compiler
by odorousrex on Thursday January 24, 2019 @03:21PM
(#18992523)
>That being said, if this can increase difficulty of sidechannel attacks and branch prediction, maybe it'd actually make sense for very isolated parts of some services.
I agree, I can see how it certain special circumstances/services this could be very useful.
However, I still expect someone to compile Quake with it by the end of the year.
Re:Movfuscator – Single instruction C compiler
by simcop2387 on Thursday January 24, 2019 @03:39PM
(#18992691)
They've apparently done DOOM already, and it's hours per frame. I don't want to think what Quake would be like.
Re:Movfuscator – Single instruction C compiler
by acheron on Thursday January 24, 2019 @02:57PM
(#18992322)
To be clear, I (the HN submitter) have nothing to do with this, I just found it and thought it was great.
Re:Movfuscator – Single instruction C compiler
by kbenson on Thursday January 24, 2019 @03:02PM
(#18992372)
From the example images of original and obfuscated assembly, there's seems to be about a sixfold increase in the number of instructions (for that example, at least), so I imagine you'll see a similar binary size increase.
I wonder what the final binary sizes are in comparison to normal GCC compilation, as well as execution speed.
I can't believe you made a floating point emulator just for this as well! Quite impressed.