From: "Peter Müller" <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 9f94dc123ae84d9d839ada0808c91c9eb0704650
Date: Sat, 18 Jun 2022 14:40:55 +0000 [thread overview]
Message-ID: <4LQJVv2v3Dz2xv4@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2272 bytes --]
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 2.x development tree".
The branch, next has been updated
via 9f94dc123ae84d9d839ada0808c91c9eb0704650 (commit)
from 01b3a62a35a38db9d67121e66f983c0e0a38ca46 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit 9f94dc123ae84d9d839ada0808c91c9eb0704650
Author: Peter Müller <peter.mueller(a)ipfire.org>
Date: Sat Jun 18 14:40:29 2022 +0000
Update rootfiles to reflect OpenVPN 2FA changes
Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/common/openvpn | 1 +
config/rootfiles/common/web-user-interface | 2 ++
2 files changed, 3 insertions(+)
Difference in files:
diff --git a/config/rootfiles/common/openvpn b/config/rootfiles/common/openvpn
index 1784651b4..d9848a579 100644
--- a/config/rootfiles/common/openvpn
+++ b/config/rootfiles/common/openvpn
@@ -36,6 +36,7 @@ var/ipfire/ovpn/crls
var/ipfire/ovpn/n2nconf
#var/ipfire/ovpn/openssl
var/ipfire/ovpn/openssl/ovpn.cnf
+var/ipfire/ovpn/openvpn-authenticator
var/ipfire/ovpn/ovpn-leases.db
var/ipfire/ovpn/ovpnconfig
var/ipfire/ovpn/scripts
diff --git a/config/rootfiles/common/web-user-interface b/config/rootfiles/common/web-user-interface
index a5973f9e4..3c47dcdba 100644
--- a/config/rootfiles/common/web-user-interface
+++ b/config/rootfiles/common/web-user-interface
@@ -236,6 +236,8 @@ srv/web/ipfire/html/images/printer-error.png
srv/web/ipfire/html/images/printer.png
srv/web/ipfire/html/images/process-stop.png
srv/web/ipfire/html/images/process-working.png
+srv/web/ipfire/html/images/qr-code.png
+srv/web/ipfire/html/images/qr-code.svg
srv/web/ipfire/html/images/reload.gif
srv/web/ipfire/html/images/start-here.png
srv/web/ipfire/html/images/stock_down-16.png
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2022-06-18 14:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4LQJVv2v3Dz2xv4@people01.haj.ipfire.org \
--to=git@ipfire.org \
--cc=ipfire-scm@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