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.

Enabling aliases in Lighttpd is even easier than in Apache. If you want to browse your app without having to include the trailing slash, then make sure you didn’t include trailing slashes in your alias definitions (my alias.url’s above don’t have the trailing slash). Many examples show something like /doc/ => “/usr/share/doc/” but then it won’t find the index.php or index.html on its own.

Removing the pcspkr module is fine for an instant halt to all beeping noises coming out of the machine, and sure you could just add this to your profile in .bashrc or .bash_profile, But the right/best/most complete way is to do it system-wide where it doesn’t even get enabled in the first place by blacklisting it in the modprobe configuration.

How do you put pictures in your Outlook email signature so that everyone you send email to gets a little picture, and when they click on it, it sends them to a special website of your choosing? Well mom, that’s easy! Here’s how. But keep in mind, your screens may look a little different than mine, but it’s the same general get-r-dun process even if you’re using an older version of Outlook or Windows. I’m on 2008 server, so your mileage may vary.

So now I know this certificate is blessed by my client, I can try to use it to connect. But let’s say I try to use a self-signed certificate or another cert that’s not trusted… And using a self-signed certificate, you should see something like this… If it’s a trust issue, perhaps the certificate is valid, but it just can’t find the CA or intermediate certificate… But, if everythings working correctly, your client should connect just fine. And it will look something like this, with a big fat Verify return code: 0 (ok) at the end.

If you submit an SSL certificate request for your Apache/Lighttpd web server to a Certificate Authority (CA) on a Windows Domain Controller, you might have to convert your resulting binary DER formatted Security Certificate into PEM so Apache or Lighttpd can understand it.

I wanted to simplify the toolbox for a special purpose wiki, but everywhere I searched all I could find was how to change the name of the toolbox, or how to show it only to logged in users, etc. To delete one of the default toolbox links, just change the data value to something it will never see. You could remove the if statements completely for each link you want removed, or just change the data value to something that will never result in entering the if statement. It’s less intrusive than removing the code completely. Either way, you won’t be deleting the toolbox function, only the link from the interface — which is exactly what I wanted. If you want to trim the navigation part of the sidebar, that’s built right in. Just go to Mediawiki:Sidebar and edit that page.

I read in a bunch of places that you can’t use HTTP["scheme"] to redirect http:80 traffic to https:443 without using 2-3 levels of nesting with socket and host. But that’s just not true. The only reason it doesn’t work at first is because http is a subset of https, so be more specific with http$ and it works with just one line in lighttpd.conf.

Now edit the lighttpd.conf configuration file to enable ssl. Use the public facing interface’s IP address instead of mine, unless yours happens to be 192.168.1.2 too! And nmap or netstat will let you know it’s listening on port 443

Enabling LDAP authentication should take you about 2 minutes, unless you type with just 2 fingers. Then maybe 3 or 4. …If you don’t allow anonymous connections to your ldap, give it a user/password combination that has enough privs to do the lookups, or just use your master account if you’re just testing or don’t really care. … Now tell it what parts of your webserver you want to protect and how. You can specify any string you’d like for the realm. Here I require an LDAP user account name and password just to get to the wiki main page, and only admin can see the server-config page… Restart lighttpd and you’re done.