From: ummeegge <ummeegge@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: OpenVPN-2.5.0 update procedure and idea collector
Date: Sun, 29 Nov 2020 12:15:58 +0100 [thread overview]
Message-ID: <5b3cc01fb12e1589b93c503c97986807ef81e7ba.camel@ipfire.org> (raw)
In-Reply-To: <c8e50e8ab753e15d6688263e90fca924df941901.camel@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2025 bytes --]
Hi all,
another bug has been fixed -->
https://git.ipfire.org/?p=people/ummeegge/ipfire-2.x.git;a=commit;h=211bce2dc6f9a3c0fcdee61f3afc0d3c2283f375
. If the save button in the global section is used, it deletes the --auth parameter, this diff fixes it.
for manual changes:
--- /srv/web/ipfire/cgi-bin/ovpnmain.cgi_advanced_encryption 2020-
11-27 10:37:47.405168037 +0100
+++ /srv/web/ipfire/cgi-bin/ovpnmain.cgi 2020-11-29
11:59:02.846338304 +0100
@@ -1303,7 +1303,6 @@
$vpnsettings{'DDEST_PORT'} = $cgiparams{'DDEST_PORT'};
$vpnsettings{'DMTU'} = $cgiparams{'DMTU'};
$vpnsettings{'DCOMPLZO'} = $cgiparams{'DCOMPLZO'};
- $vpnsettings{'DAUTH'} = $cgiparams{'DAUTH'};
#wrtie enable
if ( $vpnsettings{'ENABLED_BLUE'} eq 'on' ) {system("touch
${General::swroot}/ovpn/enable_blue 2>/dev/null");}else{system("unlink
${General::swroot}/ovpn/enable_blue 2>/dev/null");}
Am Samstag, den 28.11.2020, 06:52 +0100 schrieb ummeegge:
Hi all,
made some fixes
- --tls-auth will now be displayed and saved correctly.
- de.pl needed other 'save-enc-options' name since it was a double.
Fixes tls-crypt key generation.
- Fixed comments and changed box size to prevent line break.
New version is here
https://git.ipfire.org/?p=people/ummeegge/ipfire-2.x.git;a=commit;h=7bd13546f3c5e28fd62e25b487e440690860339b
located.
Best,
Erik
Am Donnerstag, den 26.11.2020, 19:47 +0100 schrieb ummeegge:
Hi all,
for the interested ones, have push the current state to my repo which
can be found in here -->
https://git.ipfire.org/?p=people/ummeegge/ipfire-2.x.git;a=commit;h=34af1d714178b2cd0c27e8c39052a8c7ce87d116
feel free to test and criticize it :-) .
After integration and configuration, the 'save' button in the global
section should also be pushed since --cipher will replaced by --data-
channel-fallback. For the langs files, a update-lang-cache should be
executed via console so the changes can take affect.
Happy testing. Best,
Erik
next prev parent reply other threads:[~2020-11-29 11:15 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-22 16:30 ummeegge
2020-11-23 9:14 ` ummeegge
2020-11-23 14:28 ` Kienker, Fred
2020-11-23 14:52 ` ummeegge
2020-11-23 18:06 ` Michael Tremer
2020-11-26 18:47 ` ummeegge
2020-11-26 22:33 ` Adolf Belka
2020-11-27 7:20 ` ummeegge
2020-11-27 12:19 ` Adolf Belka
2020-11-27 13:23 ` ummeegge
2020-11-27 16:43 ` ummeegge
2020-11-27 12:40 ` Adolf Belka
2020-11-27 13:24 ` ummeegge
2020-11-28 5:52 ` ummeegge
2020-11-28 14:12 ` Adolf Belka
2020-11-28 16:00 ` Adolf Belka
2020-11-29 11:15 ` ummeegge [this message]
2020-11-29 13:12 ` Adolf Belka
2020-11-29 18:36 ` ummeegge
2020-11-23 11:41 ` Adolf Belka
2020-11-23 14:44 ` ummeegge
2020-11-23 18:00 ` Michael Tremer
2020-11-23 22:29 ` Adolf Belka
2020-11-24 15:27 ` ummeegge
2020-12-14 14:13 ` Michael Tremer
2020-12-14 14:09 ` Michael Tremer
2020-11-23 17:58 ` Michael Tremer
2020-11-23 19:49 ` ummeegge
2020-11-23 22:38 ` Adolf Belka
2020-11-25 17:10 ` ummeegge
2020-12-14 14:05 ` Michael Tremer
[not found] <92ba003d-a1a9-4f7e-0608-35ff42f64bf8@gmail.com>
2020-12-01 4:26 ` ummeegge
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=5b3cc01fb12e1589b93c503c97986807ef81e7ba.camel@ipfire.org \
--to=ummeegge@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