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 simpkins
Recipients eric.araujo, giampaolo.rodola, janssen, pitrou, simpkins
Date 2011-08-21.18:24:36
SpamBayes Score 1.4237004e-08
Marked as misclassified No
Message-id <1313951076.98.0.991686855127.issue12803@psf.upfronthosting.co.za>
In-reply-to
Content
> It seems a bit strange to me to accept string types or callable in the 
> same argument.  If it just supported strings, people could still write
> password=somefunction(), right?

The function is only called if the private key is encrypted and a 
password is necessary.  This allows the code to only prompt for a 
password if it is actually needed.

This also parallels the OpenSSL C API, which only accepts a function to
get the password.  I added support for plain strings as a convenience.  
The string argument will be ignored if the file is not encrypted.
History
Date User Action Args
2011-08-21 18:24:37simpkinssetrecipients: + simpkins, janssen, pitrou, giampaolo.rodola, eric.araujo
2011-08-21 18:24:36simpkinssetmessageid: <1313951076.98.0.991686855127.issue12803@psf.upfronthosting.co.za>
2011-08-21 18:24:36simpkinslinkissue12803 messages
2011-08-21 18:24:36simpkinscreate