Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Decompiling the GPL violated Linux kernel using Evolutionary Algorithms

far.chickenkiller.com

Post reply on HN
Print view View original

11–16 of 16 posts

Re: Decompiling the GPL violated Linux kernel using Evolutionary Algorithms

#11

Post by farooqkz »

synctext wrote: post #5

This is a difficult project. The blog post seems to hint at reasonable feasibility, this stuff is hard! We build a less ambitious tool in the university lab: "ASTANA: Practical String Deobfuscation for Android Applications Using Program Slicing" [0]. Would advise to first read the reverse engineering related work. Genetic programming is just a technique best used when everything else has failed :-) [0] https://arxiv.…

Thanks for the hints. Of course, it's very very difficult. But one thing I think you missed, is that I'm proposing a "byte equivalent decompilation". And after that, we should go into reading the code readable and understandable.

If we could create a program doing all this, automatically or semi-automatically, it will be great-great because then not releasing the kernel code doesn't matter. I believe if enough effort and time is put into it, there is a good chance we could see such a thing in like 5-7 years.

After that, we might be able to target the binary blobs, the propriety firmwares. Those might have some legal issue, of course. But as long as it is used only to write a FOSS alternative, that probably won't be an issue, I think.

Re: Decompiling the GPL violated Linux kernel using Evolutionary Algorithms

#12

Post by ACCount37 »

farooqkz wrote: post #10
ACCount37 wrote: post #4

I thought this would be an actual process, not a blog post with idle musings.

I wanted to append [idea] but it became too long. I think there should be balance "musings" and actual work. I learned very valuable lessons in my wakegp research. Even though I haven't completed it. If the one doing this research would be me, I would go for no actual work as long as I can. And when I start to do the work, I should do as little as I can and move very slowly. Like the saying "When you move slowly, you…

That sounds like a load of pseudo-profound bullshit to me.

And this little idea you've described? It's exactly the kind of thing where both the fundamental issues and the specific implementation details would conspire to fuck you over hard at every single turn.

If you actually tried to implement that idea of yours, you'd fail a lot, and maybe you'd learn something, and then it would be worth writing a post about that. About what you tried, what didn't work, what worked a little bit but not really.

As is? You picked a domain where ideas are easy but implementation is hilariously hard, and then you had an idea but implemented nothing. You never tried anything and you never learned anything. The value is nil.

Re: Decompiling the GPL violated Linux kernel using Evolutionary Algorithms

#13

Post by farooqkz »

ACCount37 wrote: post #12
farooqkz wrote: post #10

Earlier quoted context omitted.

I wanted to append [idea] but it became too long. I think there should be balance "musings" and actual work. I learned very valuable lessons in my wakegp research. Even though I haven't completed it. If the one doing this research would be me, I would go for no actual work as long as I can. And when I start to do the work, I should do as little as I can and move very slowly. Like the saying "When you move slowly, you…

That sounds like a load of pseudo-profound bullshit to me. And this little idea you've described? It's exactly the kind of thing where both the fundamental issues and the specific implementation details would conspire to fuck you over hard at every single turn. If you actually tried to implement that idea of yours, you'd fail a lot, and maybe you'd learn something, and then it would be worth writing a post about that…

I don't welcome rudeness towards people. Not me nor anyone else.

Re: Decompiling the GPL violated Linux kernel using Evolutionary Algorithms

#14

Post by farooqkz »

synctext wrote: post #5

This is a difficult project. The blog post seems to hint at reasonable feasibility, this stuff is hard! We build a less ambitious tool in the university lab: "ASTANA: Practical String Deobfuscation for Android Applications Using Program Slicing" [0]. Would advise to first read the reverse engineering related work. Genetic programming is just a technique best used when everything else has failed :-) [0] https://arxiv.…

I've read the abstract of your article. I am not much in the field of decompilers. Let alone deobfuscation. It's even hard for me to type it :))

I think it is probably a safe assumption that the kernel binary found on Android devices is not obfuscated. Tho I probably need more research to confirm this.

Re: Decompiling the GPL violated Linux kernel using Evolutionary Algorithms

#15

Post by drivingmenuts »

While you might be able to produce code that would re-compile into a binary resembling the original binary, how would you be able to generate the same code that was compiled to produce the original binary? Seems like there would be a significant difference between the actual original code and the decompiled version - enough that it could not be used to prove license violation.

Re: Decompiling the GPL violated Linux kernel using Evolutionary Algorithms

#16

Post by farooqkz »

drivingmenuts wrote: post #15

While you might be able to produce code that would re-compile into a binary resembling the original binary, how would you be able to generate the same code that was compiled to produce the original binary? Seems like there would be a significant difference between the actual original code and the decompiled version - enough that it could not be used to prove license violation.

The goal is not proving anything. They don't release the source code, so we try to get it ourselves. Then make the process of mainlining devices easier.
Post reply on HN