Skip to content
This repository has been archived by the owner on Sep 10, 2024. It is now read-only.

Implement IP and DNS-based filtering in the HTTP client #1018

Open
sandhose opened this issue Mar 17, 2023 · 1 comment
Open

Implement IP and DNS-based filtering in the HTTP client #1018

sandhose opened this issue Mar 17, 2023 · 1 comment
Labels
O-Uncommon Affects or can be seen by some users regularly or most users rarely S-Tolerable Minor significance, cosmetic issues, low or no impact to users. T-Enhancement New feature of request

Comments

@sandhose
Copy link
Member

The HTTP client can be used to crawl some HTTP resources, like remove JWKS. We want to avoid malicious actors to reach internal endpoints.
We should implement on the DNS resolver level IP and DNS filtering. The default IP blacklist in Synapse could be useful.
@sandhose sandhose added T-Enhancement New feature of request O-Uncommon Affects or can be seen by some users regularly or most users rarely S-Tolerable Minor significance, cosmetic issues, low or no impact to users. labels Oct 11, 2023
@matrixbot matrixbot mentioned this issue Sep 9, 2024
Open
@matrixbot
Copy link
Member

For your information, this issue has been copied over to the Element fork of matrix-authentication-service: element-hq/matrix-authentication-service#1018

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
O-Uncommon Affects or can be seen by some users regularly or most users rarely S-Tolerable Minor significance, cosmetic issues, low or no impact to users. T-Enhancement New feature of request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@sandhose @matrixbot