In the first post in this “series” (wtf? when did I start doing “series”? Oh, right…) I went over the basics of what Bad Behavior is and how to get it installed. Bad Behavior’s advanced setup required some investigation and forethought in order to work out it so it was best to break the post up; so, you know, here you go.

By default, if all you do is follow the instructions laid out in the first post you’ll have a working setup. For some of the cooler logging functionality you’re going to have to edit the included file ‘bad-behavior-generic.php’.

I’ve been feeling kind of down on Bad Behavior about this process for a few days now. It seemed kind of lame that they came up with such a great idea, wrote a really cool script but then killed the implementation. After working with the script for a couple days it’s starting to make some sense but not really enough to convince me it shouldn’t have been done.

To help others who’ve had this delima, I’ve compiled a list of steps to get Bad Behavior logging up and running.

Install Bad Behavior

The first thing you’re going to want to do is create a database and add the connection code to your version of ‘bad-behavior-generic.php’.

Here’s the SQL:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15

CREATE TABLE IF NOT EXISTS `bb_logs` (
  `id` int(11) NOT NULL auto_increment,
  `ip` text NOT NULL,
  `date` datetime NOT NULL default '0000-00-00 00:00:00',
  `request_method` text NOT NULL,
  `request_uri` text NOT NULL,
  `server_protocol` text NOT NULL,
  `http_headers` text NOT NULL,
  `user_agent` text NOT NULL,
  `request_entity` text NOT NULL,
  `key` text NOT NULL,
  PRIMARY KEY  (`id`),
  KEY `ip` (`ip`(15)),
  KEY `user_agent` (`user_agent`(10))
)

For this simple demo I’m going to use the native php functions but it’s more than likely you’ll have a database class. I put the below directly past the comments above any function declaration:

33
34
35
36
37
38
39
40
41
42

$link = mysql_connect('localhost', 'user_name', 'password');
if (!$link) {
   die('Not connected : ' . mysql_error());
}
 
// make foo the current db
$db_selected = mysql_select_db('bad_behavior', $link);
if (!$db_selected) {
   die ('Can\'t use foo : ' . mysql_error());
}

Next, you need to populate the skeletal functions with their appropriate code:

60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100

// Return current time in the format preferred by your database.
function bb2_db_date() {
	return gmdate('Y-m-d H:i:s');	// Example is MySQL format
}
 
// Return affected rows from most recent query.
function bb2_db_affected_rows() {
	return mysql_affected_rows();
}
 
// Escape a string for database usage
function bb2_db_escape($string) {
	return mysql_real_escape_string($string);
}
 
// Return the number of rows in a particular query.
function bb2_db_num_rows($result) {
	if ($result !== FALSE)
		return mysql_num_rows($result);
	return 0;
}
 
// Run a query and return the results, if any.
// Should return FALSE if an error occurred.
// Bad Behavior will use the return value here in other callbacks.
function bb2_db_query($query) {
	return mysql_query($query);
}
 
// Return all rows in a particular query.
// Should contain an array of all rows generated by calling mysql_fetch_assoc()
// or equivalent and appending the result of each call to an array.
function bb2_db_rows($result) {
	return mysql_fetch_assoc();
}
 
// Return emergency contact email address.
function bb2_email() {
	// return "example@example.com";	// You need to change this.
	return "badbots@ioerror.us";	// You need to change this.
}

Then you’ll also need to place a call to close the database connection at the bottom of the script. Place the below on the very last line:

160

mysql_close();

Doing that will make sure you don’t have any rogue connections eating up your queue.

Once the above is complete you should have a fully setup and working install of Bad Behavior.

In case anyone has any issues with the above I’ve prepared a stand alone version of the script anyone can download bad-behavior-generic.

It should also be noted that incorporating a database into your Bad Bahavior installation ups the load on every request (which may be why it’s not in there by default). You just have to choose whether the need for logging out weighs the increased load. For me, it did.