An unnamed Apple employee told Wired that a ban would sleep in effect a minimum of 7days / 7days and speculated that your particular freeze was instituted to supply Apple for a longer time to determine which security changes to our policy, if any, were necessary.
That information was apparently corroborated by an Apple customer representative who said Apple had halted all AppleID resets requested on the telephone. The reason came as Wired was attempting replicate a hacker's exploitation for the Apple system that led to the generated identity theft of Wired's Mat Honan.
The replication attempt failed by virtue of systemwide "maintenance updates" that prevented password resets over the phone, the representative told Wired, suggesting they call way back in One day or try changing the password themselves on on the internet google nexus 4 case at iforgot.apple.com.
"Right Designer Nexus 4 Case now, our system is not going to allow us reset passwords," an AppleCare employee told Wired. "I am not aware of why."
CNET has contacted Apple for comment and will definitely update this report as soon as learn about.
Related storiesAmazon addresses security exploit after journalist hackApple responds to journalist's iCloud hackJournalist blames Apple tech for allowing iCloud hackHonan's online existence was compromised last month through a hacker who used his AppleCare and Amazon IDs, together with his billing address and last four digits of his banking to nexus 4 case bumper shoot handle of his various username and password. Rrnside a short article Friday, he said an AppleCare representative fell prey to most social engineering, ultimately causing the sabotage of Honan's online life -- along with Google and Twitter accounts being deleted remarkable MacBook,iPad, and iPhone being wiped clean.
Saying that its "own internal policies wasn't followed completely," an Apple representative told Wired yesterday in which the company was "reviewing each of our approaches for resetting account passwords to be certain of our customers' info is protected."
Amazon responded yesterday by closing an equivalent exploit within own system, a consultant representative confirmed today.
No comments:
Post a Comment