➜

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 asdfasdfasdfasdfasdfasdfasdf
Recipients asdfasdfasdfasdfasdfasdfasdf, eric.araujo, loewis, pitrou
Date 2010-11-21.02:23:05
SpamBayes Score 3.4077942e-08
Marked as misclassified No
Message-id <AANLkTimiux1qP3qFJaHUTkyf9DMDhDi0JgvSH1Yt97+d@mail.gmail.com>
In-reply-to <1290292038.14.0.150569770801.issue10441@psf.upfronthosting.co.za>
Content 
On 21 November 2010 09:27, Antoine Pitrou <report@bugs.python.org> wrote:
>
> Antoine Pitrou <pitrou@free.fr> added the comment:
>
> Martin,
>
>> You misunderstood. I was not proposing that scripts provide a CA
>> list, but that users might deploy a CA list into their Python
>> installation, which is then picked up in the same way as you are asking
>> for on Ubuntu.
>
> Could you elaborate on what kind of scheme you are proposing?
>
> It should be noted that the default OpenSSL paths can be modified at runtime using environment variables SSL_CERT_FILE and SSL_CERT_DIR. Not sure we should document this, though.

Sorry is this question aimed at me?
No I was saying that if we can't move to a sane default then an
environmental setting or other configuration maybe nice to have to
enforce certificate checking etc.
It had nothing to do with those variables, but perhaps we would use them?
History
Date User Action Args
2010-11-21 02:23:06asdfasdfasdfasdfasdfasdfasdfsetrecipients: + asdfasdfasdfasdfasdfasdfasdf, loewis, pitrou, eric.araujo
2010-11-21 02:23:05asdfasdfasdfasdfasdfasdfasdflinkissue10441 messages
2010-11-21 02:23:05asdfasdfasdfasdfasdfasdfasdfcreate