Comments on: Stop Firesheep With FireShepherd

By: Mark

Mark — Wed, 29 Dec 2010 00:05:52 +0000

I invented firefox, also windows 7. Bill stole the idea when he was balls deep in my sister!

By: johnkzin

johnkzin — Sun, 31 Oct 2010 23:08:26 +0000

What does it do with sites that a) don’t support https, or b) have completely different content for https vs http?

By: Erik Slagter

Erik Slagter — Sun, 31 Oct 2010 21:04:17 +0000

use the ‘https everywhere plugin’. it’s awesome

By: Dennis Mathews

Dennis Mathews — Fri, 29 Oct 2010 23:28:56 +0000

The nature of the WiFi security architecture (since it is left unsecured) is a major cause to this vulnerability. An Average user does not have a clue.
More software/plugins is not the solution, the WiFi access point to terminal should have been architected to be secure (even in hotspots)
Bluetooth does not leave the link unsecured.
I have written a post in my blog here ..
http://dennismathews.wordpress.com/2010/10/28/on-wireless-security-and-googles-wifi-scanning/

By: johnkzin

johnkzin — Fri, 29 Oct 2010 20:45:08 +0000

Why not just have a plugin that takes URLs for certain sites and changes them from “http:” to “https:”? The plugin could have a list of sites that it would apply to (with wildcards accepted).

So, a good starting list:
*.facebook.com
facebook.com
*.twitter.com
twitter.com
*.google.com

Seems like it would fix the problem pretty easily.

By: Martin Ove

Martin Ove — Fri, 29 Oct 2010 16:04:25 +0000

Crazy, a “counter-plugin”.

Let the plugin-wars commence! ;-)