From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] ovpnmain.cgi: Fixes bug13869 - shows values from vpnsettings in advanced server page
Date: Fri, 22 Aug 2025 11:45:59 +0200 [thread overview]
Message-ID: <17d10023-b29a-4958-8ae5-1730e9350a66@ipfire.org> (raw)
In-Reply-To: <20250820165147.21850-1-adolf.belka@ipfire.org>
Hi,
I saw that this patch had been accepted and put into next (CU198). I had expected that it would also be put into CU197 Testing as the issue being fixed is part of the openvpn-2.6 changes.
Regards,
Adolf.
On 20/08/2025 18:51, Adolf Belka wrote:
> - In the previous version the cgiparams hash was filled from the ovpn/settings file.
> However with the new version of this file that is no longer done. For the values
> of protocol, redirect_gw, mssfix, dataciphers, route_push the hash file was changed
> from %cgiparams to %vpnsettings. This was not done for the values of dciphers, dauth
> or tlsauth. These values still got their entries from the %cgiparams hash but this
> hash is empty as it has not been filled.
> - This patch replaces the use of $cgiparams with $vpnsettings.
> - Tested this out on my vm testbed and confirmed that the saved values are now shown on
> the advanced settings wui page.
>
> Fixes: bug13869
> Tested-by: Adolf Belka <adolf.belka@ipfire.org>
> Signed-off-by: Adolf Belka <adolf.belka@ipfire.org>
> ---
> html/cgi-bin/ovpnmain.cgi | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/html/cgi-bin/ovpnmain.cgi b/html/cgi-bin/ovpnmain.cgi
> index 83f9fdc02..3a85c11ac 100644
> --- a/html/cgi-bin/ovpnmain.cgi
> +++ b/html/cgi-bin/ovpnmain.cgi
> @@ -2694,18 +2694,18 @@ ADV_ERROR:
> $selected{'DCIPHER'}{'CAST5-CBC'} = '';
> $selected{'DCIPHER'}{'BF-CBC'} = '';
> $selected{'DCIPHER'}{'DES-CBC'} = '';
> - $selected{'DCIPHER'}{$cgiparams{'DCIPHER'}} = 'SELECTED';
> + $selected{'DCIPHER'}{$vpnsettings{'DCIPHER'}} = 'SELECTED';
>
> $selected{'DAUTH'}{'whirlpool'} = '';
> $selected{'DAUTH'}{'SHA512'} = '';
> $selected{'DAUTH'}{'SHA384'} = '';
> $selected{'DAUTH'}{'SHA256'} = '';
> $selected{'DAUTH'}{'SHA1'} = '';
> - $selected{'DAUTH'}{$cgiparams{'DAUTH'}} = 'SELECTED';
> + $selected{'DAUTH'}{$vpnsettings{'DAUTH'}} = 'SELECTED';
>
> $checked{'TLSAUTH'}{'off'} = '';
> $checked{'TLSAUTH'}{'on'} = '';
> - $checked{'TLSAUTH'}{$cgiparams{'TLSAUTH'}} = 'CHECKED';
> + $checked{'TLSAUTH'}{$vpnsettings{'TLSAUTH'}} = 'CHECKED';
>
> &Header::showhttpheaders();
> &Header::openpage($Lang::tr{'status ovpn'}, 1, '');
next prev parent reply other threads:[~2025-08-22 9:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-20 16:51 Adolf Belka
2025-08-22 9:45 ` Adolf Belka [this message]
2025-08-22 13:08 ` Michael Tremer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=17d10023-b29a-4958-8ae5-1730e9350a66@ipfire.org \
--to=adolf.belka@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox