<!-- Kamailio Pull Request Template -->

<!--
IMPORTANT:
  - for detailed contributing guidelines, read:
    https://github.com/kamailio/kamailio/blob/master/.github/CONTRIBUTING.md
  - pull requests must be done to master branch, unless they are backports
    of fixes from master branch to a stable branch
  - backports to stable branches must be done with 'git cherry-pick -x 
...'
  - code is contributed under BSD for core and main components (tm, sl, auth, 
tls)
  - code is contributed GPLv2 or a compatible license for the other components
  - GPL code is contributed with OpenSSL licensing exception
-->

#### Pre-Submission Checklist
<!-- Go over all points below, and after creating the PR, tick all the 
checkboxes that apply -->
<!-- All points should be verified, otherwise, read the CONTRIBUTING 
guidelines from above-->
<!-- If you're unsure about any of these, don't hesitate to ask on 
sr-dev mailing list -->
- [x] Commit message has the format required by CONTRIBUTING guide
- [x] Commits are split per component (core, individual modules, libs, utils, 
...)
- [x] Each component has a single commit (if not, squash them into one commit)
- [x] No commits to README files for modules (changes must be done to docbook 
files
in `doc/` subfolder, the README file is autogenerated)

#### Type Of Change
- [ ] Small bug fix (non-breaking change which fixes an issue)
- [x] New feature (non-breaking change which adds new functionality)
- [ ] Breaking change (fix or feature that would change existing functionality)

#### Checklist:
<!-- Go over all points below, and after creating the PR, tick the 
checkboxes that apply -->
- [ ] PR should be backported to stable branches
- [x] Tested changes locally
- [ ] Related to issue #XXXX (replace XXXX with an open issue number)

#### Description

##### **Summary**

This update introduces new functionality to the `secfilter` module, enabling 
the removal of entries from both the Blacklist and Whitelist. It also includes 
automatic detection and removal of duplicate values from these lists.

##### **Details**

   * Users can now remove specific entries from the Blacklist or Whitelist 
based on type (e.g., IP, domain, user) and a given value.
   * Supports removal of single or multiple matching entries in one operation.


##### **Benefits**

- Improves the usability and flexibility of the `secfilter` module by allowing 
fine-grained control over list management.
- Ensures that the Blacklist and Whitelist are kept clean and free from 
redundant entries.
- Enhances performance by reducing unnecessary duplication in the lists.

##### Testing
This feature was tested using `kmcmd` commands in various scenarios:
- Removing the **first element** in the list.
- Removing an element from the **middle** of the list.
- Removing the **last element** in the list.
- Removing **all matching elements** in the list.

In all cases, the commands worked correctly, and the lists were updated and 
cleaned as expected.

You can view, comment on, or merge this pull request online at:

  https://github.com/kamailio/kamailio/pull/4086

-- Commit Summary --

  * secfilter‌: support remove rule in Whitelist and Blacklist
  * Merge remote-tracking branch 'origin/master' into 
Feature/5-support-remove-rule-in-Whitelist-Blacklist
  * secfilter‌: support remove rule in Whitelist and Blacklist
  * edit end of file

-- File Changes --

    M src/modules/secfilter/secfilter.c (8)
    M src/modules/secfilter/secfilter.h (3)
    M src/modules/secfilter/secfilter_db.c (106)
    M src/modules/secfilter/secfilter_rpc.c (94)

-- Patch Links --

https://github.com/kamailio/kamailio/pull/4086.patch
https://github.com/kamailio/kamailio/pull/4086.diff

-- 
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/4086
You are receiving this because you are subscribed to this thread.

Message ID: <kamailio/kamailio/pull/4...@github.com>
_______________________________________________
Kamailio - Development Mailing List -- sr-dev@lists.kamailio.org
To unsubscribe send an email to sr-dev-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!

Reply via email to