dotcom22 Posted February 12, 2009 Share Posted February 12, 2009 Hi all I want install whmcs right now and before I have read wiki here: http://wiki.whmcs.com/Furthur_Security_Steps It is write if my server run suphp (and it's the case) I don' need to set my folder to 777...So that mean my folder are already writable with 755 permission also for anybody of just for the script ?? I need to move this 3 folder "attachments", "downloads" and "templates_c" in home or not ??? For what it is folder "template_c" ??? It is empty folder.. thanks in advance... 0 Quote Link to comment Share on other sites More sharing options...
DataHosts Posted February 12, 2009 Share Posted February 12, 2009 I need to move this 3 folder "attachments", "downloads" and "templates_c" in home or not ??? These folders are withing the WHMCS folder you create For what it is folder "template_c" ??? It is empty folder.. This keeps the cache smarty templates. It is empty to start but gets full over time. You will need to delete the files manually ever once in awhile 0 Quote Link to comment Share on other sites More sharing options...
dotcom22 Posted February 12, 2009 Author Share Posted February 12, 2009 thanks for reply... I just need also to understand more what is it suphp... My server run suphp...so for what I understand that mean the more higher permission level allowed are 755 and it will be the same of 777 ? That mean hackers can be able to see and modify files or not ? thanks 0 Quote Link to comment Share on other sites More sharing options...
striddy Posted February 13, 2009 Share Posted February 13, 2009 I just need also to understand more what is it suphp... My server run suphp... http://letmegooglethatforyou.com/?q=suPHP 0 Quote Link to comment Share on other sites More sharing options...
XN-Matt Posted February 13, 2009 Share Posted February 13, 2009 In essence. Generally when you try and set certain files to 777 and access them - apache will ISE on you. Folders should be 644 and files 755 from what I remember when using suPHP. 0 Quote Link to comment Share on other sites More sharing options...
HostOrca Posted February 13, 2009 Share Posted February 13, 2009 (edited) In essence. Generally when you try and set certain files to 777 and access them - apache will ISE on you. Folders should be 644 and files 755 from what I remember when using suPHP. I think it's the other way around, folders 755, files 644 With suphp all scripts run as the account owner, rather than "nobody", so they can write to the folder/files because they "own" them, so only the script can write to the folder/file. Hackers can not. Edited February 13, 2009 by HostOrca 0 Quote Link to comment Share on other sites More sharing options...
bear Posted February 13, 2009 Share Posted February 13, 2009 apache will ISE on you. Had to ponder that one for a moment. Internal Server Error. .Gareth is correct 0 Quote Link to comment Share on other sites More sharing options...
XN-Matt Posted February 13, 2009 Share Posted February 13, 2009 Heh.. Indeed that is the wrong way around. I think that must have been a fastest-post-first. Whoops With suphp all scripts run as the account owner, rather than "nobody", so they can write to the folder/files because they "own" them, so only the script can write to the folder/file. Hackers can not. Unless you have other scripts within the same user account space (such as a parked/addon/sub domain) that have a vulnerability which could then edit/affect other files with the same UID. 0 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.