Hi, On Fri, Dec 1, 2017 at 10:58 AM, Selva Nair <selva.n...@gmail.com> wrote: > > Hi, > > On Fri, Dec 1, 2017 at 8:53 AM, Arne Schwabe <a...@rfc2549.org> wrote: >> >> Am 30.11.2017 um 03:03 schrieb Selva Nair: >> >> Cross-posting to users and devel as this may be of interest to both. >> >> Hi, >> >> I have made a draft implementation of this feature that was discussed in a >> previous thread. A test executable (GUI only) is in this pre-release: >> >> https://github.com/selvanair/openvpn-gui/releases/tag/v11-echo-msg >> >> It would be great if anyone can test this out[*]. >> >> Thanks, >> >> Selva >> >> [*] Although virtually any text can be sent, some familiarity with openvpn >> config/ccd parsing/quoting and push processing is necessary to get it right >> for non-trivial messages that contain comment characters, commas, new lines >> etc... Short and simple messages must be easy, though. >> >> >> Could we have some text stating that clients might only display one message >> per connect? At the moment you can have multiple "echo msg-notify >> message-title" pushed by the server. I would like to avoid in my client to >> implement logic to display multiple messages. If one message allowed the >> message can become just an Android notification without special logic > > > Yes, we can and probably should document that some clients may only > display one message. Do you also want to say that some clients may > interpret msg-window as msg-notify? > > Even in case of Windows desktop, I think it may be better to display > only one message per connection as otherwise it starts to get very > noisy. At most one message window and one notification. > > Jon, do you plan to document the proposed "echo msg" specs in management > notes or elsewhere? The single message per connect limitation > could be specified there.
I'll be happy to try to document the protocol between OpenVPN and the GUI, including the "msg*" commands and others such as "forget-passwords", "setenv", etc., which we've discussed. However, I'm thinking it should be a separate "doc/gui-notes.txt" document. In a separate document it would be easier to make it clear that it is describing the protocol between the configuration and the GUIs and not get lost in the complexity of the management interface itself. ------------------------------------------------------------------------------ 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
