Firesheep is a Firefox extension that makes it easier to steal logins and take over social media and email accounts after users log in from a WiFi hotspot or even their own unprotected network. Zscaler researchers have created, and are now offering to every consumer, a free Firefox plugin called BlackSheep, which serves as a counter-measure. BlackSheep combats Firesheep by monitoring traffic and then alerting users if Firesheep is being used on the network. BlackSheep does this by dropping ‘fake’ session ID information on the wire and then monitors traffic to see if it has been hijacked.
Then they will create anther extension called PinkSheep that will detect BlackSheep and will circumvent it.
What we really need is a wolf.
A wolf in sheep’s clothing, or the kind that dresses up in women’s clothing?
It only sends the fake stuff every 5 minutes so could be countered by adding a window to firesheep.
It also doesn’t stop a hijacked session, so you get hijacked and see later that firesheep is running somewhere – now you have to logout in the interim and hope nothing bad happened.
If they aren’t using IP verification, I can use a VPN tunnel for the transmissions and blacksheep would not see them.
What moron thinks that because they have a plugin in their browser that detects someone else using a plugin in their browser, that somehow they’re no longer leaking sensitive data over a public network.
Treating the symptom doesn’t fix the problem… but I suppose it allows people to sleep at night in ignorance.
The internet is not all on my hard drive? You know the one on my desk?
Yeah, that big black and tan box that has my automatic pullout cup holder!
Where did my refrigerator magnet get to that holds my backup 8″ floppy disk to my steel fire proof filing cabinet?
You can download the Internet here: http://thepiratebay.org/torrent/5923737/Geocities_-_The_Torrent It’s just 640 GB!
Heh, reminds me of this, click to see how OSNews would look if it had been hosted on geocities:
http://wonder-tonic.com/geocitiesizer/content.php?theme=2&music=6&u…
In today’s world, I think any site that handles any personal information (other than name, and timezone) should require at least simple SSL encryption.
Sites using phpbb, WordPress, etc since they ususally only store name, IP, and timezone info can be exempt.
These site should be forced IMO. (at least parts of the site once you are logged in)
Shopping sites (Amazon.com), WebMail (Hotmail, Google), Banks/Financial, social sites (Facebook).
Unfortunately even using Facebook Pro Secure is iffy, sometimes it still uses normal http.
http://userscripts.org/scripts/show/49079
Edited 2010-11-08 20:13 UTC
The reason so few use SSL on their sites is the brain-dead stupid business model of SSL certs. Tying identity to encryption is a misdirection. Encryption should not require identity. SSL certs are expensive and simply don’t prove anything useful.
Developers are not the problem. It’s the CAs and the browser vendors. Producing scary errors on self-signed certs protects absolutely bloody nobody and locks password protection to the SSL racket.
I’ll agree that the entire concept of SSL certificate/encryption, with CA’s and high prices, is indeed a broken system and a scam to some extent – but the “scary errors” browsers display have a valid purpose.
Given how SSL works, and how users expect it to behave, if you can’t verify the certificate you’re using belongs to the site you are surfing, you can’t know that the encryption keys you’re sharing with them haven’t been tampered with by a middleman. On a public wifi network, this can be a real threat…
In any case – if I encounter a site with an “untrusted” certificate, and I don’t figure it matters for that particular site (read: I’m not revealing personal information to the site), then I’ll just accept it anyway.
These days, you can get a free Class 1 cert (unrevokable, single domain)… or a cheap Class 2 verification wildcard cert for like $25/year ($50 for two years) from StartCom:
http://www.startssl.com/
All major browsers accept these… so it’s hard to complain about it much.
Edited 2010-11-08 22:46 UTC
One of the reasons I’ve heard cited is that encrypting all communication with SSL incurs higher server load (and client for that matter – those poor cell phones have to encrypt/decrypt every request to the server).
Another thing it also limits is the ability to easily load balance cache-able resources – for example, a trick that many sites use is to farm their image or .js hosting out to other load balanced servers on different domains – which would require a connection to a different server, which creates a complicated security situation. I already see this often while using gmail https – my browser is constantly warning me that there are “some unsecured elements on the page”…
There are some companies that take this stuff seriously… Google for example even gives you a way to search on a public network without anyone else sniffing your search terms (except Google of course… but hey, they already know everything about you):
https://encrypted.google.com/