getting beyond 'XML response has no "auth" node' aftermath

[Geert Stappers]

On Sat, Jun 24, 2017 at 10:51:56PM +0100, David Woodhouse wrote:
> On Sat, 2017-06-24 at 22:58 +0200, Geert Stappers wrote:
> > 
> }  ... openconnect manualpage about --protocol ...
> > 
> > I do understand that I missed it previously _and_ shouldn't have to  :-/
> 
> If you're saying you shouldn't have to specify the protocol... yeah, I
> can sympathise with that. We should implement autodetection.
 
I tried to say:
 * I did read the manaul page before posting here
 * Did reread it after getting the reply with  --protocol=nc
 * The manual has documented the option
 * That I needed several readings and extra help to get it
 * On hindsight I could have avoided my posting
   by better Reading The Fine Manual  :-)

About autodetection: Yes, a "nice to have"


> > The VPN server that I use is named "pulse secure".

Name was/is mentioned for people encountering the same problem.
(For the archive, where search engine webcrawlers can pick it up.)
 
> You're using the older 'Network Connect' protocol with it. We don't
> support the newer Pulse protocol yet.

Thanks for the heads-up about a newer protocol.


Groeten
Geert Stappers
-- 
Leven en laten leven