On Thu, 2015-10-22 at 15:59 +0200, Gert Doering wrote:
> hi,
>
> On Thu, Oct 22, 2015 at 02:55:44PM +0100, David Woodhouse wrote:
> > > So what is the underlying issue here? Non-ASCII characters in the
> > > device name ("this *should* have been fixed a few releases ago")?
> >
> > No, and not spaces (despite the vpn.ccrypto.org link above suggesting
> > that it is).
>
> Spaces are known to not cause issues ("I do test things" :-) ).I have a Windows VM somewhere with an interface named 'TAP ♥' :) > > The issue is not known. Seriously, "because Windows". > > > > Renaming the interface, and then renaming it back to precisely what it > > was before, and doing registry dumps and checking that things really > > *are* just the same as they were before, is sufficient to fix it. > > Urgh. > > And with interface indexes, it works all the time? So Olli and Lev would appear to be saying. For OpenConnect I haven't actually tested this hypothesis. Unfortunately I'd need to reimplement the get_adapter_index stuff under LGPL first... -- dwmw2
smime.p7s
Description: S/MIME cryptographic signature
