Currently we are using a fork of tokio-tls because of a regression in the alpha version of that library which hides the SSL certificate details from client code. There's an open issue about this on the tokio repo. We could cut the tokio project a PR with something like what the fork does; the current fork isn't great so will need improving. Or we can just wait and hope they get to that issue eventually.
In the linked tokio issue there seems to have been a PR merged that fixes the issue upstream. This issue should now just be to migrate to the new version of tokio.
Currently we are using a fork of tokio-tls because of a regression in the alpha version of that library which hides the SSL certificate details from client code. There's an open issue about this on the tokio repo. We could cut the tokio project a PR with something like what the fork does; the current fork isn't great so will need improving. Or we can just wait and hope they get to that issue eventually.