[Tickets #12975] Re: tmpdir problems not logged

[noreply at bugs.horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/12975
------------------------------------------------------------------------------
  Ticket             | 12975
  Updated By         | skhorde at smail.inf.fh-bonn-rhein-sieg.de
  Summary            | tmpdir problems not logged
  Queue              | Horde Framework Packages
  Version            | FRAMEWORK_5_1
  Type               | Bug
  State              | Unconfirmed
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


skhorde at smail.inf.fh-bonn-rhein-sieg.de (2014-02-18 10:45) wrote:

>> I configured confiig/conf.php: $conf['tmpdir'] = '/var/cache/horde';
>> chown root:root /var/cache/horde
>> chmod u=rwx,g=,o=wx /var/cache/horde
>
> You have got to be kidding. With the above settings, you might just  
> as well set the cache to /dev/null. The whole idea of a cache is  
> that you can both write *and* read stuff to/from the cache. If you  
> don't understand why Horde is unable to use the cache with the  
> permissions

a) the permissions of the cache directory can change unintentionally.  
Horde would not log problems.

b) without read permission of the directory, the only denied operation  
is opendir($conf['tmpdir']). Horde can read any item it created within  
the directory and below. I wonder what Horde searches for in tmpdir  
e.g. if one uses the system default /tmp, which is shared among  
various other processes. Any found item could belong to another  
process or web application.