September 2008

Securing TYPO3 the nazi way

Filesystem permissions

How does the UNIX-filesystem permissions interact with TYPO3?

The answer is simple: TYPO3 runs as the user, PHP "runs" as. This could depend on the httpd.conf file of Apache. Default is "nobody" as far as I know. On Debian installations it is "www-data".

The main thing is, that TYPO3 must be able to write to certain folders in order for the file-administration to work. This means that after installation of TYPO3, you should alter the user of the scripts and folders, probably with the "chown" command.

If you have access to the webserver through FTP, you might be uploading scripts with yourself as user. These scripts might be executable by Apache as PHP-scripts but when the scripts need to write to eg. the upload-folder, this folder might be owned by "you" and thereby TYPO3 does not work. Therefore; the folders TYPO3 need write-access to must be writeable by the Apache-user.

Folders that requires write access are fileadmin/* and uploads/* for the frontend and typo3temp/ for both frontend and backend. Furthermore for extensions directories typo3/ext/ and typo3conf/ and sub directories must be writeable for PHP as well.

Symantec joins the online storage industry as SaaS competitor... Is it any good? What makes it different then others?

Symantec is probably one of the most forward facing security company that is basically a household name.  Here just recently they have released what looks to be a little outside of their normal product line that they have offered in the past which is pretty surprising and scary at the same time.  The Symantec Protection Network application is a SaaS (Storage as a Service) client that gives you the ability to secure your critical data to their secure datacenter in an automated fashion.  Those who know me I have an extensive backround in this exact type of industry, and to have

Current Projects

Put Project list and information here

DataHEALTH Virtual Office
DataHEALTH CMS / E-commerce

Home Budget SAN Environment
DYI Server Rack

OpenSolaris 2008.5 Evaluation
ESXi Evaluation
Drupal CMS Tutorials
TYPO3 CMS Tutorials
XenDesktop Tutorials

Using perl to automate a common telnet session

I have been fighting with a server that is running out of resources at the data center, and it is impossible for me to access the machine remotely and kill the offending process some of the times.   Since the machine is connected to a managed power distribution unit, I wanted to find a way that I could script of the power cycling of the outlet.   My first thought was to see if I could do it using IPSentry the server alert and monitoring system that we have in place right now, which is basically a Windows version of Nagios but not near as flexible.  I found that none