full-disclosure - [HV-PAPER] Anti-Phishing Tips You Should Not Follow

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 for Android: free password hash cracker in your pocket

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

Message-ID: <200603311656.k2VGuW5R006365@turing-police.cc.vt.edu>
Date: Fri Mar 31 17:56:50 2006
From: Valdis.Kletnieks at vt.edu (Valdis.Kletnieks@...edu)
Subject: [HV-PAPER] Anti-Phishing Tips You Should Not
	Follow 

On Fri, 31 Mar 2006 21:14:58 +1200, Jasper Bryant-Greene said:
> Marcos Ag?ero wrote:
> > Jasper Bryant-Greene escribi?:
> >> Seriously though, it wouldn't be that hard to forward the POST on to the
> >> real bank website, would it?
> > I think so, but would be very easy to detect. Logs would show lots of
> > diferent user logging in from the same IP Address.
> 
> Phishing scams are public in nature. They aren't trying to avoid 
> detection :) and the IP address would of course be spoofed.

http is a TCP connection, so you'd have to get through the 3-packet handshake.
The vast majority of machines now implement RFC1948, so it's not that easy to
do anymore....

(It's doable by somebody with sufficient technical ability - but if you're
*that* good, why you wasting time running a phishing scam?)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 228 bytes
Desc: not available
Url : http://lists.grok.org.uk/pipermail/full-disclosure/attachments/20060331/71c38ba4/attachment.bin