Message94773
It might mean that other threads with access to the same file handle
could interfere and intercept part of the password entry if they wanted
to but thats not too concerning.
py3k/Modules/_io/bufferedio.c which is presumably used when input is
sys.stdin instead of a /dev/tty file appears to lock things.
Compared to glibc's getpass implementation the locking should probably
be done around a wider swath of getpass code in order to protect all
possible race conditions of other code accessing the handle as we set it
up and display the prompt. I don't really think it is something worry
about as it requires code executing within the context of your own
getpass calling program to be doing something that'll interfere with
your password reading. If someone has -that- problem they have bigger
issues. |
|
Date |
User |
Action |
Args |
2009-10-31 22:26:15 | gregory.p.smith | set | recipients:
+ gregory.p.smith, belopolsky, pitrou, pajs@fodder.org.uk |
2009-10-31 22:26:15 | gregory.p.smith | set | messageid: <1257027975.32.0.546894185436.issue7208@psf.upfronthosting.co.za> |
2009-10-31 22:26:13 | gregory.p.smith | link | issue7208 messages |
2009-10-31 22:26:12 | gregory.p.smith | create | |
|