mirror of
https://github.com/AdguardTeam/AdGuardHome.git
synced 2026-03-04 00:01:12 -05:00
An option to only delete log entries that belong to a specific IP or CIDR #2895
Labels
No labels
P1: Critical
P2: High
P3: Medium
P4: Low
UI
bug
cannot reproduce
compatibility
dependencies
docker
documentation
duplicate
enhancement
enhancement
external libs
feature request
good first issue
help wanted
infrastructure
invalid
localization
needs investigation
performance
potential-duplicate
question
recurrent
research
snap
waiting for data
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/AdGuardHome#2895
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @DandelionSprout on GitHub (Jul 12, 2021).
Originally assigned to: @ainar-g on GitHub.
Have a question or an idea? Please search it on our forum to make sure it was not yet asked. If you cannot find what you had in mind, please submit it here.
Prerequisites
Please answer the following questions for yourself before submitting an issue. YOU MAY DELETE THE PREREQUISITES SECTION.
Problem Description
This is somewhat of a fringe plausible event that relies on 1) running a public AdGuard Home server, and 2) not having a "No logging" policy:
The possibility has struck me that someone who is an end-user of someone else's public AGH server, may plausibly wish to exercise the GDPR "Right to Forget" right. Currently, the only way to fulfill such a request, would be to delete AGH's entire log for all users, incl. those of the admin's household items.
Proposed Solution
An option to only delete log entries that belong to a specific IP or CIDR.
Alternatives Considered
None that I can think of, mostly I haven't thought about it all that much due to the rare chance of it happening.
Additional Information
As far as I can determine, this is not a clone of #3140 nor #1717
@ainar-g commented on GitHub (Jul 12, 2021):
Will only be really possible after #2290.