Message 357068 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	pitrou
Recipients	aeros, asvetlov, dacut, gvanrossum, njs, pitrou, vaizki, yselivanov
Date	2019-11-20.12:25:15
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1574252715.97.0.514600884668.issue37228@roundup.psfhosted.org>
In-reply-to

Content
(previous message deleted, I hadn't noticed the "reuse_port" parameter) 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 way we 1) solve the security issue 2) ensure that anyone that passed "reuse_address=True" explicitly is notified that they were doing something dangerous unwillingly. And, yes, someone who really wants SO_REUSEADDR can set it manually, for example by calling `transport.get_extra_info('socket')`.

(previous message deleted, I hadn't noticed the "reuse_port" parameter)

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 way we 1) solve the security issue 2) ensure that anyone that passed "reuse_address=True" explicitly is notified that they were doing something dangerous unwillingly.

And, yes, someone who really wants SO_REUSEADDR can set it manually, for example by calling `transport.get_extra_info('socket')`.

History
Date	User	Action	Args
2019-11-20 12:25:16	pitrou	set	recipients: + pitrou, gvanrossum, njs, asvetlov, yselivanov, dacut, vaizki, aeros
2019-11-20 12:25:15	pitrou	set	messageid: <1574252715.97.0.514600884668.issue37228@roundup.psfhosted.org>
2019-11-20 12:25:15	pitrou	link	issue37228 messages
2019-11-20 12:25:15	pitrou	create