Thanks dmilligan, very interesting! I'd just like to point out that it's probably not a good reason to say the keys are the intellectual property of Canon. It's actually near impossible (if not impossible) to figure out a private key assuming it is of suitable strength (key length). The whole idea of these keys is that they CANNOT be figured out so the public key can float freely. So they either figured out the key because it was low strength OR someone at Canon slipped it to them. I'd wager that if these are strong keys, the latter is what happened. So the real risk of releasing these keys to any developer is that it might force Canon's hand into finding and prosecuting the person who released confidential information (which I don't think they want to do, presently).
This is pertinent to the thread because the OP's request is essentially asking that any proof that a potentially stolen key was not used to unlock the camera. I think that valid. I hope I'm not going off-topic, but Alex's concerns that some development may lead to bricked cameras should not be dismissed lightly. Should ML ever brick many of these cameras Canon would have no choice but to change the keys on all cameras leaving the factory. I can't see them fixing any of the bricked cameras, or servicing ones that ran ML. That they're letting cameras leave the factory with a broken, or hackable key probably already makes them very nervous, because, in a sense, it can be argued that the behavior implies that they approve of ML.
In short, the senior devs have made the right decision in limiting access. But Alex's cautionary words should haunt everyone just the same.
