I remember seeing some documentary interview with a career break & enter guy. He said he learned pretty quick to rob rich neighbourhoods; they had much better stuff to steal. The interviewer asked if he was worried about house alarms, and he said that the vast majority of houses he robbed had alarms not switched on or otherwise inoperable. He'd just try break in, if he didn't hear a siren he'd be in and out in a few minutes.
..and this appeared in an Australian newspaper just yesterday "'Right to silence' law changed" http://www.smh.com.au/nsw/right-to-silence-law-changed-20120814-2462p.html
or to extort facebook? "pay for our botnet protection, as we wouldn't want to see your advertisers getting poor value for money".
Some was arrested in Japan for this recently: http://yro.slashdot.org/story/12/07/05/135230/japanese-13-year-old-arrested-for-virus-creation
Someone steals my identity (from cards in a wallet robbed from my house) - signs up a bunch of cell phones in my name, then steps out on the bill. The police get me to fill out a form, and I spend hours dealing with 3 different cell companies, and debt collection agency.
Do you think the police checked any cell tower data to find the perpetrator?
Here's a quick mock-up of how it will look: http://i.imgur.com/2aA3Z.jpg
Apple announce "You won't be able to write native apps, just do everything in a browser!". They must've known they were buidling at app store at that time!
I wish i had some mod points for you
Hey, you forgot to include a link!
Which is a much better position than "Let's pretend there's no bugs, and hush up anyone who says there is". Nice one, Google...
S3 is just storage. Someone still needs to pay the bandwidth on the server that streams that content. Cloudfront can do streaming from your S3 store.
So the gap is "the secret key must be kept secret"? I don't see that as a digital certificate failing. It's also the reason we have revocation lists.
The 3rd party would only ever get the intersection of "do not mail" and their own marketing list. And emails wouldn't be sitting around in clear text in a database / filesystem..
Here's what 'supercookies' actually are (from the horse's mouth: http://cyberlaw.stanford.edu/node/6715)
* you hit a page which includes a wlHelper.js script
* wlHelper.js is served with header that tell your browser - cache this forever
* wlHelper.js contains code something like this:
var unique_id = 'RANDOM_LOOKING_STRING_JUST_FOR_YOU'
if MUID cookie doesn't already exist
set MUID cookie to unique_id
You delete your MUID cookie - but next time you hit a page that contains wlHelper.js the cached version is pulled form your browser. unique_id is there in the cached code, so the cookie gets set again.