Additional collection backends for libmodsecurity (Redis, Memcached) #1139

Activity

1. zimmerle

   self-assigned this

   on May 5, 2016
2. zimmerle

   added

   RIP - libmodsecurity

   libmodsec - missing features

   on May 5, 2016
3. zimmerle

   added this to the v3.0.0 - OWASP CRS Compatible milestone on May 5, 2016
4. zimmerlezen

   modified the milestones: v3.0.0 feature complete, v3.0.0 - OWASP CRS Compatible on May 5, 2016
5. zimmerle

   modified the milestones: v3.0.1, v3.0.0 feature complete on Aug 2, 2016
6. theadoria commented on Aug 18, 2016

   

   theadoria

   on Aug 18, 2016

   More actions

   Will this support connecting to redis over a unix socket? Would be very useful for multi tenant environments :)
7. zimmerle commented on Aug 25, 2016

   

   zimmerle

   on Aug 25, 2016

   ContributorAuthor

   More actions

   Hi @tedwardia, the support for Redis [or Memcache] should be independent of transport. That way you will be able to use what fits better inside your environment. Notice that you will be also able to choose which backend you want to use.
9. tomsommer commented on May 30, 2017

   

   tomsommer

   on May 30, 2017

   Contributor

   More actions

   Major +1
11. HugoSoszynski commented on Feb 22, 2018

    

    HugoSoszynski

    on Feb 22, 2018

    More actions

    Hi,

    The VultureProject team (https://vultureproject.org/) is currently developing this feature for ModSecurity v3.
    We are working to make it available for everyone as soon as possible.

    Regards,

    Hugo SOSZYNSKI
    Vulture Team

    👍React with 👍1Reacted by Felipe Zimmerle
12. zimmerle commented on Feb 23, 2018

    

    zimmerle

    on Feb 23, 2018

    ContributorAuthor

    More actions

    @HugoSoszynski if you need to discuss any aspect of the implementation, I will be glad to help.
13. zimmerle commented on Feb 28, 2018

    

    zimmerle

    on Feb 28, 2018

    ContributorAuthor

    More actions

    @HugoSoszynski any position so far?
14. HugoSoszynski commented on Mar 1, 2018

    

    HugoSoszynski

    on Mar 1, 2018

    More actions

    Hi,

    @zimmerle You can check the work done so far here : https://github.com/VultureProject/ModSecurity/tree/remotes/trunk/src/collection/backend .

    A summary of the features and the design informations is available in my last commit (https://github.com/VultureProject/ModSecurity/commit/71ba1d041e10c508dc47a471f76185d2295d90da).

    I am currently testing the internal methods such as querying and fail-over in our infrastructures as it is pretty hard to create a REDIS cluster on a Travis VM.
    Once the internal methods are validated, I will implement the Collections methods and start Travis unit testing.

    If you have any question, suggestion and / or correction to submit, feel free to open an Issue on the VultureProject repository.

    Regards,

    Hugo SOSZYNSKI
    Vulture Team

    ❤️React with ❤️1Reacted by Victor Hora
15. zimmerle commented on Mar 1, 2018

    

    zimmerle

    on Mar 1, 2018

    ContributorAuthor

    More actions

    good news! :) i will be looking in to it.
16. HugoSoszynski commented on Mar 8, 2018

    

    HugoSoszynski

    on Mar 8, 2018

    More actions

    Hi,

    @zimmerle
    In my quest to replicate the actual behavior of Collections with REDIS I'm having some trouble:

    • Is there any documentation about the exact detailed behavior of the Collection methods ?
    • As REDIS does not authorize multiple identical keys, I found a workaround using LIST object. However, it is pretty hard to emulate the behavior of an std::unordered_multimap or LMDB; must the REDIS Collection have the exact same behavior ?

    I hope we find some solutions to these questions.
    Regards,

    Hugo SOSZYNSKI
    Vulture Team
17. zimmerle commented on Mar 8, 2018

    

    zimmerle

    on Mar 8, 2018

    ContributorAuthor

    More actions

    Hi @HugoSoszynski,

    • There is no documentation about it :(
    • There is the need to have a middle ware, converting the ModSecurity data into Redis and vice-versa. A good way to test if it is working is by running the regression tests.
18. zimmerle

    modified the milestones: v3.0.1, v3.0.2This milestone has been deleted on Apr 2, 2018
19. victorhora

    modified the milestones: v3.0.3, v3.0.4 on Sep 5, 2018
20. LeeShan87 commented on Jan 22, 2019

    

    LeeShan87

    on Jan 22, 2019

    More actions

    It seem VultureProject stopped implementing redis backend for modsecurity. :(

    https://github.com/VultureProject/ModSecurity/

    😕React with 😕5Reacted by Tom Sommer, Felipe Zimmerle, Bryan Spears, Thea Wells and Matt H
21. fzipi commented on Oct 12, 2026

    

    fzipi

    on Oct 12, 2026

    Collaborator

    More actions

    Revisiting this one. 3.x still ships two collection backends, in-memory per process and LMDB (src/collection/backend/). The Vulture fork that started a Redis backend was abandoned in 2019 and nothing came back upstream. The interface is still there for anyone who wants to pick it up.

    Proposal: keep this as the tracking issue for additional collection backends (Redis, Memcached, ...) and label it help wanted; close #1140 into it. Needs a maintainer decision.
22. fzipi

    added

    3.xRelated to ModSecurity version 3.xRelated to ModSecurity version 3.x

    on Oct 12, 2026
23. fzipi

    changed the title [-]Implement Redis support as Collection backend on libmodsecurity[/-] [+]Additional collection backends for libmodsecurity (Redis, Memcached)[/+] on Oct 12, 2026
24. fzipi

    added

    needs decisionTriage done; a maintainer needs to make the final callTriage done; a maintainer needs to make the final call

    help wanted

    on Oct 12, 2026