-
Notifications
You must be signed in to change notification settings - Fork 326
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
Proposal to block 4190 (sieve) and 6679 (osaut, irc+tls alternate) #1663
Comments
CC @valenting |
Blocking new ports creates a lot of work for enterprise users. I'd rather not do it without clear evidence of a risk. |
As I understand it both ports have been used and probably are still used for text protocols that can be spoofed. |
Sorry for being slow, I haven't found evidence of extensive use of these ports that would worry me, but I want to do a bit more research. |
@ricea has that research been completed? @valenting any thoughts from Gecko? |
I don't have any concerns regarding this change. I'm happy to standardize on a common list of blocked ports. |
Tests: web-platform-tests/wpt#45350. Fixes #1663.
PR and tests are now up. I'll merge it all a week from now barring any unforeseen comments. |
Tests: web-platform-tests/wpt#45350. Fixes #1663.
Automatic update from web-platform-tests Fetch: block ports 4190 & 6679 For whatwg/fetch#1663. -- wpt-commits: 6c6f8a91e970250b526794289906ab53e04f6f32 wpt-pr: 45350
Automatic update from web-platform-tests Fetch: block ports 4190 & 6679 For whatwg/fetch#1663. -- wpt-commits: 6c6f8a91e970250b526794289906ab53e04f6f32 wpt-pr: 45350
I noticed WebKit has been blocking these for the past six years or so. I'm happy to work on PRs if there's agreement to standardize.
cc @ricea @mozfreddyb
The text was updated successfully, but these errors were encountered: