stun.DialConfig{} requires a tls.Config instead of *tls.Config
If you want to use stun.DialURI with a custom stun.DialConfig you are required to use a tls.Config instead of a pointer to it. That ends up in "copying lock" whining from linters etc.
Note: Yes of course you can build directly a stun.DialConfig instead but it would be nicer to have the ability to pass tls.Config that come from other places
I guess it will never happen as it will break backwards compatibility but maybe something to keep in mind in case a v3 is released
We'll keep this issue open, as something to consider when we're making a new major version, we can also make a "hack" for the current version. Thank you.