The default out-of-the-box installation should delete any additional anonymous users after installation and disallow remote logins completely, but it doesn’t. At least all you have to do is run the mysql_secure_installation script to do so.

If you want to add a user to all of the components in bugzilla, you don’t have to go through the gui. In fact, you can change just about anything in bugzilla by connecting to the database directly and modifying the tables. I find this much faster than repetitively navigating through the web front end. Connect to the database, match up user id’s to user names, figure out which components you want to modify, then update the component_cc table. Step-by-step.

Start by installing all of the required dependencies. Here’s the list, but your specific versions may vary. I’m just letting yum install all the latest packages. And I finish by running a “yum update -y” to get the whole system up to date. There are newer versions of the libnet package available, but you specifically need libnet-1.0.2a.tar.gz. You can search and find a bunch of mirrors or try the one I used below: Now download the snort source.

Before I get to the problem, here’s the interesting part. If you list the files in /var/lib/rpm/ you will see the flat berkeley database files, but not all of them. And I didn’t notice there was one missing until I went to fix it. I’m not sure what caused/causes this, but I found a pretty simple solution.

If your dump was performed with the “–clean” option, you can skip the reinitializing of your databases to avoid duplicating data. This option, used with the “pg_dumpall” command will cause the restore to clean out all the objects in the database before performing the restore. If you didn’t include this option, then just delete the data directory and reinitialize the database as shown below.

Easy, just go into the database and delete the row from mwuser, right? wrong. If you’re using phpPgAdmin pgadmin3 or some other tool, you should get a nice message letting you know exactly which constraint would be violated if it actually let you do that dave. In my case, I had a user that had updated a few pages, so I just needed to change the revision table so that he wasn’t referenced anymore.