| Summary: | Block loading for port 10080 | ||||||
|---|---|---|---|---|---|---|---|
| Product: | WebKit | Reporter: | youenn fablet <youennf> | ||||
| Component: | Page Loading | Assignee: | youenn fablet <youennf> | ||||
| Status: | RESOLVED FIXED | ||||||
| Severity: | Normal | CC: | achristensen, beidson, benjamin, cdumez, clopez, cmarcelo, ews-watchlist, webkit-bug-importer | ||||
| Priority: | P2 | Keywords: | InRadar | ||||
| Version: | WebKit Local Build | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Attachments: |
|
||||||
|
Description
youenn fablet
2021-04-12 06:05:29 PDT
Created attachment 425739 [details]
Patch
This patch modifies the imported WPT tests. Please ensure that any changes on the tests (not coming from a WPT import) are exported to WPT. Please see https://trac.webkit.org/wiki/WPTExportProcess Corresponding WPT PR at https://github.com/web-platform-tests/wpt/pull/28445 Is there anything official allocating 10080? It seems to be in an unallocated block of ports. If I wrote a program that used an unallocated port, what would I have to do to get that port blocked in all browsers? https://groups.google.com/a/chromium.org/g/blink-dev/c/CNpLNXx2wf0/m/Ehi3cx1YAQAJ claims that this is a "mitigation for the NAT Slipstream 2.0 attack" but I can't find anything abut that attack that references this port. Discussion is at https://github.com/whatwg/fetch/pull/1148 and https://github.com/whatwg/fetch/issues/1191. Comment on attachment 425739 [details] Patch https://github.com/torvalds/linux/blob/master/net/netfilter/nf_conntrack_amanda.c has been in the Linux repo for a long time. Committed r275831 (236401@main): <https://commits.webkit.org/236401@main> All reviewed patches have been landed. Closing bug and clearing flags on attachment 425739 [details]. |