Hi, (copying in openvpn-devel as the author of the offending patch is not reading -users)
On Mon, Aug 28, 2017 at 09:50:12AM +0200, Eike Lohmann wrote:
> > I believe this simply infers that 'previous' <connection> "blocks" will not
> > be
> > effected by this _pushed_ option.
> >
> > It is a very dodgy message none the less ..
>
> Yes, I also think so.
Indeed, it shouldn't print the <connection> message for pushed options
- though I'm not sure why it does - or, phrased differently, why nobody
else has stumbled across this when the corresponding change has been
in-tree since December 2013...
Author: Arne Schwabe <a...@rfc2549.org>
Date: Tue Dec 17 11:22:47 2013 +0100
Add warning for using connection block variables after connection blocks
In 2.3 some options that were allowed only in global config before have
been moved to connection blocks. This changes the behaviour if the
variables were defined after connection block. This patch adds a warning
to catch these mistakes.
Could you throw a log that shows what the server pushes and then the
warning message (plus the client config, stripped of all sensitive stuff,
of course) into our trac? Then it won't get lost and we can go and
investigate...
The option parser is a big chunk of magic, so it's possible that some
extra conditions need to be checked before printing the message...
thanks,
gert
--
USENET is *not* the non-clickable part of WWW!
//www.muc.de/~gert/
Gert Doering - Munich, Germany g...@greenie.muc.de
fax: +49-89-35655025 g...@net.informatik.tu-muenchen.de
signature.asc
Description: PGP signature
------------------------------------------------------------------------------ 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
