The Greymatter script, while excellent in almost every aspect (A tip of the Farlopsian hat to Mr. Grey!), needs a little help so that, after installation, it runs in a secure fashion. For example, many of the forms it uses send the author’s username and password as unencrypted text between client and server. Actually this is problem that many perl server scripts have, and if you don’t take precautions, you’re one packet sniff or hack away from getting your script and maybe the rest of your server, owned.
Anyway, I imagine a lot of the savvy Web builders knew this upon installation and thus took cautionary measures. However there might be some inexperienced users out there who’ve just installed Greymatter and may be unaware of how to stop the hack Dangerous Monkey publicized.
Pretty simple to state:
- Make certain that the directory Greymatter generates pages to forbids file structure browsing to unauthorized users. Don’t do this in other words. This can be done via .htaccess or by putting an default page in place.
Don’t use the IE-based bookmarklets Greymatter offers, at all. And erase any files labeled gmrightclick[some number].reg in the journal directory to prevent dictionary attacks.
To secure Greymatter, or any server-side script in general:
- Make certain all scripts are installed in directories that forbid file structure browsing to unauthorized users.
- Tweak scripts and forms to use SSL for any password, username, credit card numbers, SSN or other information you don’t want packet sniffing to see. Unfortunately not everyone will be running their site on a server which allows users to use SSL. If not, well, I guess you’ll have to change your password frequently.
- Make certain that any script passwords and usernames don’t correspond to root or system usernames and passwords.