Feelay 0 Report post Posted March 9, 2008 Hey!How can i make my included files 100% safe.Like if I include a file witht his code.. include "bla.php"; How can i make it 100% safe? I know I must close the php tags in the included files. but what more =? Share this post Link to post Share on other sites
faulty.lee 0 Report post Posted March 9, 2008 What do you mean by safe? Share this post Link to post Share on other sites
Feelay 0 Report post Posted March 9, 2008 (edited) No one can view the code, or even know that they excist. that should be enough. Edited March 9, 2008 by Feelay (see edit history) Share this post Link to post Share on other sites
faulty.lee 0 Report post Posted March 9, 2008 No one can actually view your php file in the first place. Unless you mistakenly configure the server to serve php pages as html, then it would just display them as plain text. Other wise, no way.The other thing is, most server serve the include folder above the www/html root, thus making it only visible to the code, but no way to access it from the outside world. yourroot/www/your html files --> http://yourserver/index.tmlyourroot/cgi-bin <-- No way to see this from outside, unless you can actually do this, (http://yourserver/../cgi-bin) which is not possible Share this post Link to post Share on other sites
Mordent 0 Report post Posted March 9, 2008 I'm no expert, but surely a simple check to see if the include is being accessed from another page on your site would be enough? If so, just define a variable at the start of the script in which you use the include. Then, in the included file, check that whatever variable you used is defined, and if not simply die() (i.e. don't process the script). Possible error messages would include "This file cannot be directly accessed!" or the like.Anything wrong with this method of doing things? Share this post Link to post Share on other sites
TavoxPeru 0 Report post Posted March 12, 2008 (edited) I'm not 100% sure but you can use the define and defined php functions for securing your include files, first define a constant in the caller page and then verifiy if it is defined in the include file. Caller File: <?phpdefine( "MY_ACCESS_CODE", true );include("includefile.php");?>Included File (includefile.php): <?phpdefined( 'MY_ACCESS_CODE' ) or die( 'Direct Access to this location is not allowed.' );?>EDIT:The solution given by faulty.lee is another good one.You can use session variables.The code that i post was taken from this topic A Simple Checking & Validation PHP Script check it out for more information about this solution.Best regards, Edited March 12, 2008 by TavoxPeru (see edit history) Share this post Link to post Share on other sites
Mordent 0 Report post Posted March 12, 2008 I'm not 100% sure but you can use the define and defined php functions for securing your include files, first define a constant in the caller page and then verifiy if it is defined in the include file.Caller File: <?phpdefine( "MY_ACCESS_CODE", true );include("includefile.php");?>Included File (includefile.php):<?phpdefined( 'MY_ACCESS_CODE' ) or die( 'Direct Access to this location is not allowed.' );?>Best regards,*nods* That'd be the way I described above, but in code format. One point to bear in mind is that you'd need to define the access code once only per page (if you have more than one include). I doubt it would hurt to define it more than once, but it's just messy coding in my opinion. Share this post Link to post Share on other sites
Dizzy1405241556 0 Report post Posted March 12, 2008 it really ccompicated but easy if you know how get someone you know to help you out make sure you know what your doing Share this post Link to post Share on other sites
vujsa 0 Report post Posted March 15, 2008 Well, I realize that this dicussion may be resolved but I figured it couldn't hurt to provide the information anyway. There actually is a tutorial about the suject on the forums: CMS103 - Securing Your Website, Keeping your included files from being accessed directly. Actually, I see that Feelay has read the article already. Anyway, it discusses this situation. One additional security measure for your files is to prevent them from being seen altogether. Basically, do not allow anyone to view the files in a given directory. As most of you know, on most servers if there isn't and index file (index.html) then the server makes a nice directory listing of every file on that folder! To prevent this, you can change you server setting or simply add a blank index.html file to EVERY folder on your server. If you want to get creative, you could use the following index.html file instead: <html><head><title>You Aren't Allowed Here!</title></head><body>Yeah, like we were just going to let you look around and try to see all of our super secret files and image!<br />Not to worry, they all look a lot better when viewed through the main page: <a href="domain.com/index.php">Main Page</a></body></html> Alternately, you could simply add the following to the .htaccess file in the parent directory of the folders you do not want to show indexes on: Options -Indexes Hope this helps, vujsa Share this post Link to post Share on other sites
Feelay 0 Report post Posted March 15, 2008 Thanks Vujsa :)And yes. I remebered that I had read your topic, when I saw TavoxPeru's post Share this post Link to post Share on other sites
Quatrux 4 Report post Posted March 16, 2008 If you really want to protect your php files, include it from a directory where there is a .htaccess file with "deny from all", php still will be able to include it and execute, moreover, that directory could be outside public_html or www directory whatever, I mean somewhere, before public_html/ that it wouldn't be directly accessible to users, but php will still be able to include them. Share this post Link to post Share on other sites
