On 09/12/13 22:19, Laurens Van Houtven wrote:
... but in the server's AMP protocol,
self.transport.getPeerCertificate() is still None :/
Unless you set the appropriate verify options on the server side too,
the client cert isn't available for inspection.
On Tue, Dec 10, 2013 at 9:41 AM, Phil Mayers wrote:
> Unless you set the appropriate verify options on the server side too, the
> client cert isn't available for inspection.
>
A-ha! But I want to do TOFU-POP; the certs are generated by the client, and
there's little point in me signing them (I do
On 08:41 am, p.may...@imperial.ac.uk wrote:
On 09/12/13 22:19, Laurens Van Houtven wrote:
... but in the server's AMP protocol,
self.transport.getPeerCertificate() is still None :/
Unless you set the appropriate verify options on the server side too,
the client cert isn't available for inspec
On 10/12/13 13:21, exar...@twistedmatrix.com wrote:
On 08:41 am, p.may...@imperial.ac.uk wrote:
On 09/12/13 22:19, Laurens Van Houtven wrote:
... but in the server's AMP protocol,
self.transport.getPeerCertificate() is still None :/
Unless you set the appropriate verify options on the server
Somehow, JP's e-mail did not make it into my inbox :-(
Anyway, using the context factory that I got
from ssl.PrivateCertificate.options() (which I think is
CertificateOptions), I wasn't able to inspect the peer certificate. That's
on 13.2. Using the context factory I pasted in a previous e-mail, i
On 12/09/2013 12:43 PM, Daniel Sank wrote:
This is an update because glyph asked about this issue in another
thread but I want to put the information where it belongs:
1. Try to log in. Does not accept credentials (login box simply
reappears with username and password fields blank).
2. Cannot f
> Can you try deleting all cookies for twistedmatrix.com and then try the reset
> again, or perhaps login with last reset password you got?
1. Deleted all cookies
2. Asked for password reset
3. Got new password
4. Tried to log in with new password. Does not work.
