Security Skins: Single Sign-On with Images
Appol writes "Berkeley researchers propose a Mozilla extension to stop phishing. They claim that users only need to remember one password and one image for their lifetime to securely log in to any number of sites. They also use uniquely generated visual hashes to "skin" trusted windows and webpages, which is harder to spoof than the SSL lock icon. To verify that the skin is legit, the user has to compare two images, which is easier for novices than verifying a certificate."
...whether Passport or some open-source solution. The task of typing some stuff into a form field is not so onerous we need a complicated solution for a non-problem. Most browsers support various ways to locally remember form fields that take care of these problems simply. And this wont stop phishing.
Isn't this a lot like Netcraft's new Anti-Phishing plugin? I'm glad that all these people are finally taking initiative against phishers, even though it's almost definitely due to the heightened media attention that phishing is currently getting.
In practice though, I think the only way this would really work is if it's shipped by default in Firefox. The peoplen that would install this anti-phishing plugin aren't usually the people that would get tricked by phishing scams anyway.
- dshaw
Note: This is all IMO; and yes, I understand that some scams are so realistic that anyone could get caught in their webs.
There are people who are blind what do they do ? Stare at the screen hoping there eye sight comes back?
Not a good over all solution, you need a seperate medium/channel to display such pictures.
*what if they're colour blind?*
They'll pick a black and white image?
Pulp Audio Weekly - Geek News and Reviews
Using an SO would be a bad idea; if you ever break up just think about how dumb you would feel if you ever find another significant other (sort of like an online version of the embarassing tattoo). Better to pick a cute puppy or something like that instead.
I Am My Own Worst Enemy
That sounds like a good idea. However, it may be like asking the average citizen to spot counterfiet money. And after a few times of being asked to compere images, the user may get annoyed and every time afterward, they will just confirm everything to get done quickly.
Tired of Apathy? http://apathyonline.net
Of course, if you've already written the paper, it takes minimal effort to print/export it to PDF, whereas if you export to HTML you have to do all kinds of double-checking to make sure it's formatted correctly, and probably have to mess with the code some.
Plus, if you really are running that slow a system, it's possible whatever HTML they use *won't* quite be so universal. If you're using an old browser that doesn't render tables quite right or somesuch, the HTML might just be a bigger hassle.
Warning: Apple/Nintendo fangirl. Likes her electronics cute & cuddly. May be rabid.
I skimmed the article, and I noticed the adware section, but it didnt really answer my question: If the secure aspect is the local picture and the local picture needs to be pulled from the local machine by the page then what is to stop an adware program from grabbing that api and using the secure picture on a insecure site?
Dear valued ebay customer,
You may be aware of a new technology to synch a picture with a web page to ensure it is legitimate, please click this link to download an executable to synch the picture you selected with our server to better provide you with secure transactions.
Anyone that sees this as a phishing scam, doesn't need this technology, Anyone that does need this technology is just as likely to fall for this.
I'm with you until this bit:
But what the hell - send them all new ones by e-mail.
If the site changed domain the user would have to re-register, or at least visit the site and provide a new hash, I don't see any way around that.
The other thing, of course, is that this relies on user co-operation to install new software, and also implies complete trust in that software. If you're going to force people to install new software, why not just use personal certificates? You also missed a vulnerability - the hashes given to the webserver include a reasonable amount of known (and specified) plain text. This makes an attack of the hash algorithm much easier. Given the value of discovering the master password (it will unlock the users entire online life, including banks etc) it's not hard to imagine people committing serious resources to breaking the hashes.
All of this reminds me of Schneier's Law:
"any person can invent a security system so clever that she or he can't think of how to break it."
I'm not saying I can think of a way of breaking it, but personally I'd go with something well tested in the real world.
---- Den ene knappen er powerknapp, den andre er Bender voice knapp "Bite My Shiny Metal Ass"