Tickets :: [#6341] Config Backup Files (all applications)

6.0.0-beta1

7/4/25

Summary	Config Backup Files (all applications)
Queue	Horde Base
Queue Version	HEAD
Type	Enhancement
State	Resolved
Priority	1. Low
Owners	chuck (at) horde (dot) org
Requester	rdorfner (at) sysdesign-edv (dot) de
Created	02/28/2008 (6336 days ago)
Due
Updated	11/17/2008 (6073 days ago)
Assigned	02/28/2008 (6336 days ago)
Resolved	02/28/2008 (6336 days ago)
Milestone
Patch	No

11/17/2008 03:58:59 PM	Chuck Hagenbuch	Deleted Original Message

11/17/2008 05:58:36 AM	mrhmtallh (at) yahoo (dot) (dot) com	Comment #4 New Attachment: Grandma_Evil.jpg	Reply to this comment
Done. Hacked BY rhmtallh www.cinema.43i.net

02/28/2008 11:26:38 PM	Chuck Hagenbuch	Comment #3 State ⇒ Resolved	Reply to this comment
Done.

02/28/2008 07:37:07 PM	Chuck Hagenbuch	Comment #2 State ⇒ Assigned Assigned to Chuck Hagenbuch	Reply to this comment
Makes sense to me.

02/28/2008 12:53:01 PM	rdorfner (at) sysdesign-edv (dot) de	Comment #1 Priority ⇒ 1. Low Type ⇒ Enhancement Summary ⇒ Config Backup Files (all applications) Queue ⇒ Horde Base State ⇒ New	Reply to this comment
It's dangerously to create a backup files called conf.php.bak after configuration in a horde application has been changed. A general webserver will deliver the backup file (e.g. http://myserver.com/hordedir/config/config.php.bak) without any restrictions like htaccess etc. It would be better to name the files conf.bak.php to avoid this.