On Sun, 2010-02-28 at 07:47 -0500, Chaskiel Grundman wrote: > > > > Try this and see if it's the HTTP/1.0 stuff. Then if not you can try the > > other commits in between (which may need a little massaging, but not a lot): > > > > git reset --hard 7733c517d7d22ef9b706176b21e1e5e270c65aa5 > > git show cc64d59d8132350cadf7adf91857597795eb9090 | sed s/strcasecmp/strcmp/g > > | patch -p1 > > This results in a prompt for the password, so the problem is in those > patches, not the intermediate ones. I see absolutely no reason why this should be necessary, but: http://git.infradead.org/users/dwmw2/openconnect.git/commitdiff/357c85e8 Thanks for the excellent report and subsequent debugging. I'll probably do a 2.22 release when I get home in a couple of weeks' time... if people stop reporting regressions :) -- David Woodhouse Open Source Technology Centre David.Woodhouse at intel.com Intel Corporation
