Hi, Quoting from the 26th March meeting summary
> Noted that the combination of a username-only --auth-user-pass and > --management-query-passwords does not work. Dazo will take a stab at > fixing the actual problem. There is already a > GET_USER_PASS_PASSWORD_ONLY flag which just needs to be processed > correctly when the management interface is in action. That's not very useful as GET_USER_PASS_PASSWORD_ONLY is currently meant to prompt for the private key password, token password etc. The GUI will treat any 'Auth' request to mean both username and password. In other words, a management client only sees the prompt and there is no defined prompt string for auth-user-pass password only. Also, asking for a password without at least displaying the username is confusing and there is currently no way of indicating the username in such a request. I considered several options for fixing this but all involve some regression that may not be acceptable. An option is to step back when only username is found in the file and ask for both username and password from the management with the usual Auth request. Do this only if --management-query-passwords is present. But even that is a regression as currently, in such cases, the console will be queried. There could be some users out there with those options in the config, but not using the GUI or any management client, and rely on prompting for password via the console. > An attempt to document the limitation plus related discussion is here: > > <https://patchwork.openvpn.net/patch/1040/> > > Further discussion of the issue is available here: > > <https://www.mail-archive.com/openvpn-devel@lists.sourceforge.net/msg12835.html> > Selva _______________________________________________ Openvpn-devel mailing list Openvpn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-devel
