Ruleset updating mechanism to fetch, verify the authenticity of, and apply new ruleset databases

This pull request contains all of the commits I (Zack Mullaly) have made over the course of the Summer of 2014 to build a secure ruleset updating mechanism for my Google Summer of Code 2014 project.
There are still some details (such as a public key) that need to be filled in by whoever now is the primary maintainer of the project, but the feature should be functional once the TODOs are taken care of.
You're correct that we can't defend against arbitrary local malware using filename nonces; however, the purpose of this is to defend against an attacker exploiting a program that can save files to /tmp but not enumerate the files that are there already.