bpo-36161: Use thread-safe function ttyname_r instead of unsafe one ttyname by chibby0ne · Pull Request #14868 · python/cpython

* Use dynamically-allocated buffer for ttyname_r buffer
* In case there is an error with the crypt/crypt_r then raise the error,
instead of failing silently.
* Check for EINVAL (invalid argument) in errno when adding not supported
cryptographic methods, such as Blowfish in the case of glibc, but raise
other errors.
* Use _SC_TTY_MAX_LENGTH for TTY_NAME_MAX

Signed-off-by: Antonio Gutierrez <chibby0ne@gmail.com>

jacobneiltaylor pushed a commit to jacobneiltaylor/cpython that referenced this pull request

…onGH-14868)

Signed-off-by: Antonio Gutierrez <chibby0ne@gmail.com>

glebm mentioned this pull request

erlend-aasland added a commit to erlend-aasland/cpython that referenced this pull request

PR python#14868 replaced the ttyname() call with ttyname_r(), but the old
check remained.

erlend-aasland added a commit that referenced this pull request

PR #14868 replaced the ttyname() call with ttyname_r(), but the old
check remained.

erlend-aasland added a commit to erlend-aasland/cpython that referenced this pull request

erlend-aasland added a commit that referenced this pull request

…) (#128599)

(cherry picked from commit e08b282)

PR #14868 replaced the ttyname() call with ttyname_r(), but the old
check remained.

srinivasreddy pushed a commit to srinivasreddy/cpython that referenced this pull request

erlend-aasland added a commit that referenced this pull request

…) (#128598)

(cherry picked from commit e08b282)

PR #14868 replaced the ttyname() call with ttyname_r(), but the old
check remained.