SamleSide

noen php-sider

phpftp phpftp_source notftp
PhpMyExplorer?
freshmeat.org
mount -o loop /mnt/cdrom/iso /mnt/iso/1/CDplate..

.httaccess php-tips

Another way to stop a user from looking at or executing the files read by include() or require() is to use a different file extension for them (i.e. *.inc) and add the following to your apache configuration:
<Files ~ "\.inc$">
   Order allow,deny
   Deny from all
   Satisfy All
</Files>
They won't execute unless used in a include() or require() since they don't have the *.php extension, and the server won't serve them up as text/plain with the directive above.
ocrow at simplexity dot net
02-Jul-2003 05 16
If your PHP pages include() or require() files that live within the web server document root, for example library files in the same directory as the PHP pages, you must account for the possibility that attackers may call those library files directly.
Any program level code in the library files (ie code not part of function definitions) will be directly executable by the caller outside of the scope of the intended calling sequence. An attacker may be able to leverage this ability to cause unintended effects.
The most robust way to guard against this possibility is to prevent your webserver from calling the library scripts directly, either by moving them out of the document root, or by putting them in a folder configured to refuse web server access. With Apache for example, create a .htaccess file in the library script folder with these directives:
Order Allow,Deny
Deny from any