[issue8882] socketmodule.c`getsockaddrarg() should not check the length of sun_path

A.M. Kuchling added the comment: No changes seems to be necessary, per MvL's comment. -- nosy: +akuchling resolution: -> wont fix stage: -> resolved status: open -> closed ___ Python tracker __

[issue8882] socketmodule.c`getsockaddrarg() should not check the length of sun_path

Changes by Sébastien Sablé : -- nosy: +sable ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue8882] socketmodule.c`getsockaddrarg() should not check the length of sun_path

Edward Pilatowicz added the comment: some additional data. AIX 6.1: defined sun_path = 1023 max sun_path = 1023 i'll also point out the existence of the SUN_LEN() macro, which is defined on all the previously mentioned operating systems, and which calculates the size of a sockaddr_un s

[issue8882] socketmodule.c`getsockaddrarg() should not check the length of sun_path

Edward Pilatowicz added the comment: so i wrote a simple test program that tells me the defined length of sun_path and then uses bind() with increasingly long paths to determine the actually supported length of sun_path. here's what i've found: Solaris: defined sun_path = 108 max sun_p

[issue8882] socketmodule.c`getsockaddrarg() should not check the length of sun_path

Martin v. Löwis added the comment: > Applications should not assume a particular length for sun_path or > assume that it can hold {_POSIX_PATH_MAX} characters (255). > > hence, it seems to me that python should not actually be doing any size > checks on the path passed to getsockaddrar

[issue8882] socketmodule.c`getsockaddrarg() should not check the length of sun_path

New submission from Edward Pilatowicz : recently i was writing some python code that attempted to bind a unix domain socket to a long filesystem path. this code was failing and telling me that the path name was too long. tracing python i saw that it wasn't event issuing a system call for my bin