Securing 3.2 Install

[sk4sk4]

Are there any suggested actions to secure an installation of 3.2? I remember it was suggested for 3.1x per your TCH setup instructions to create a .htaccess file in the mt/ directory that contained the code:

 

Options All -Indexes

<Files mt.cfg>

<Limit GET>

deny from all

</Limit>

</Files>

 

Does this still apply to 3.2 and/or are there any additional things that can be done? Thanks!

[TweezerMan]

If you've performed a new installation of MT 3.2, or upgraded from an older version but decided to go with the new name of the config file, 'mt.cfg' should be replaced with 'mt-config.cgi'.

 

It is not recommended that you use MT-Blacklist with MT 3.2, but use the SpamLookup plugin included with MT 3.2 instead.