The State of Hacked Accounts
Orome1 writes "Most users get hacked at high rates even when they do not think they are engaging in risky behavior, with 62% unaware of how their accounts had been compromised, The results of a Commtouch survey presenting statistics on the theft, abuse and eventual recovery of Gmail, Yahoo, Hotmail and Facebook accounts, shows that less than one-third of users noticed their accounts had been compromised, with over 50% relying on friends to point out their stolen accounts. Also, more than two-thirds of all compromised accounts are used to send spam and scams, which is not surprising, as cybercriminals can improve their email delivery rates by sending from trusted domains such as Gmail, Yahoo, and Hotmail, and enhance their open and click-through rates by sending from familiar senders."
These are lower limits: consider the large but unknown number of users who are not and never will be aware that their accounts have been cracked. Then there are the billions of abandoned accounts...
Warning: this article may contain humor, sarcasm, parody, and perhaps even irony. Read at your own risk.
WTF happened while I was napping?
every day http://en.wikipedia.org/wiki/Special:Random
People just don't care enough about it to inconvenience themselves with strong authentication, how many of our mothers use their dog's name, in all lowercase, as their password on every single one of their accounts?
When you have websites like Facebook that, by default, use unencrypted HTTP and a trivially sniffable session cookie for their authentication, there's really nothing a user can do to protect themselves. (Okay, now they offer HTTPS, but that wasn't always the case.)
The problem with HTTPS, of course, is that it is seriously heavyweight. Most content doesn't need encryption; it just needs authentication. For those sites, SSL is serious overkill.
What this really points out is the desperate need for a standard mechanism of authentication that is not based on cookies, but rather nonce-based, similar to the way digest authentication works, but integrated with web pages so it doesn't feel ugly and bolted on. Until we get that, there's really no point in users bothering to secure their accounts. Why choose a strong password when you're basically sending it back and forth on the Internet equivalent of a postcard?
Check out my sci-fi/humor trilogy at PatriotsBooks.
These days users consider their accounts to have been 'hacked' if there is any unauthorized use, like if they leave their smartphone lying around and a friend posts a status update from it that seems to be considered being 'hacked'.
Define "bs free stuff". Hotmail peaked years ago, but gmail is extremely popular for good reason and yahoo is also very heavily used. And of the probably dozen or so email addresses I have, they're ALL powered by gmail (even though only one of them is actually @gmail.com). Technically two of them are paid, but that's beside the point. I've dealt with having my own mail server. It sucks. And it's not like it's the service's fault that people choose crappy passwords.
How are sites slashdotted when nobody reads TFAs?
In fact Gmail now has cellphone based authentication too, which is pretty much safe unless the attacker is specifically targeting you. But people who'll use it are the same who use good passwords, so not much is gained.
Dilbert RSS feed
Can we get past this already? SSL is not heavyweight, and has not been for years. It's a couple percent of overhead*. Most authentication systems are going to have significantly more overhead than turning on SSL, since they'll be most likely hitting the filesystem or a database to retrieve session information on top of the actual code logic that goes into authentication.
I agree that an authentication system tied more tightly into the browser would be of great value, but it won't happen anytime soon if ever. See: IE6. Hell, even Safari is updated quite infrequently (and even then mostly just security patches, not feature releases), never mind the plethora of mobile browsers floating around these days. That also solves a completely different problem than SSL. There's no getting around the fact that in order to have hijack-proof sessions, all of the authentication data - whether in the form of a session cookie or some new, novel mechanism - needs to be sent encrypted. Not necessarily SSL, but that's more or less a solved problem so why not? I also quite like the idea of nobody knowing what URLs I'm hitting.
* Excluding the time spent tracking down that one damn analytics script that's pulling in a tracking pixel over http and making browsers throw up all over the place
How are sites slashdotted when nobody reads TFAs?
I had a customer yesterday that wanted to change her email password so that it could be the same as the checking account and had me do it because she couldn't figure out the " stupid wavy letters thing" (captcha). She was bitching all the time about security requirements (numbers letters min 8 w caps) but she might as well have given me the keys to her bank account. For the most part my customers don't care about security untill someone has drained their bank account and put a bunch or fraudulent charges on the credit card. Whatever...not my problem.
"We are just a war away from Amerikastan. When god vs god the undoing of man." Dave Mustaine
Define real, when there's ISP's http://www.mts.ca/ outsourcing their email systems to hotmail, what exactly is real?
This would've been much more interesting if you would've posted it as CmdrTaco.
Im not sure that HTTPS qualifies as "seriously heavyweight". A Pentium4 processor can handle about 400mbit/sec of AES SSL-- lets assume this is the home computer. Rendering the HTML, running scripts, and handling the flash content would comprise a far bigger portion of the CPU usage than perhaps 1meg of SSL'd traffic.
On the server side, you can right now get a $250 Xeon E3 1220L, using ~20watts, which can handle ~13gbit/second of AES traffic (with the AES-NI extensions). If thats not sufficient, you can always get a second one.
Encryption is now very cheap, CPU-wise. (P4 stats taken from an actual freebsd box with 'openssl speed'; Xeon stats extrapolated from TrueCrypt and OpenSSL benchmarks on E3 series CPUs).
The sustained data rate is not the heavyweight part, it's the heaviness of building a session. With most web services it's the transaction throughput that's important. The problem is magnified by the number of transactions needed for a single page load on modern sites.
I'm a loner Dottie, a Rebel.
If you want to have fun with a random facebook user visit an Apple store and it wont take long to find a machine with a facebook account still logged in. Some of the results can be very amusing
Imitation Watches at Replica Watches
TOP grade Replica Watches of high quality at wholesale prices!
Join the wise shoppers to let your dreams come true.
BEST deals of imitation watches plus FREE shipping!
*PLEASE NOTE*
You are receiving this email because you or some one with your email has subscribed in our website.We have No aim of spamming and at any time if you want to stop receiving email from us,Just use the unsubscribe button At the end of the email,But you will Lose out our Special offers and Make money online news
Unsubscribe me from this list
I think I just cashed out all my cool points.
"I've dealt with having my own mail server. It sucks."
Factor in there that most users aren't competent to set up a mail server, however insecure it might be. In fact, online mail is so very popular because most users can't even set up a mail client! Way back, when the internet was much newer, I set up Pegasus Mail for some people. (at that time, Outlook seemed to be the number one vector for virus/worm infections) They thought I was some kind of genius, based on the ability to set up a client! Had I suggested, and implemented, a server, they probably would have fallen to their knees and worshipped me, LMAO!
"Windows is like the faint smell of piss in a subway: it's there, and there's nothing you can do about it." - Charlie Br