[Mod-security-developers] [JIRA] Resolved: (MODSEC-365) Segfault in Nginx with Modsecurity if user didn't put the modsecurity directives

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

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

Breno Silva Pinto resolved MODSEC-365.
--------------------------------------

    Resolution: Fixed

Hello Aditya,

I tested with the latest trunk and looks fixed. If you can test and give me a feedback would be good.

Thanks

Breno

> Segfault in Nginx with Modsecurity if user didn't put the modsecurity directives
> --------------------------------------------------------------------------------
>
>                 Key: MODSEC-365
>                 URL: https://www.modsecurity.org/tracker/browse/MODSEC-365
>             Project: ModSecurity
>          Issue Type: Bug
>      Security Level: Normal
>          Components: Core
>    Affects Versions: 2.7.1
>         Environment: Centos 5.8 x86, Nginx 1.3.8
>            Reporter: Aditya W
>            Assignee: Breno Silva Pinto
>            Priority: Low
>              Labels: nginx, segfault
>             Fix For: 2.7.3
>
>
> If a user compiled modsecurity with nginx and the user didn't write both ..
> ModSecurityEnabled on/off
> ModSecurityConfig xxxxx
> in the appropriate section of his/her configuration file, when the user started nginx it'll be segfault
> 2012/12/05 09:25:29 [alert] 28916#0: cache manager process 32671 exited on signal 11
> 2012/12/05 09:25:29 [alert] 28916#0: worker process 32672 exited on signal 11
> 2012/12/05 09:25:29 [alert] 28916#0: worker process 32673 exited on signal 11
> 2012/12/05 09:25:29 [alert] 28916#0: worker process 32674 exited on signal 11
> 2012/12/05 09:25:29 [alert] 28916#0: worker process 32675 exited on signal 11
> and it keeps on looping and filling the log file

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