full-disclosure - Request for comments: anti-phishing storefrontapproach

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <0eb501c56944$ddf5e720$6fd4a8c0@othello>
Date: Sat Jun  4 21:35:11 2005
From: niceman at att.net (Mike N)
Subject: Request for comments: anti-phishing
	storefrontapproach

I can see many users falling for the scenario below - it *sounds* realistic 
since they don't understand the underlying mechanism.

----- Original Message ----- 
From: "Dan Margolis" <dmargoli+lists@....net>

> Or, better yet, a box that says "If the above image does not read
> 'AUTHENTIC,' do not sign in." Users would assume that some sort of
> verification were going on. Never mind the mechanism.