Earlier quoted context omitted.
Easy solution. Logging in takes two passwords. After you enter your first password (first 8 chars of your 16 char password) you are presented with an image of a Tiger. You now trust the system. (The picture of a tiger was your secret image). You now enter your second password (the remaining 8 chars of your 16 digit password). See site key: http://en.wikipedia.org/wiki/SiteKey
SiteKey is completely susceptible to Man-in-the-middle (unless the user is a scrupulous cookie-manager and refuses to re-authenticate a computer more than once), so adds minimal value over regular SSL.
If malware authors ever learn how to spell we're all screwed
81–90 of 106 posts
Re: If malware authors ever learn how to spell we're all screwed
#82I forget what the term for it is, but there's a principle that any dialog that's asking the user for credentials or authorization must be clearly delineated from the rest of the UI and thus "unspoofable". The example I recall was a "ribbon" in the OS that slide out to reveal the dialog. If a dialog presented itself but the ribbon remained along the edge you could immediately tell it was spoofed. Of course this requir…
We tried this with "AOL Certified Mail", which had an unspoofable official chrome, and I don't remember any serious drop in phishing.
Re: If malware authors ever learn how to spell we're all screwed
#83Earlier quoted context omitted.
"The user is then presented 10 images (a tiger, a house, a moose, etc) from a library of 10,000 images." I should have made this more clear. The ten images are chosen randomly from the group of 10,000 The question is: are there 10,000 images that are different enough people won't be fooled. Say my picture is a green house. And a prompt has a picture of a red house, will I accidentally think its the right site key? Th…
That is a fair attempt. The weak point of course is the bit of data which stores which image you chose. If the attacker is able to read that, then he can display the right image.
1) If the attacker can scrape the screen, they can detect which image you are using - securing the entire pipeline to the screen is hard.
2) 10,000 images is way too few.
Even if we can assume an even distribution of images, as an attacker I can serve the same image to all targets, 1 in 10,000 will now think that they are interacting with a trusted component
Re: If malware authors ever learn how to spell we're all screwed
#84Earlier quoted context omitted.
Unless the entire image is a clickable hotspot that starts the next step in the process of their evil. ;)
Can you do that? I.e. launch events on mouse down but not a full "click"?
Re: If malware authors ever learn how to spell we're all screwed
#85This is why you don't run your computer using the default UI theme on the most popular OS.
Re: If malware authors ever learn how to spell we're all screwed
#86Re: If malware authors ever learn how to spell we're all screwed
#87That's what happens when programmability (JavaScript, Java, Flash, plugins...) is added to a presentation format (HTML). Maybe this is the right time to revive Gopher and give Usenet a fresh breath of life.
Re: If malware authors ever learn how to spell we're all screwed
#88Simple solution for tech savvy users. All system prompts should include a photo of a user selected image. If the incorrect image is displayed you know its a scam. For example when I install Windows 8 or Mountain lion one of the first prompts I must address is: "Please choose an image to help you identify valid system prompts" The user is then presented 10 images (a tiger, a house, a moose, etc) from a library of 10,0…
Tech savvy users are not the main problem in malware. The whole SiteKey/tiger image solution only gives you an illusion of the solution. What happens when the system displays "System error, unable to display the image?" How will a convincingly-written error message prevent your average gullible or below-average competence computer user from logging in to a phishing site? Think of how many things can go wrong on a com…
Re: If malware authors ever learn how to spell we're all screwed
#89Earlier quoted context omitted.
Can you explain how that fixes the problem? I'm not sure I understand.
It doesn't -- at all -- the obvious workaround is to extend the middleman game a little longer and pass the user's answer to the site.
Re: If malware authors ever learn how to spell we're all screwed
#90Earlier quoted context omitted.
Can you explain how that fixes the problem? I'm not sure I understand.
It doesn't -- at all -- the obvious workaround is to extend the middleman game a little longer and pass the user's answer to the site.
Security is never about 100% guarantees. It's about reducing the exploitability and impact of weaknesses.