Using native libraries with non-native binaries (usercorn)

[Manouchehri]

Think it would be possible to use something like this to get non-native binaries running with native libraries?

https://github.com/lunixbochs/usercorn

[zardus]

I don't think usercorn supports running binaries with shared objects of different architectures... I guess it could be done (by translating the argument registers from one unicorn instance, under one arch, to another instance, under another arch, and mapping their memories to be the same), but I'm 99% sure this isn't functionality that usercorn supports right now. And it'd probably be easier to do that in plain angr, because the calling convention helpers would at least help a bit with the job of translating the arguments. There'll be plenty of other issues due to assumptions of a single architecture across the entire binary, though.

But what would be the practical purpose of this capability?

[Manouchehri]

Hmm, I thought you could do it..

Going native for libraries will save a ton of time in angr, no?

[Manouchehri]

Pinging @lunixbochs, what's your opinion?

lunixbochs/usercorn#67 (comment)

[rhelmot]

my opinion is that this would be an absurd amount of effort for very little
payoff. We're working on a unicorn engine plugin for simuvex right now, and
when that's done it'll let you execute any code that runs on concrete
values - current tests show a hundreds-of-thousands of times speedup over
normal symbolic execution w/ concrete values. If you have a case where
something is big enough for the difference between unicorn-native and
unicorn-emulated to be meaningful, then you're at a large enough scale that
you need to be thinking about a more clever solution to your problem than
"just execute everything".

On Mon, May 23, 2016 at 5:08 PM, David Manouchehri <notifications@github.com

wrote:

Pinging @lunixbochs https://github.com/lunixbochs, what's your opinion?

lunixbochs/usercorn#67 (comment)
lunixbochs/usercorn#67 (comment)

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#22 (comment)