K T wrote:
Whenever the dev centers come back, I'd expect Apple to force devs to change their password(s) first thing. The process should be straightforward and for anyone wishing to act now, please see this User Tip:
How To Change Your Apple ID/Password(s)
Passwords are handled by the AppleID servers. Those servers were not involved. The hacker in question was able to do something to circumvent those authentication servers and query the stale copy of developer data that Apple keeps (or probably kept, past tense) on the developer site. If you have ever changed your Apple ID before, you would have noticed that you had to manually contact Apple developer support to get it to recognize your new e-mail address.
Everything else, including certificates, is encrypted.
If anyone has bothered to watch the video (which seems to be gone now), you would see that he used some web service, authorized with his own Apple ID, and included a hashkey that was able to return information about other developers.
What Apple has to do now is strip out that stale copy of developer information and do that interaction correctly, the way it should have been done in the first place. Instead of keeping a stale copy, the developer systems will have to interact more with the AppleID servers to query a developer's current e-mail address. Considering that Apple recently rolled out two-factor authentication, that is going to take some work.