Message 415967 - 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	gregory.p.smith
Recipients	christian.heimes, gregory.p.smith, habnabit, pitrou, serhiy.storchaka, zonyitoo
Date	2022-03-24.18:35:08
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1648146908.2.0.855411783636.issue44493@roundup.psfhosted.org>
In-reply-to

Content
It looks like the length would be short by one in Python before this change, meaning binding or connecting to a non-anonymous named AF_UNIX socket potentially loses the last character of the path name intended to be bound? Depending on if the OS uses the length or trusts a null termination? That should be an observable behavior change. It also suggests that fixing this could break code that has been working around this bug forever by adding an extra character when binding or connecting to a non-anonymous AF_UNIX socket? Is that true? In what circumstances is this practically observed?

It looks like the length would be short by one in Python before this change, meaning binding or connecting to a non-anonymous named AF_UNIX socket potentially loses the last character of the path name intended to be bound? Depending on if the OS uses the length or trusts a null termination?

That should be an observable behavior change.

It also suggests that fixing this could break code that has been working around this bug forever by adding an extra character when binding or connecting to a non-anonymous AF_UNIX socket?  Is that true?  In what circumstances is this practically observed?

History
Date	User	Action	Args
2022-03-24 18:35:08	gregory.p.smith	set	recipients: + gregory.p.smith, pitrou, christian.heimes, habnabit, serhiy.storchaka, zonyitoo
2022-03-24 18:35:08	gregory.p.smith	set	messageid: <1648146908.2.0.855411783636.issue44493@roundup.psfhosted.org>
2022-03-24 18:35:08	gregory.p.smith	link	issue44493 messages
2022-03-24 18:35:08	gregory.p.smith	create