SoylentNews is people
SoylentNews
from the don't-store-personal-photographs-on-an-internet-connected-device dept.
PapayaSF and AnonTechie write in with 2 stories which seem to be linked. The first is the leak of nude and personal photographs of celebrities, and the second is perhaps the flaw that allowed someone to access the photographs.
Stars Exposed in Massive Nude Photo Leak
Nude celebrities, bitcoins, and Apple: it's a story seemingly designed to stir up the entire internet. Scores of private photos of celebrities such as Jennifer Lawrence, Kate Upton, Selena Gomez, Ariana Grande, Kirsten Dunst, and Mary Elizabeth Winstead have been leaked (allegedly from Apple's iCloud), and posted on 4chan in exchange for bitcoins. A list of 100+ names has appeared, but pictures have not yet appeared for many names on the list (including Kate Bosworth, Kim Kardashian, Rihanna, and Kaley Cuoco). Victoria Justice claims the photos of her are fake. Twitter accounts are being shut down. The story is still developing, so grab your popcorn.
This could be the Apple iCloud flaw that led to celebrity photos being leaked.
An alleged breach in Apple’s iCloud service may be to blame for countless leaks of private celebrity photos this week.
On Monday, a Python script emerged on Github (which we’re not linking to as there is evidence a fix by Apple is not fully rolled out) that appears to have allowed malicious users to ‘brute force’ a target account’s password on Apple’s iCloud, thanks to a vulnerability in the Find my iPhone service. Brute force attacks are where a malicious user uses a script to repeatedly guess passwords to attempt to discover the correct one.
The vulnerability allegedly discovered in the Find my iPhone service appears to have allowed attackers to use this method to guess passwords repeatedly without any sort of lockout or alert to the target. Once the password has been eventually matched, the attacker can then use it to access other iCloud functions freely.
(Score: 4, Informative) by VLM on Monday September 01 2014, @07:45PM
You've thrown down the gauntlet with the bacon thing, and the ultimate way to cook bacon is on a wire rack in the oven for like 20 minutes at 400 or so. You have to keep a really close eye on it toward the end as the difference between undercooked and burned is like 120 seconds.
I gave up on both the frying pan and the microwave for bacon once I mastered the oven technique.
(Score: 5, Funny) by c0lo on Monday September 01 2014, @08:23PM
Next step - use an overclocked cryptocurrency rig to cook your bacon: at least you'll derive some secondary benefits and look nerdier.
End notes:
* you see, the 400K is not nearly enough for a crispy bacon. Hand over your nerd card if you use other temperature scale.
* 20 min on my 3kW fan forced electric oven is a waste, no matter how perfectly the bacon cooks. I'd try an electron gun for a precise energy transfer, but the bremsstrahlung would kill me.
https://www.youtube.com/@ProfSteveKeen https://soylentnews.org/~MichaelDavidCrawford
(Score: 3, Funny) by isostatic on Monday September 01 2014, @11:10PM
you see, the 400K is not nearly enough for a crispy bacon.
True, but 640K should be enough for anyone
(Score: 2) by c0lo on Monday September 01 2014, @11:29PM
Wolfram doesn't understand your query [wolframalpha.com].
https://www.youtube.com/@ProfSteveKeen https://soylentnews.org/~MichaelDavidCrawford