Sorry about the delay - I'm finally getting around to doing this. And now I see that the behaviour has changed since I last tried. Rather than the message I was getting before, it now appears to reject my password. I'm not sure whether this list accepts attachments, and the log is short anyway, so I'll just cut and paste it below. It doesn't look very informative to me, but maybe someone can understand what it means. Cheers, Jonathan $ sudo openconnect --verbose --user <redacted> remote.unimelb.edu.au/staff POST https://remote.unimelb.edu.au/staff Attempting to connect to server 128.250.2.50:443 SSL negotiation with remote.unimelb.edu.au Server certificate verify failed: signer not found Certificate from VPN server "remote.unimelb.edu.au" failed verification. Reason: signer not found Enter 'yes' to accept, 'no' to abort; anything else to view: yes Connected to HTTPS on remote.unimelb.edu.au Got HTTP response: HTTP/1.1 200 OK Content-Type: text/html; charset=utf-8 Transfer-Encoding: chunked Cache-Control: no-cache Pragma: no-cache Connection: Keep-Alive Date: Wed, 25 Sep 2013 03:45:26 GMT X-Aggregate-Auth: 1 HTTP body chunked (-2) XML POST enabled Password: <Type correct password here> POST https://remote.unimelb.edu.au/ Got HTTP response: HTTP/1.1 200 OK Content-Type: text/html; charset=utf-8 Transfer-Encoding: chunked Cache-Control: no-cache Pragma: no-cache Connection: Keep-Alive Date: Wed, 25 Sep 2013 03:45:28 GMT X-Aggregate-Auth: 1 HTTP body chunked (-2) Login failed. Password: <etc.> On 16/09/13 01:14, Kevin Cernekee wrote: > On Sat, Sep 14, 2013 at 7:42 PM, Jonathan Schultz <jonathan at imatix.com> wrote: >>> If you use OpenConnect 5.01 with the --no-xmlpost option, does it work? >> >> >> Yes, that does the trick. >> >> The openconnect manual page indicates that needing to use this option means >> that I have found a bug. Can anyone advise on whether it is useful to report >> it, or are we talking about a known bug? > > Yes, please post or email the entire unredacted log. > > Thanks. >
