Results 1 to 5 of 5
  1. #1
    Join Date
    Jan 2007
    Posts
    584

  2. #2
    Join Date
    Mar 2003
    Location
    Canada
    Posts
    8,910
    You could copy your server php.ini to their public_html directory then add mail to the disable_function's directive. If you set the php.ini ownership as root, that *should* prevent the user from removing or modifying the php.ini file.
    Patrick William | RACK911 Labs | Software Security Auditing
    400+ Vulnerabilities Found - Quote @ https://www.RACK911Labs.com

    www.HostingSecList.com - Security notices for the hosting community.

  3. #3
    Have anyone noticed php.ini will work only on the folder in which it is, not on sub folders. When cpanel use phpsuexec, it worked for sub folders too. With suPHP, i think php.ini only work on current folder.

  4. #4
    Join Date
    Mar 2003
    Location
    Canada
    Posts
    8,910
    Quote Originally Posted by flashwebhost View Post
    With suPHP, i think php.ini only work on current folder.
    With a custom php.ini under the public_html directory, it will work under subdirectories when used in conjunction with suPHP, at least with our FreeBSD setup.

    I think that's how it's supposed to work anyway ... unless it's different under Linux?
    Patrick William | RACK911 Labs | Software Security Auditing
    400+ Vulnerabilities Found - Quote @ https://www.RACK911Labs.com

    www.HostingSecList.com - Security notices for the hosting community.

  5. #5
    Check

    disable_functions = mail

    http://www.wehost4u.net/phpinfo.php

    php.ini is in public_html folder

    Check phpinfo in subfolder with no php.ini

    http://www.wehost4u.net/test_php/phpinfo.php

    See sub folder listing to verify

    http://www.wehost4u.net/test_php/

    This problem i faced on a different server than this. So i think its same for all new cpanel boxes.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •