Stephen Dewey (2009-07-13 12:39:04)

curl_setopt() will not allow you to activate CURLOPT_FOLLOWLOCATION when in safe mode.

tschmieder at bitworks dot de (2007-09-22 06:04:58)

refers to the previuos posting of
bananarama
15-May-2006 10:11
"all file-handling and -management functions are restricted, just in case someones wondering why they're not listed here.
a script can run these functions on files without errors, if the files were created (are owned) by the same UID, the script was created (is owned) by."
.... or if the directory, in which the file is located, has the same UID as the script, which tries to use a file in that directory...

bananarama (2006-05-15 01:11:28)

all file-handling and -management functions are restricted, just in case someones wondering why they're not listed here.
a script can run these functions on files without errors, if the files were created (are owned) by the same UID, the script was created (is owned) by.

example:
you upload a script, it is owned by UID 720. you upload a picture, it is owned by UID 720. the script creates a thumbnail of the picture. the thumb is owned by UID 30 (the server/apache). this makes it impossible (?) to run a gallery script, which checks for newly uploaded pictures in order to create and display thumbs of them if you want to check, if a thumbnail already exists. the script would be owned by UID 720, the thumb by UID 30.
you could upload a script which creates a file (e.g. from a text file) with .php ending. this script would be owned by UID 30 and could access the thumbs, but it couldnt read the upload pictures.

<? 
  $data = fread(fopen("test.txt", "r"), filesize("test.txt")); 
   
  $file = "test.php";   
  if (!$file_handle = fopen($file,"a")) { echo "Cannot open file"; }  
  if (!fwrite($file_handle, $data)) { echo "Cannot write to file"; }    
  fclose($file_handle);
  
  chmod("test.php", 0777);
?>

zauker (2006-03-21 14:57:20)

The SAFE_MODE handling of glob() needs a checkup for security reasons.
In short - always with SAFE_MODE on:
1) glob() can still fetch all filenames in a directory not owned by the
same UID as the user, if just the first file in the directory (or more
specific, the glob-pattern) happens to be owned by the same user as the
PHP-script.
2a) No warning is raised if glob is used on another owner's directory
and there is no match.
2b) In those cases where SAFE_MODE correctly prohibits glob() from
fetching a list of files, the warning still discloses the first
filename.
Solution: glob() in SAFE_MODE should be restricted in the same way as
opendir() is
see the link http://bugs.php.net/bug.php?id=28932

Jan (2005-10-23 02:46:22)

It seems that glob and file_exists functions are also restricted in safe-mode.