Guest Posted March 20, 2003 Share Posted March 20, 2003 I'm just stumbled upon this site/software, and first off, I just want to say that this is incredible! Everything that I have seen so far makes me wonder why I haven't heard of osCommerce before. That being said, I have one problem with my installation (v2.2 ms1): my Admin seems OK, but when I go to my store, at the top in a pink band it says: Warning: I am able to write to the configuration file: domain setup here/catalog/includes/configure.php. This is a potential security risk - please set the right user permissions on this file. I understand what it means, and I have gone throught the Wiki documentation (it says to chmod the file to 644), I have set chmod to 644, but still the pink banner. Help!! (many, MANY thanks in advance!) JD Link to comment Share on other sites More sharing options...
Acemang Posted March 20, 2003 Share Posted March 20, 2003 I had same problem with 644. I changed to 444 and now its ok. "Long live the new Flesh" ________________________________________ http://www.personalcare.com.pt Link to comment Share on other sites More sharing options...
Guest Posted March 20, 2003 Share Posted March 20, 2003 Nope, still doesn't work (I think at some point I had tried 444)... Too many number combinations! Link to comment Share on other sites More sharing options...
Acemang Posted March 20, 2003 Share Posted March 20, 2003 How did you chmod you file? with an ftp program? if I change there to 444 and press f5(to refresh) the file dont change. you need to have shell acess to change it. you can remove yourself the warning to false that way it want be displayed. "Long live the new Flesh" ________________________________________ http://www.personalcare.com.pt Link to comment Share on other sites More sharing options...
Guest Posted March 20, 2003 Share Posted March 20, 2003 DOH! Yep, you're right - I was doing it through an FTP app, and it doesn't change from 644 to 444. Now the problem is that I don't have shell access to my server (they don't support that, which makes it fun to work with the db) I think that I will have to get them to do something about that, since I don't like to think that the file is susceptable - but for the time being I will disable it like you suggested. Thanks for your help! Link to comment Share on other sites More sharing options...
Acemang Posted March 20, 2003 Share Posted March 20, 2003 jdlewis, there is one solution for your problem if you dont have shell access. get phpshell http://gimpster.com/downloads/phpshell/ Install in your server and run phpshell.php. Read the Install file and the Readme. phpshell it will let you chmod 444 file.php I know because I dont have shell access and I use this :wink: "Long live the new Flesh" ________________________________________ http://www.personalcare.com.pt Link to comment Share on other sites More sharing options...
carrzkiss Posted March 20, 2003 Share Posted March 20, 2003 Warning: I am able to write to the configuration file: domain setup here/catalog/includes/configure.php. This is a potential security risk - please set the right user permissions on this file. If you are on a "Windows Server" i.e. WinNT 4 / Win2k / WinXP Server Family. Right Click on the File and choose "Read Only" And this will get rid of the error that you are getting, this is what I had ask a few days ago, and what was told to me, and it worked like a charm, Wayne Carrz-Fox-Fire Promotions Thank You Wayne & Carr Barron Link to comment Share on other sites More sharing options...
Guest Posted March 21, 2003 Share Posted March 21, 2003 jdlewis,there is one solution for your problem if you dont have shell access. get phpshell http://gimpster.com/downloads/phpshell/ Awesome! Installed the file, set permission to 444, and now all is good in my world - no more pink banner and configure.php is safe. Thanks!! Link to comment Share on other sites More sharing options...
Guest Posted March 21, 2003 Share Posted March 21, 2003 If you are on a "Windows Server" i.e. WinNT 4 / Win2k / WinXP Server Family.Right Click on the File and choose "Read Only" And this will get rid of the error that you are getting. Thanks, but I'm on Apache. Good to know, though, in case I do an install on a client's WinXX machine! Link to comment Share on other sites More sharing options...
New 
Recommended Posts
Archived
This topic is now archived and is closed to further replies.