Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Completely migrate from whitelist/blacklist to allowlist/denylist terminology #2536

Closed
mshibuya opened this issue Feb 28, 2021 · 2 comments
Closed
Assignees

Comments

@mshibuya
Copy link
Member

The work done in #2442 is just a half-way. It leaves names of some classes and methods untouched for smoother transition. In the next major release we will migrate all of them.

@mshibuya mshibuya added this to the Release v3.0.0 milestone Feb 28, 2021
@mshibuya mshibuya self-assigned this Feb 28, 2021
@seuros
Copy link
Contributor

seuros commented May 30, 2021

Hi, i think we should discard the denylist and have only allowed list . My point is there is always a security holes when a dev restrict instead of allowing things .

@mshibuya
Copy link
Member Author

@seuros OK, I'll mark the denylist as deprecated, so we can remove it in the future.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants