Re: mod-security-users Digest, Vol 158, Issue 6
Reindl Harald <[email protected]>
| Newsgroups | gmane.comp.apache.mod-security.user |
|---|---|
| Organization | the lounge interactive design |
| Message-ID | <[email protected]> |
Am 13.07.19 um 01:37 schrieb Penetration: > Hello > you can set SecStatusEngine to On./ in .htaccess or httpd.conf (global > config) > please send the result of this command > #httpd -M > thanks besides that either you subscribe regulary instead reply to digest mails which makes everything a mess (starting with the subject and threading) or just read only: the oiginal subject was "ModSecurity disabled?" and hecne i responded "you don't need it and it has *nothing* to do with modsecurity disabled" days ago https://www.trustwave.com/en-us/resources/blogs/spiderlabs-blog/introducing-modsecurity-status-reporting/ > On Fri, Jul 12, 2019 at 4:45 PM > <[email protected] > <mailto:[email protected]>> wrote: > > Send mod-security-users mailing list submissions to > [email protected] > <mailto:[email protected]> > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.sourceforge.net/lists/listinfo/mod-security-users > or, via email, send a message with subject or body 'help' to > [email protected] > <mailto:[email protected]> > > You can reach the person managing the list at > [email protected] > <mailto:[email protected]> > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of mod-security-users digest..." > > > Today's Topics: > > 1. ModSecurity disabled ? (Edouard Guign?) > 2. Re: ModSecurity disabled ? (Reindl Harald) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 11 Jul 2019 14:57:26 -0300 > From: Edouard Guign? <[email protected] > <mailto:[email protected]>> > To: [email protected] > <mailto:[email protected]> > Subject: [mod-security-users] ModSecurity disabled ? > Message-ID: <[email protected] > <mailto:[email protected]>> > Content-Type: text/plain; charset="utf-8"; Format="flowed" > > Hello, > > I set mod_sec with apache. > > When I start apache service, I noticed : > > /ModSecurity: Status engine is currently disabled, enable it by set > SecStatusEngine to On./ > > What does it mean ? > Do I have to add? SecStatusEngine directive in httpd.conf ? > I am using virtual host conf file, as reverse proxy. > > Best Regards, > > EdG > > -------------- next part -------------- > An HTML attachment was scrubbed... > > ------------------------------ > > Message: 2 > Date: Thu, 11 Jul 2019 20:23:04 +0200 > From: Reindl Harald <[email protected] > <mailto:[email protected]>> > To: [email protected] > <mailto:[email protected]> > Subject: Re: [mod-security-users] ModSecurity disabled ? > Message-ID: <[email protected] > <mailto:[email protected]>> > Content-Type: text/plain; charset=utf-8 > > > > Am 11.07.19 um 19:57 schrieb Edouard Guign?: > > I set mod_sec with apache. > > > > When I start apache service, I noticed : > > > > /ModSecurity: Status engine is currently disabled, enable it by set > > SecStatusEngine to On./ > > > > What does it mean ? > > Do I have to add? SecStatusEngine directive in httpd.conf ? > > I am using virtual host conf file, as reverse proxy. > > you don't need it and it has *nothing* to do with "modsecurity disabled" > > https://www.trustwave.com/en-us/resources/blogs/spiderlabs-blog/introducing-modsecurity-status-reporting/ _______________________________________________ mod-security-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mod-security-users Commercial ModSecurity Rules and Support from Trustwave's SpiderLabs: http://www.modsecurity.org/projects/commercial/rules/ http://www.modsecurity.org/projects/commercial/support/