Sounds like a good solution. Thanks!
Steve
On Thu, Dec 8, 2016 at 9:12 AM, Andy Balholm wrote:
> So the set of devices keeps changing.
>
> I think you can make an http.Transport with a custom DialTLS function that
> always uses an up-to-date TLS config.
>
> Andy
--
You received this message b
So the set of devices keeps changing.
I think you can make an http.Transport with a custom DialTLS function that
always uses an up-to-date TLS config.
Andy
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and sto
Well, because when someone wants to import a new device, I can't change the
existing Transport. The docs explicitly say not to change it once it's in
use.
Steve
On Thu, Dec 8, 2016 at 8:42 AM, Andy Balholm wrote:
> Why not make a tls.Config that trusts all the self-signed certs for all
> the
Why not make a tls.Config that trusts all the self-signed certs for all the
different devices, and make one Transport with that config?
Andy
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving email
I have an application that needs to talk to numerous external devices, each
of which has only a self-signed cert. We can't simply accept all
self-signed certs with insecureSkipVerify; instead, as part of configuring
the application for each new external device, we need to import its
self-signe
