[Mod-security-developers] [JIRA] Resolved: (MODSEC-149) It should be possible to define SecDataDir in other Scopes than Main

[Breno S. P. (JIRA) <no...@mo...>]

     [ https://www.modsecurity.org/tracker/browse/MODSEC-149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Breno Silva Pinto resolved MODSEC-149.
--------------------------------------

    Resolution: Won't Fix

> It should be possible to define SecDataDir in other Scopes than Main
> --------------------------------------------------------------------
>
>                 Key: MODSEC-149
>                 URL: https://www.modsecurity.org/tracker/browse/MODSEC-149
>             Project: ModSecurity
>          Issue Type: Improvement
>      Security Level: Normal
>          Components: Configuration
>    Affects Versions: 2.5.12
>            Reporter: Peter Meier
>            Assignee: Breno Silva Pinto
>             Fix For: 2.7.0
>
>
> If you are running apache with mod-itk [1] each vhost might run as own user, hence if you need to define a SecDataDir you need to make this data directroy global writeable, which is not that nice.
> It might be nicer to be able to define SecDataDir per vhost and hence have a directory that can only be written and READ by the user that the current vhost is running with.
> [1] http://mpm-itk.sesse.net/

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira