Another SILLY_SAFE_MODE observation Another SILLY_SAFE_MODE observation
 

News:

cpg1.5.48 Security release - upgrade mandatory!
The Coppermine development team is releasing a security update for Coppermine in order to counter a recently discovered vulnerability. It is important that all users who run version cpg1.5.46 or older update to this latest version as soon as possible.
[more]

Main Menu

Another SILLY_SAFE_MODE observation

Started by redwoodhead, January 22, 2009, 12:48:43 AM

Previous topic - Next topic

0 Members and 2 Guests are viewing this topic.

redwoodhead

Not a big deal, and perhaps obvious, but don't do what I did.

Many threads here point out the necessity of including the line
define ( 'SILLY_SAFE_MODE' , 1 ) ;
in config.inc.php in order to put Coppermine into SILLY_SAFE_MODE.

What does NOT work is to change the "1" to a "0" to reverse this mode setting.  Just remove the line.  The code checks for SILLY_SAFE_MODE being defined, not what the value is.  Changing the "1" to "0" will leave it just as defined as it was.

(The Fantastico installation that installed Coppermine on my webhost set this.  It wasn't my idea!)

Fabricio Ferrero

Quote(The Fantastico installation that installed Coppermine on my webhost set this.  It wasn't my idea!)
That's why it's totally not recommended to use it.
Read Docs and Search the Forum before posting. - Soporte en español
--*--
Fabricio Ferrero's Website

Catching up! :)

Joachim Müller

Quote from: redwoodhead on January 22, 2009, 12:48:43 AM
What does NOT work is to change the "1" to a "0" to reverse this mode setting.  Just remove the line.  The code checks for SILLY_SAFE_MODE being defined, not what the value is.  Changing the "1" to "0" will leave it just as defined as it was.
That's correct - that's how constants work and are being used in coppermine. Thanks for your notion to mention this in case it was not clear for others.

Quote from: redwoodhead on January 22, 2009, 12:48:43 AM
The Fantastico installation that installed Coppermine on my webhost set this.  It wasn't my idea!
As Fabri suggested: we're not fond of auto-installers, and particularly not of Fantastico. Fantastico-driven installs go unsupported by us. Complain @ Netenberg (the creators of Fantastico).