Thread (3 messages) 3 messages, 2 authors, 2019-09-03

Re: [PATCH net-next] net: Fail explicit bind to local reserved ports

From: Subash Abhinov Kasiviswanathan <hidden>
Date: 2019-09-03 20:34:50

I don't know how happy I am about this.  Whatever sets up the 
transparent
proxy business can block any attempt to communicate over these ports.

Also, protocols like SCTP need the new handling too.
Hi David

The purpose of this patch was to allow the transparent proxy application
to block the specific socket ranges to prevent the communication on the
specific ports.

Dropping packets for this particular port using iptables could lead to
applications on the system getting stuck without getting a socket error.
If bind fails explicitly, the application can atleast retry for some 
other
port.
Is there some alternate existing mechanism to achieve this already?

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help