Hi, On Sun, Dec 20, 2020 at 5:38 PM Gert Doering <g...@greenie.muc.de> wrote:
> Hi, > > On Sun, Dec 20, 2020 at 04:00:13PM +0100, Arne Schwabe wrote: > > > ... and the client would then either print this on the console > > > (if !management) or dump it to management, where the GUI/Tunnelblick > > > could pick it up and create a popup window. > > > > > See --echo. That is basically what you desribe as info-msg in your mail > > While echo sounds as if it would do what I want, it doesn't. > > Echo is "something magic" - it is never printed by the 2.x client, it > is not even logged. And it's not displayed by the GUIs either, but > instead it can be used to "do things"... > The "not getting logged" concern is easy to fix. What echo does is to get a message from the server to the client-side UI. Currently GUI's do not display them because so far the only meanings we have assigned to echo commands are as directives like save-password or forget-password. But that doesn't mean we can't use them for messages.And, that's exactly what we discussed 3 years ago -- see the draft implementation from Nov 2017 that I posted. Here is the link again. https://github.com/selvanair/openvpn-gui/releases/tag/v11-echo-msg I got no feedback then nor now. > So less "echo to user" but "send this string to the management interface > and make the mgmt client do something magic"... > A message to the user can be delivered in a useful fashion only if there is a UI. The core itself can only write the message to log which may not be seen in time, or to the console if one exists. And, IMO, any decent UI of openvpn should use the management interface -- almost all do (except NM?). I thought we already went through this when we discussed the proposed "echo msg" in considerable detail 3 years ago. Selva
_______________________________________________ Openvpn-devel mailing list Openvpn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-devel
