Remove deprecated Blocklist.site (BlockList Project) entries from Unbound blocklists.conf
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 70/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- php
- Domain
- networking
Research direction
Start with the 18 Blocklist.site URLs in src/opnsense/service/templates/OPNsense/Unbound/core/blocklists.conf (lines 34-51, below the deprecated marker on line 33), then read the template logic at lines 71-74 that writes any shortcode present in the configuration. Follow commit a948778160, which removed ThreatFox from both Unbound.xml and blocklists.conf, as the pattern. Done when the blm entries and their URLs are gone from blocklists.conf and a configuration still selecting blm no longer produces a blocklists.blm line.
Written by the indexing model from the issue text.
Description
Important notices
- I have read the contributing guidelines at https://github.com/opnsense/core/blob/master/CONTRIBUTING.md
- I am convinced that my issue is new after having checked both open and closed issues at https://github.com/opnsense/core/issues?q=is%3Aissue
- AI tools were used to create at least part of the text submitted herewith.
If AI was used, please disclose:
- Model used: Claude Opus 5.5
- Extent of AI involvement: drafting of the text. All facts, file paths and line numbers were checked by the reporter against the current master branch.
Describe the bug
The Blocklist.site lists (BlockList Project, https://github.com/blocklistproject/Lists) were marked as deprecated in #9509 (merged 10 December 2025) and removed from the selection menu in Unbound.xml. However, their 18 URLs are still present in src/opnsense/service/templates/OPNsense/Unbound/core/blocklists.conf (lines 34-51, below the "deprecated, but still exist" marker on line 33), and the template (lines 71-74) still writes any shortcode present in the configuration. Installations that selected these lists before #9509 therefore keep downloading them.
The BlockList Project repository is now archived and read-only. Its last commit dates from 20 July 2026, and false-positive removal requests can no longer be submitted. Outdated entries in these lists can no longer be corrected.
To Reproduce
- On an installation configured before #9509, select "Blocklist.site Malware" (shortcode blm) under Services > Unbound DNS > Blocklist.
- Upgrade to the current version.
- The configuration still contains blm, and blocklists.conf still generates blocklists.blm=https://blocklistproject.github.io/Lists/alt-version/malware-nl.txt.
- The archived list continues to be downloaded and applied.
Expected behavior
Lists that are deprecated, unmaintained and archived upstream should no longer be downloaded. There is a precedent: commit a948778160 (closing #11091, 26 October 2026) removed Abuse.ch ThreatFox from both Unbound.xml and blocklists.conf instead of keeping it as deprecated.
Describe alternatives you considered
Requesting removal of the false positive from the list itself is not possible, because the repository is archived.
Screenshots
Not applicable.
Relevant log files
Not applicable.
Additional context
Our domain, biolink.website, appears in the archived malware list (https://blocklistproject.github.io/Lists/alt-version/malware-nl.txt, line 433859; file header "Last modified: 2026-07-18"). The upstream sources of that list no longer include it, but the archived copy cannot be updated.
Related: #9509, #7741, #8527. This issue replaces #11206, which did not use the template.
Environment
Reported based on a review of the current master branch (14 November 2026); latest stable tag 26.7.9. The reporter does not operate an OPNsense installation.
- Dominant language
- PHP
- Stars
- 4.8k
- Forks
- 1k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 36
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from opnsense/core
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
opnsense/core#11171 · 1 reaction ·
Maintainers usually reply within 1 day
-
support
Difficulty 1/5 1-3 hours Newbie friendliness 85/100
opnsense/core#11153 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
opnsense/core#11148 · 1 reaction ·
Maintainers usually reply within 1 day
Similar issues
-
sync-en
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Old /download.php attachment links: redirect drops the subfolder, nginx.example.conf returns 404OpenBug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
enhancement Feature: Users good first issue UI
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 Under an hour Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
vimeo/psalm#13772 · 2 comments ·
Maintainers usually reply within 4 days