So I just wrote this in 2 minutes so I could kill some things in /etc and /home and be done with it. Short and simple, don’t you think?

My suggestion is to come up with a system that makes sense to you. If it asks for your favorite pet’s name, maybe the answer could be “nail biting” or “chocolate lab”. You just have to remember how you translated the secret question.

The model has strong principals, but the goals blow my mind. I’ll explain in a minute, check out the principles first.

The problem is, hexdump will give you 16 ascii characters surrounded by pipes and then a newline before printing the next 16. You can’t search for long strings that way…

You might want to do this to make sure a set of configuration files don’t get changed, or to figure out which files get changed when you build that random source code as root! (note to self: don’t make as root unless you have to, rpmbuild is bad enough!)

This has worked for me for as long as I can remember. To get around a blocked site, as long as i’m trying to view flash or other 2.0 stuff, I just translate english pages from spanish to english. What happens is any english (which is everything) just gets passed right on, but the results come from google instead of the target site.

Generate a gpg keypair. Check /dev/random to make sure you’re getting some output. If you dont get any standard output when you run this, ctrl-c and you will see 0+1 records in/out. This means there is a problem with your /dev/random device. Here’s the fix…

Install Bro - Network-based Intrusion Detection, on Fedora or Ubuntu. Bro will get installed in /usr/local/bro/ by default, unless you specified a prefix in configure as I did. I also created a bro user and group to own everything and did the make as that bro user.

Bro is intended for use by sites requiring flexible, highly customizable intrusion detection. It is important to understand that Bro has been developed primarily as a research platform for intrusion detection and traffic analysis. It is not intended for someone seeking an “out of the box” solution. Bro is designed for use by Unix experts who place a premium on the ability to extend an intrusion detection system with new functionality as needed, which can greatly aid with tracking evolving attacker techniques as well as inevitable changes to a site’s environment and security policy requirements.

If you want to store a mix of encrypted and unencrypted files under the same area, choose plaintext passthrough, otherwise choose the default, no. I suggest an all or nothing approach, as it can get confusing as to which files are encrypted especially when they’re binary! (With ascii text files you can just cat a file and tell if it’s encrypted or not.)