Changes between and of Version 5Version 7Ticket #5445


Ignore:
Timestamp:
02/27/2013 11:42:42 AM (21 months ago)
Author:
glyph
Comment:

Replying to exarkun:

The ticket description could still do a better job of explaining what needs to be done. For example, as is, I might just say that it is already possible to point an Agent at a certificate store using WebClientContextFactory and the pyOpenSSL Context APIs. What do you think is necessary beyond that to resolve this ticket?

Hmm. Good point. The issue here is that this always ought to be done by default; as it was phrased previously this was not clear at all.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #5445

    • Property Summary changed from certificate validation against natively-configured certificate authorities for HTTPS URLs in twisted.web.client.Agent to validate against platform-trusted certificate authorities by default for HTTPS URLs in twisted.web.client.Agent
  • Ticket #5445 – Description

    v5 v7  
    1 It should be possible to use the platform's native list of certificate authorities as the trust root for HTTPS client connections from Agent.request. 
     1HTTPS client connections from Agent.request should use the platform's native list of certificate authorities as the trust root by default. 
    22 
    33This ticket is only for fixing `Agent` to actually point at the certificate store API we come up with; [ticket:5446 there is another ticket for actually implementing that store] which is really the hard part here.