Message357124
> My preference for create_datagram_endpoint() would be:
> - make the "reuse_address" parameter a no-op, and raise an error when "reuse_address=True" is passed
> - do that in 3.8 as well
This solution would more elegant, but my concern is that it will leave open a substantial security concern for versions 3.5, 3.6, and 3.7 if we only applied that to 3.8 and 3.9. Although Nathaniel's suggestion would ultimately make the `reuse_address` parameter fairly meaningless (essentially converting it into an alias for `reuse_port`), it would fix the security issue while still maintaining backwards compatibility for most users, allowing us to backport it all the way back to 3.5.
Perhaps this could lead to a deprecation warning or error, and then an eventual removal of `reuse_address`, but I think that's more of a long term concern for 3.9+. |
|
Date |
User |
Action |
Args |
2019-11-21 02:33:31 | aeros | set | recipients:
+ aeros, gvanrossum, pitrou, ned.deily, njs, asvetlov, yselivanov, dacut, vaizki |
2019-11-21 02:33:30 | aeros | set | messageid: <1574303610.97.0.862169096697.issue37228@roundup.psfhosted.org> |
2019-11-21 02:33:30 | aeros | link | issue37228 messages |
2019-11-21 02:33:30 | aeros | create | |
|