
If I read that last point correctly, the main beneficiaries of this will be phishing targets (banks, car manufacturers and so on).
It will be interesting to see whether any of them actually bother to use it. Last time I checked, most were still not publishing SPF which would make a phishing email purportedly from somebank.com but sent by an open proxy on a domestic DSL line transparently obvious.
And then there's Microsoft, which august organisation still goes out of its way to make its Technet emails look as much like phish as possible.
Still, PhishTank looks good to me. Certainly a refreshing change from the likes of PhishFighting...
Category: Phish
Technorati: Phish
1. Jerry Carter02/10/2006 16:48:59
Homepage: http://datatribesoftwerks.com
Sounds great.
/devil's advocate on/
What keeps the API from being used by Phishers to tune their phish?
/devil's advocate off/
2. Chris Linfoot02/10/2006 16:52:24
RT docs
http://www.phishtank.com/api_documentation.php
3. Jerry Carter02/10/2006 17:33:03
Homepage: http://datatribesoftwerks.com
(for those to lazy to click, like myself)
"Second, as an application developer you are required to register your application with us. That means you need an account. We don't ask a lot of questions but we use the information you give us to create your authorization page on the Phishtank so users can verify your application can access their data in the PhishTank."
I guess that's about all anyone can do. So long as someone keeps an eye on developers to make sure their use continues to match their stated intent.
The adversary is unscrupulous, and sometimes musters something resembling cunning.
Unable to post a comment? Please read this for a possible explanation...