full-disclosure - Analysis of CherryOS and PearPC code

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

From: khermansen at ht-technology.com (Kristian Hermansen)
Subject: Analysis of CherryOS and PearPC code

I became interested in this whole debate recently and wanted to get to
the bottom of it all (in the interest of FD).  I did some simple IDA Pro
analysis myself, but I am wondering what other people here think?  Is
there any possible way CherryOS did NOT steal PearPC code?  And how does
an open source project like PPC protect themselves from harm like this
in the future?  I believe these to be important security-related issues
-- not to mention the fact that Maui's website has been getting hacked
because of all the fuss over it lately.  Can anyone shed some light on
the subject from another point of view which I am not seeing?

Here is a link to the IDA Pro analysis complete with screenshots:
http://www.ht-technology.com/cherryos-pearpc/cherryos-pearpc.html
-- 
Kristian Hermansen <khermansen@...technology.com>