RESOURCE CENTER
KICK ASS OFFERS
MOST COMMENTED ARTICLES
NewsComcast Filtering-For-Profit: A Three-Phase Plan to 'Right-Size' Consumer Bandwidth
1 NEW COMMENT(S) | 54 TOTAL COMMENTS
THIS MONTH's ISSUE
FEATURE Awesome Upgrades: The best PC upgrades in every price range.HOW TO Connect your PC to your surround-sound audio systemProtect Your PC We put 10 of the most popular antivirus programs to the test to see which will protect you best. Android Revealed Find out how the Google-powered HTC G1 stacks up against its rivals.






How To: Host Your Blog at Home
Posted 09/04/2007 at 11:53:06am
I would just like to mention that I think port forwarding MySQL (336) is completely unnecessary and presents an unwelcomed security risk. With this configuration, MySQL and apache reside on the same server, negating the need for any remote administration. Even opening port 336 (MySQL) in step 2, on the Windows Firewall is unnecessary as all connections to "localhost" are not blocked. Remote database administration can just as easily be done through phpmyadmin. However, this tool can also pose a security risk. I don't think XAMPP limits access to this directory. Placing the following text in a file called .htaccess in the xampp/phpmyadmin directory *should* do the trick: # ------------------------------------- Order allow, deny Deny from all Allow from localhost Allow from 127.0.0.1 # ------------------------------------- Disclaimer: I'm rusty with .htaccess and this may not work as desired. It is not a foolproof method of security but it should limit unwanted incursions into your database. -- Stux