[Solved]: Files to delete after installation? [Solved]: Files to delete after installation?
 

News:

CPG Release 1.6.26
Correct PHP8.2 issues with user and language managers.
Additional fixes for PHP 8.2
Correct PHP8 error with SMF 2.0 bridge.
Correct IPTC supplimental category parsing.
Download and info HERE

Main Menu

[Solved]: Files to delete after installation?

Started by jenepherre, April 16, 2004, 04:53:21 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

jenepherre

I know with other PHP scripts/programs I've used, you're usually told to delete the config.php file to prevent possible security loopholes.  I didn't see anything saying what files should be deleted after installation in the install instructions (which seem very... brief compared to the install instructions for the last version... am I wrong about that?  I wish you went into more detail...).  :|

Can you tell me which files should be deleted, if any, and also which files are safe to delete?  I assume the docs folder doesn't actually have to be on the server, right?  What else?  :?:

Thanks in advance,
Jen
===============================
Jen Robertson
B/J Journal Archives: http://bj.irishcaelan.com/
jen_robertson@sbcglobal.net
===============================
"The only constant is change."
 - Trance Gemini,
"Gene Roddenberry's Andromeda"
=================================
Jen Robertson
=================================
I don't want to explain, I just want to dance.

hyperion

You can leave all files on the server if you wish, as Coppermine locks the installation once it has run.

However, if you wish to save space, you can get rid of install.php, the documentation, and any languages or themes you are not using. Also, xp_publish.php can be removed if you do not want to allow uploads using the XP Publishing utitlity.

You can remove the config.php if you desire, but you will need to put it back anytime you want to change the gallery config.  It is secure, so there is really no need.

I know of one user who had someone try to brute-force attack the login.php script (30,000 requests per hour), so he removed it (he was the only user).  If you needed to login, you could put it back.

Again, all the files have authentication controls, so it is not really necessary to remove anything.

Directory permissions are more important, and you should basically avoid 777 permissions whenever possible.
"Then, Fletch," that bright creature said to him, and the voice was very kind, "let's begin with level flight . . . ."

-Richard Bach, Jonathan Livingston Seagull

(https://coppermine-gallery.com/forum/proxy.php?request=http%3A%2F%2Fwww.mozilla.org%2Fproducts%2Ffirefox%2Fbuttons%2Fgetfirefox_small.png&hash=9f6d645801cbc882a52f0ee76cfeda02625fc537)

jenepherre

Thanks so much!  Just the info I needed.   :)
=================================
Jen Robertson
=================================
I don't want to explain, I just want to dance.