[HELP] Option for token-field

[Daniel Lenski]

On Wed, Apr 4, 2018 at 11:46 AM, Tyson Vinson <tyson at ninjut.su> wrote:
> I'm connecting to a VPN endpoint that uses a non-standard field name
> for the oath/totp challenge. There was a set of patches to openconnect
> here http://lists.infradead.org/pipermail/openconnect-devel/2015-December/003330.html
> that add a token-field option. These still apply cleanly and the patch
> resolves my issue replying with a token. Can this patchset be applied
> to HEAD? If there was some reason this wasn't merged I'd be happy to
> help get it in to a state where it can be.

I'm glad that patch is useful.

If I remember right, there was some follow-up discussion much later in
which David Woodhouse pointed out that my approach would be hard to
integrate correctly with GUI front-ends, or with multiple sequential
login forms (as Juniper VPNs often use…)

Dan