[Tickets #12788] access to /etc/resolv.conf not allowed per open_basedir directive

[noreply at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/12788
------------------------------------------------------------------------------
  Ticket             | 12788
  Created By         | x.van_dessel at ieee.org
  Summary            | access to /etc/resolv.conf not allowed per
                     | open_basedir directive
  Queue              | Horde Base
  Version            | 5.1.4
  Type               | Bug
  State              | Unconfirmed
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


x.van_dessel at ieee.org (2013-10-23 12:48) wrote:

On one side, this is a code snippet from
/usr/share/pear/Horde/Core/Factory/Dns.php

  if (is_readable('/etc/resolv.conf')) {

On the other side, this is part of the http configuration file for horde:

         php_admin_value open_basedir  
"/usr/share/horde:/etc/horde:/usr/share/pear:/tmp:/usr/share/php"

This states that the http engine should not be allowed to access any  
data outside the specified directories when running horde code.

It is clear that both statements are contradictory: testing whether  
you can read /etc/resolv.conf, but also installing a rule that you  
cannot access it.

The only net effect are error messages in the syslog.

Recommendation: no php module should need to natively read  
resolv.conf. calling standard name services should be sufficient.