Feature request: accept a set of fingerprints in TCPConnector

[sp-1234]

Long story short

Right now, if I understand correctly, it's only possible to set a single fingerprint which will be accepted by https client.
Sometimes, endpoint may use one of several certificates (for example if the exact time of certificate update is unknown), so it would make sense to trust a set of certificates instead of just one.

Also, as I see in the current source, it should be a very easy change:

got = self._hashfunc(cert).digest()
expected = self._fingerprint
if got != expected:
    …

so if you agree but have no time, I can give it a try.

[asvetlov]

I think better fix would be adding fingerprint parameter to client.get() etc. like we have it for proxy support now. If you would to make a PR -- you are welcome.

[sp-1234]

@asvetlov so if I do this issue, I should also do #1128 in the same PR?

[asvetlov]

Please make two separate PRs.
It makes reviewing much easier.

[cecton]

Started in #2184

[asvetlov]

Fixed in aiohttp 2.3 by #2184

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a [new issue] for related bugs.
If you feel like there's important points made in this discussion, please include those exceprts into that [new issue].
[new issue]: https://github.com/aio-libs/aiohttp/issues/new