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 orsenthil
Recipients Nathanael.Noblet, loewis, orsenthil, pitrou
Date 2012-01-29.23:55:28
SpamBayes Score 1.0097297e-05
Marked as misclassified No
Message-id <20120129235520.GB6478@mathmagic>
In-reply-to <1327876245.67.0.23679510461.issue13856@psf.upfronthosting.co.za>
Content
On Sun, Jan 29, 2012 at 10:30:45PM +0000, Antoine Pitrou wrote:
> 
> Well, if you are a security expert you can volunteer to maintain a
> trusted certificates' file in the Python repository :) I think
> nobody else amongst us is qualified.

:-) haha. Neither am I (and I didn't figure out immediately that,
that's the requirement to go forward, so definitely not the person.)

But given that curl [1] has adopted the approach the user will know
where the CA cert will be and let's the user specify the details, I
wondered if the just having the provision to give ca_cert details is a
good thing.

Yeah, I recollect a discussion that there is not a standard
file-system path where OS store the certs and relying on them is not a
good idea.

[1] http://curl.haxx.se/docs/sslcerts.html
History
Date User Action Args
2012-01-29 23:55:29orsenthilsetrecipients: + orsenthil, loewis, pitrou, Nathanael.Noblet
2012-01-29 23:55:28orsenthillinkissue13856 messages
2012-01-29 23:55:28orsenthilcreate