Replies: 1 comment
-
Hi! This sounds like an issue that been discussed before: #691 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Today a server I don't control started misbehaving: It is no longer sending its intermediate cert. To fix the issue quickly I wanted to either just disable TLS verification or explicitly provide the intermediate cert to the application. However, I can't figure out how to do either: I'm stuck on how to write a
TlsConnector
, because most of the implementation details that ureq uses are private, making it really difficult to come up with a way to make this simple change.So for example, with
curl
I can docurl -k
(disable verification) orcurl --cacert ./cert.pem
to provide the intermediate cert and it just works. To emulate the latter with Rust I got as far as this:But this where I'm stuck. I've copied this impl block and then replaced all error handling with
unwrap
, but because neitherTlsConnector
norClientConfig
are part of my crate I can't write theimpl
block like this:error[E0117]: only traits defined in the current crate can be implemented for types defined outside of the crate
I could go and fix this issue and also deal with the implementation of
ReadWrite
that I haven't done yet, but this is becoming an awful lot of code so I'm wondering if there's an easier way or if I'm doing something wrong? I'm fairly new to rust, so this might just be a newbie problem, or it could be that the ecosystem is young and some APIs haven't matured that far yet, so I'm hoping someone has an idea of what I should try next.Beta Was this translation helpful? Give feedback.
All reactions