References: <20201220105430.GP976@...1296...> <093511bd-43c0-a37c-1d8f-335d9df451d6@...1227...> <20201220185402.GQ976@...1296...> <20201221070420.GW976@...1296...> From: Jan Just Keijser Message-ID: <65cbacc6-0c9f-4c46-04aa-6e707c7d5efd@...1147...> Date: Wed, 23 Dec 2020 12:15:42 +0100 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/alternative; boundary="------------5BD6EED22FEF36F593FB3410" Content-Language: en-US Subject: Re: [Openvpn-devel] wanted: mechanism to send text messages to client List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Selva Nair , Gert Doering Cc: openvpn-devel This is a multi-part message in MIME format. --------------5BD6EED22FEF36F593FB3410 Content-Type: text/plain; charset="utf-8"; format="flowed" Content-Transfer-Encoding: 8bit On 21/12/20 18:22, Selva Nair wrote: > > > On Mon, Dec 21, 2020 at 2:04 AM Gert Doering > wrote: > > Hi, > > On Sun, Dec 20, 2020 at 07:31:42PM -0500, Selva Nair wrote: > > I thought we already went through this when we discussed the > proposed "echo > > msg" in considerable detail 3 years ago. > > Yeah, sorry.  Seems I got distracted and forgot all about the > discussed > "solution space", and just remembered the itch. > > I'm sure the thread is still sitting in my mailbox... will go > looking for > it today. > > > For those who have lost the original threads: > > https://sourceforge.net/p/openvpn/mailman/openvpn-users/thread/CAEsd45T%2Bd6FUJ9Po0KHwtHjfuL9Q2D-poG8yFtY45Qyh%2BtHjkg%40mail.gmail.com/#msg36136236 > > https://sourceforge.net/p/openvpn/mailman/openvpn-devel/thread/CAKuzo_jPThhvXTJAtzhqVUVOLPW1VGu6h2jQhVsHicY8P2WRqA%40mail.gmail.com/#msg36141193 > > That was in Nov-Dec 2017. Actually, I was also thinking of reviving > this only the other day when intimating users about some updates > came up.. Somehow such itches re-surface at the end of the year :) > sorry to chip on so late, but at some point we did have a way to push env vars to the client (back in v2.2 at least): inside a client-connect script you can/could do echo "push \"setenv-safe MSG1 'hello'\"" > $1 echo "push \"setenv-safe MSG2 'download version 2.5 please'\"" >> $1 and then on the client-side you'd simply have to process them (as OPENVPN_MSG1 and OPENVPN_MSG2) - couldn't we reuse that to send messages to a connected client? Sending messages to an unauthenticated client - other than "wrong password , go away" - seems dangerous to me. JM2CW, JJK --------------5BD6EED22FEF36F593FB3410 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: 8bit
On 21/12/20 18:22, Selva Nair wrote:


On Mon, Dec 21, 2020 at 2:04 AM Gert Doering <gert@...1296...> wrote:
Hi,

On Sun, Dec 20, 2020 at 07:31:42PM -0500, Selva Nair wrote:
> I thought we already went through this when we discussed the proposed "echo
> msg" in considerable detail 3 years ago.

Yeah, sorry.  Seems I got distracted and forgot all about the discussed
"solution space", and just remembered the itch.

I'm sure the thread is still sitting in my mailbox... will go looking for
it today.

For those who have lost the original threads:



That was in Nov-Dec 2017. Actually, I was also thinking of reviving this only the other day when intimating users about some updates came up.. Somehow such itches re-surface at the end of the year :)

sorry to chip on so late, but at some point we did have a way to push env vars to the client (back in v2.2 at least):

inside a client-connect script you can/could do

echo "push \"setenv-safe MSG1 'hello'\"" > $1
echo "push \"setenv-safe MSG2 'download version 2.5 please'\"" >> $1

and then on the client-side you'd simply have to process them (as OPENVPN_MSG1 and OPENVPN_MSG2) - couldn't we reuse that to send messages to a connected client? 

Sending messages to an unauthenticated client - other than "wrong password , go away" - seems dangerous to me.

JM2CW,

JJK


--------------5BD6EED22FEF36F593FB3410--