Peter Hamilton

Hi all, I'm going to be stepping in to assist @danetrain with the implementation for the CertificateValidator. I'm hoping to get a pull request up by next week. @etrauschke As...

@etrauschke I agree that making additional network connections when doing lookups should be avoided, at least for this first cut. Right now, the implementation we're working on requires the full...

@rowland-smith Check out https://github.com/pyca/cryptography/pull/2387. It adds a `signature` property to the `Certificate` API that allows you to get the signature bytes. I'm hoping that'll get merged soon. We're still debating...

@rowland-smith No word yet on the `tbs_certificate` bytes. It definitely needs to be added to `cryptography`, either as an update to the Certificate API or to the backend API. @etrauschke...

@rowland-smith FYI, @reaperhulk updated https://github.com/pyca/cryptography/pull/2387 to include a `tbs_certificate_bytes` property in the Certificate API. Hopefully this will merge soon.

@alex W00t! Thanks, I'm hoping to push an update to https://github.com/pyca/cryptography/pull/2460 today, so this definitely helps me out.

Hi @KBassford, thanks for filing this issue. Yeah, the `repr` functions are definitely not uniformly up-to-date. The original intent was to support basic serialization to string form as opposed to...

This came up again in Issue #448, this time regarding the ``host/hostname`` field, yielding an unintuitive client connection error.

Hi @pkking, thanks for filing this issue. Adding support for the `Link` attribute is on the todo list but I can't say at this point when I'll be able to...

Thanks for the update. I'll look into how much effort it'll take to get `Link` support in place on the client side. I may be able to squeeze something in...