Build Status:

###Table of Contents

• WSI-Services httpBL
• About Project Honey Pot
  • HTTP Blacklist
• Installing WSI-Services httpBL
  • GIT
  • Composer
• Using httpBL
  • Namespace
  • Class: httpBL
  • Class: response
• Utilities
  • phpDocumentor
  • phpUnit
    • Code Coverage

WSI-Services httpBL

PHP library for checking IPv4 addresses against Project Honey Pots Blacklist. An API key from Project Honey Pot is required to utilize this library. You can create an account and obtain an API key by creating an account at Project Honey Pot, then request an access key.

About Project Honey Pot

Project Honey Pot is the first and only distributed system for identifying spammers and the spambots they use to scrape addresses from your website. Using the Project Honey Pot system, you can install addresses that are custom-tagged to the time and IP address of a visitor to your site. If one of these addresses begins receiving email, not only can they tell that the messages are spam, but also the exact moment when the address was harvested and the IP address that gathered it.

HTTP Blacklist

The HTTP Blacklist, or "http:BL", is a system that allows website administrators to take advantage of the data generated by Project Honey Pot in order to keep suspicious and malicious web robots off their sites. Project Honey Pot tracks harvesters, comment spammers, and other suspicious visitors to websites. Http:BL makes this data available to any member of Project Honey Pot in an easy and efficient way.

Http:BL provides data back about the IP addresses of visitors to your website. Data is exchanged over DNS. You may query your local DNS server and receive a response back that indicates the type of visitor to your site, how threatening that visitor is, and how long it's been since the visitor has last been seen within the Project Honey Pot trap network.

Installing WSI-Services httpBL

GIT

Clone the GIT repository locally:

$ git clone https://github.com/WSI-Services/httpbl.git

Composer

Add the required sections to your composer.json file:

"require": {
	"wsiservices/httpbl": "dev-master"
},
"repositories": [
	{
		"type": "git",
		"url": "https://github.com/WSI-Services/httpbl.git"
	}
]

Using httpBL

Namespace

use WSIServices\httpBL;

Class: httpBL

$httpBlacklist = new httpBL\httpBL($apiKey);
$response = $httpBlacklist->lookup($ipAddress);

Class: response

if($response->inBlacklist()) {
	echo 'Response Time-To-Live: '
		.$response->getTtl().PHP_EOL;

	$responseType = $reponse->getType();

	echo 'Visitor Type Id      : '
		.$responseType.PHP_EOL;
	echo 'Visitor Type         : '
		.$response->getTypeName($responseType).PHP_EOL;

	if($responseType === httpBL\response::VISITOR_SEARCH_ENGINE) {
		$searchEngineId = $response->getSearchEngine();

		echo 'Search Engine Id     : '
			.$searchEngineId.PHP_EOL;
		echo 'Search Engine        : '
			.$response->getSearchEngineName($searchEngineId).PHP_EOL;
	} else {
		echo 'Threat Score         : '
			.$response->getThreatScore().PHP_EOL;
		echo 'Last Active          : '
			.$response->getLastActive().PHP_EOL;
	}
} else {
	echo 'Visitor ('.$response->getIpAddress()
		.') is not in the blacklist.'.PHP_EOL;
}

Utilities

This library includes utilities for documentation and testing.

phpDocumentor

From the root of the project, run the following command:

$ ./utilities/phpdocumentor.sh

Example Output:

Collecting files .. OK
Initializing parser .. OK
Parsing files
Parsing /path/to/httpBL/source/httpBL.php
Parsing /path/to/httpBL/source/response.php
Storing cache in "/path/to/httpBL/documentation/api" .. OK
Load cache                                                         ..    0.014s
Preparing template "responsive"                                    ..    0.367s
Preparing 13 transformations                                       ..    0.000s
Build "elements" index                                             ..    0.003s
Replace textual FQCNs with object aliases                          ..    0.038s
Build "packages" index                                             ..    0.025s
Collect all markers embedded in tags                               ..    0.007s
Build "namespaces" index and add namespaces to "elements"          ..    0.002s
Transform analyzed project into artifacts                          ..    1.225s
Analyze results and write report to log                            ..    0.006s

The documentation for this library is generated in the documentation/api directory.

phpUnit

From the root of the project, run the following command:

$ ./utilities/phpunit.sh

Example Output:

PHPUnit 4.0.15 by Sebastian Bergmann.

Configuration read from /path/to/httpBL/phpunit.xml

.........................................................

Time: 4.58 seconds, Memory: 4.75Mb

OK (57 tests, 154 assertions)

Generating code coverage report in Clover XML format ... done

Generating code coverage report in HTML format ... done


Code Coverage Report:
  2014-04-19 20:04:24

 Summary:
  Classes: 100.00% (2/2)
  Methods: 100.00% (18/18)
  Lines:   100.00% (106/106)

\WSIServices\httpBL::httpBL
  Methods: 100.00% ( 5/ 5)   Lines: 100.00% ( 13/ 13)
\WSIServices\httpBL::response
  Methods: 100.00% (13/13)   Lines: 100.00% ( 93/ 93)

If you would like to perform live tests with your Project Honey Pot API key, edit file test\httpBLLookupLiveTest.php and locate the following line.

define('WSIServices\httpBL\PROJECT_HONEYPOT_API_KEY', 'abcdefghijkl');

Replace abcdefghijkl with the API key provided to you by Project Honey Pot.

Code Coverage

Running phpUnit generates logs in directory test/log. Below you can see the files and discriptions of the generated output.

coverage.xml

The XML format for code coverage information logging produced by PHPUnit, loosely based upon the one used by Clover.

report (directory)

The HTML format for code coverage information; provides a package overview, namespace & class discriptions, charts, and reports (including errors, markers, and depricated elements).

testdox.txt

The text format of the PHPUnit TestDox, to generate agile project documentation based on the tests.

testdox.html

The HTML format of the PHPUnit TestDox, to generate agile project documentation based on the tests.

logfile.tap

The Test Anything Protocol (TAP) is Perl's simple text-based interface between testing modules.

logfile.json

The JavaScript Object Notation (JSON) is a lightweight data-interchange format.

You can find more out about phpUnit logging in their documentation Chapter 14. Logging and Chapter 15. Other Uses for Tests.