Apple provides credit to people who have reported security issues
support.apple.com
support.apple.com
This was the guy who posted the YouTube video claiming he found the flaw that forced Apple to take the developer center down for one week.
Looking through the list, there's plenty of Anglo-American sounding names, and the percentages seem about right:
David Bloom, Will Drewry, Christian Matthies, Jeremy Richards, Joshua Long
Also, while it may be less true in some "Anglo" nations, there's millions upon millions of "international" sounding names in the US. In Houston, there's tons of hispanic sounding names (and despite what some might say, plenty of them aren't illegal, but from families where they've been here for generations). Go up north, plenty of Germanic names. (My ex's maiden name was Krausert, and she was very American). Tons of other examples.
It always puzzles me to see statements like this... Maybe I'm biased by the fact that I am American but don't have a western european surname and a good number of Americans I interact with do not either. In what part of the country does it seem remarkable for someone to have a "non-Anglo-American" name?
Put it this way, if I ran into somebody named "Lutz", I wouldn't think anything of it. If I ran across many people with Germanic names though, I might wonder if I were in somewhere like south-central PA (an area notable for a large number of German descendants: http://en.wikipedia.org/wiki/Pennsylvania_Dutch). The distribution would catch my eye, not the particular name itself.
(Personally, I'm not really seeing any interesting trends with those names.)
And I'm really hoping this is sarcasm.
What difference does it make if the disclosure was responsible or not?
If Facebook's billing platform for advertisers was compromised in some fashion, do you think they'd wait even a minute to take it off-line until they situation was under control?
If someone gives you reproduce steps for an issue, that's a lot better than just seeing intrusions or weird stuff happening without any idea of the cause.
And steps to reproduce should help you bring the system up faster.
I'm not sure I understand your argument.
You seem to be implying that they kept their dev center down for longer than they could have? I don't think we have any idea how hard they worked to get it back online — maybe they put in as much effort as they could to resolve the issue as quickly as possible, and "as quickly as possible" turned out to be weeks.
They did restore the most useful dev tools after one week (adding devices, updating provisioning profiles). So it's not like they kept the entire system down for weeks.
And surely rebuilding their system now is better for their developer customers in the long term? If they had simply attempted to patch it up, it may have led to other exploits down the road. Rebuilding it from scratch seemed like a painful but necessary long-term procedure.
The scales of impact aren't even on the same register.
2013-07-22 iadworkbench.apple.com
An information disclosure issue was addressed. We would like to acknowledge Ibrahim BALIC (Balich IT - www.balicbilisim.com) for reporting this issue.
hah, some of these are entertaining.
This title is inaccurate - the linked pages credits 7dscan.com and SCANV for reporting the developer centre issue.
Ibrahim BALIC is credited with reporting an apparently unrelated issue in iAd Workbench.