Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#1930 safe_mode: why not try using locales?

I18n
closed-duplicate
nobody
None
5
2005-10-27
2005-10-27
Rafal Wijata
No

On my php, I have set safe_mode to true, allowed LC*
LANG* envvars to be set, and then in SM code disabled
the safe_mode check.
Locales and translations works fine.
Why SM assumes that it's impossible while in safe_mode?
Maybe it's better to check if LC_ var can be set
instead of checking for safe_mode ?

Discussion

  • Tomas Kuliavas
    Tomas Kuliavas
    2005-10-27

    Logged In: YES
    user_id=225877

    See bug 1334412 on internationalization tracker.

    We would have to check for all possible variable names and
    wildcards in safe_mode_allowed_env_vars and
    safe_mode_protected_env_vars.

    Theoretically we might just hide putenv errors with @.

    Closing dublicate bug report. Use 1334412 bug for feedback.

     
  • Tomas Kuliavas
    Tomas Kuliavas
    2005-10-27

    • status: open --> closed-duplicate
     
  • Logged In: NO

    > Theoretically we might just hide putenv errors with @.
    That would be very useful for people like me.
    I need php to be run in safe_mode, but I dont see anything
    wrong in allowing LC_* LANG TZ* vars to be changed.