Hannes Mehnert
Hannes Mehnert
Indeed that would be great. Since there's no need to track IP addresses or user-agents, just the requested artifact, there shouldn't be an issue with GDPR.
this fixes #25 #26 #27 #28
another part of certificate selection should be based on signature algorithms -- i.e. when both EC and RSA certificates are available for the same alpn/hostname/..., accept that and select during...
I looked at the code, and the signature algorithm are respected when selecting a certificate. The ALPN not, though.
maybe using an optional argument is a good way to allow specialization by the client while making it not cumbersome. what do you think?
the only thing I'm wondering is about floating point numbers... since I dislike them, and would prefer integer numbers -- but I'm not sure whether there's a good/easy path forward...
back, I've a minor suggestion above. otherwise good to be merged.
thanks, squashed and merged :)
see also #89 ;) Maybe worth to have a GitHub action / cirrus runner for executing this test?
The question I have while this API gets revised: could we use an (immediate) int instead of of (boxed) int64? And: where's the limit of 64 devices coming from?