That idea with the closed part isn't quite good for a couple of reasons. At first it violates the open source idea thats behind this program. Second, the hiding of the key has to be
VERY good, if every script kiddy can get it its pretty useless. And of course this has to work on at least 3 different OS, so the effort to realize just this little, non-productive feature, is at least a double digit factor higher than the effort to realize the whole functionality of the program
.
And third, and thats the most important point imho, it's almost useless. The AACSLA revokes ALL Device Keys on a regular basis, so no matter how good we hide our stuff, it WILL get revoked. The only benefit of the hiding would be that they MAYBE can't figure out from where we got that key (they can still do black box tests against the program and derive this way where the key comes from) so that they can't point with their fingers on that manufacturer.
Anyway, thanks for the new Certificate, too bad that its not that helpful without recent Processing Keys, but well, better than nothing. Honestly, i haven't worked on aacskeys for a long time now, i have a slightly better version here than the last release but never bothered to make it public because the benefits are quite small. Without recent Processing Keys it doesn't help that much that BDAV's should be decrypted correctly now and that finally it doesn't crash on Mac OSX anymore
.
