You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd like to connect to a docker daemon with tls certificate, but the certificate are never stored on the filesystem client side. connect_with_ssl only take Path for keys.
Would it be possible to have a constructor that take directly a Transport so a user can set it up themselve.
An alternative would be to able to pass a rustls::ClientConfig.
I'm willing to contribute this, what do you think?
Thanks,
Hugues
Edit: I think this could also make it possible to tunnel through ssh #244
The text was updated successfully, but these errors were encountered:
Yes, I'm definitely interested. There was some conversation recently around request customisation ( #395 (comment) and #436 ), so it would be interesting to see if this implementation can be used as a template to solve that problem too.
Hello,
I'd like to connect to a docker daemon with tls certificate, but the certificate are never stored on the filesystem client side.
connect_with_ssl only take
Path
for keys.Would it be possible to have a constructor that take directly a
Transport
so a user can set it up themselve.An alternative would be to able to pass a
rustls::ClientConfig
.I'm willing to contribute this, what do you think?
Thanks,
Hugues
Edit: I think this could also make it possible to tunnel through ssh #244
The text was updated successfully, but these errors were encountered: