Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> AFAIK it's software RE work, and nothing done in the console hacking scenes is truly cleanroom at all

There's a wide gradient of how much effort people put into reverse engineering consoles in a legal way vs. just copying code straight from their decompiler and slapping an open source license on it. libogc is very much on the "didn't even try" side of that gradient, it's been known since pretty much forever, and even their documentation is straight up copied from Nintendo's SDKs for part of their libraries.

What's new here is discovering that even the parts people thought were developed "fresh" and not just straight-up asm2c'd from Nintendo are actually stolen from other open source projects in a way that tries to conceal the origin of the code.

Whether you'll find that "more morally reprehensible" or not will largely depend on your personal morals, but clearly for some people that seems to be the case...



Yes, libogc is a dumpster fire and the dkP org would be better served by rewriting a libogc replacement (w/ a different API) from scratch, quite honestly.

What I find odd is the timing, I highly suspect he learned about it many months ago.

> There's a wide gradient of how much effort people put into reverse engineering consoles in a legal way vs. just copying code straight from their decompiler and slapping an open source license on it.

Agreed (I replied the same in another comment)




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: