PhishTank launched today. PhishTank is a site designed to make keeping tabs on phishing sites easier. If you come across a phishing site while browsing the web, you’re encouraged to submit the URL to PhishTank.
PhishTank is a collaborative clearing house for data and information about phishing on the Internet. Also, PhishTank provides an open API for developers and researchers to integrate anti-phishing data into their applications at no charge.
PhishTank is operated by OpenDNS. OpenDNS opened their services to the public earlier this year to much fanfare. David Ulevitch and crew have done an amazing job with OpenDNS, I expect the same from PhishTank.
PhishTank does not provide protection against phishing sites, they simple store phishing related data. OpenDNS does protect against phishing though. OpenDNS and PhishTank go hand in hand. OpenDNS blocks access to phishing sites that are in the PhishTank database. Here’s a little piece from the OpenDNS FAQ about reporting phishing sites:
The fight against phishing isn’t just for the banks and big companies to tackle; you can help. Right now, we encourage submission of possible phishing sites via our contact form. Nothing will be blocked unless it’s verified.
Later this summer, we will introduce PhishTank.com, a free community site, with API, which will serve as a collaborative clearing house for data and information about phishing and malware on the Internet.
PhishTank will no doubt prove to be a valuable resource for the internet security community. Now, users of OpenDNS can basically control what sites are deemed “phishing” sites by making use of PhishTank. This was one of the main gripes people had with OpenDNS initially. There was no method to show what sites were flagged as phishing sites. Let there be transparency!
Slackware 11.0 Release Candidate 4 is out! This release sees kernel 184.108.40.206 included as the default. Soon after RC4 was made, Patrick made another small update to the ChangeLog:
Sun Sep 3 19:59:47 CDT 2006
a/udev-097-i486-8.tgz: Fixed a missing ‘[‘ in rc.udev. Thanks to
guilherme for pointing out the error, and to J., who found the missing
‘[‘. (It had fallen off my desk and ended up under a table)
kernels/System.map: Forgot to gzip a bunch of these. Thanks, Steve’o.
This should definitely be the last RC before Slackware 11.0 final is released. In the past two or three Slackware releases (10.0, 10.1, and 10.2), we’ve only seen 2 or 3 release candidates. I suppose there’s a chance we’ll see RC5 this time, but I’m thinking this RC4 will be the last. Probably see Slackware 11.0 final within a week and a half or so.
Slackware 11.0 Release Candidate 3 is here!! The 2.6 kernel was moved from /testing/ to /extra/. What’s that mean? Not much really, other than it’s considered to be more stable since it’s now in /extra/.
Head on over to the Slackware Blog for more details.
Slackware 11.0.0 is really feeling “official” now for me. Yesterday, Patrick made an update to the -current ChangeLog stating he had bumped the /etc/slackware-version number up to 11.0.0. I had been waiting for him to bump that version number up. Now that he’s done so, I know Slackware 11.0 will be out soon. I am excited.
Optimization can drastically change the way your websites load. Poorly optimized sites load slowly and aren’t very nice to look at for the users. Well optimized sites load quickly and provide the user with the content they need. There’s lots of different ways to optimize site performance. You can optimize apache, mysql, PHP, and even your HTML code.
One thing people often overlook when optimizing a site is the CSS. Blogging Pro takes a look at four different CSS optimization tools. I, for one, have never really thought of optimizing CSS. I just don’t think it’s really ever occurred to me, I need to work on learning CSS before I get into optimization. But, there’s tools to do the optimizing for you, go check out the article at Blogging Pro.