Hi On Tue, Aug 7, 2018 at 5:01 PM, Gert Doering <g...@greenie.muc.de> wrote: > >> > in the LinOTP URL - so, it didn't decode it, because the second ':' >> > was missing (if I put a blank in there, I get pass=mypin%20). >> > >> > Is this intentional? Should it be that way? >> >> If you are constructing the SCRV1: line using a custom UI, >> I would suggest to add the second colon. If using Windows-GUI or running >> OpenVPN from command line we'll need to fix this one place >> or the other. > > Command line client (git:master/5961250e776194a4, what I happened to > have lying around), run with a config file that has > > auth-user-pass > auth-nocache > auth-retry interact > static-challenge "token value: " 1 > > in it, and pressing <return> at the > > CHALLENGE: token value: _ > > prompt.
I cannot reproduce this but the plugin was not able to handle an empty challenge response. The patch sent to the list should fix that. With that just pressing <return> at the challenge prompt behaves as expected (on unpack up->password gets the user input, up->response stays empty). I haven't tested this using LinOTP, but should work. Selva ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Openvpn-devel mailing list Openvpn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-devel
