From: ummeegge <ummeegge@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Testing Core Update 118
Date: Tue, 06 Feb 2018 10:37:26 +0100 [thread overview]
Message-ID: <29B2F501-2E87-4252-BB50-C78107855534@ipfire.org> (raw)
In-Reply-To: <1517498173.2319.5.camel@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1367 bytes --]
Hello,
i wanted to ask if it is possible to add the OpenSSL configuration for OpenVPN ovpn.cnf --> https://git.ipfire.org/?p=ipfire-2.x.git;a=blob;f=config/ovpn/openssl/ovpn.cnf;h=40daf2a0a886dd4957df00c3303d3504f8cb0bc0;hb=refs/heads/core115 again to Core 118 update ?
Since there are a couple of users in the IPFire forum which reports the same issue --> https://forum.ipfire.org/viewtopic.php?f=16&t=19738p112874#p112874 and --> https://forum.ipfire.org/viewtopic.php?f=27&t=20180 , it seems that ovpn.cnf has been missing with the Core 115 update but the ovpnmain.cgi changes has been delivered.
Might be great if we can deliver this file again to complete this patch otherwise it does not work...
Am 01.02.2018 um 16:16 schrieb Michael Tremer:
>
> That sounds good. They have their own configuration file format for
> some modules stuff but since we don't intend to use any of that, we
> should be fine here.
>
> Would you update those packages and rebase the branch on next since you
> have already been working on this? Please send this over to Peter for
> review then and let him test the TCP logging capabilities since he was
> the one who required this in the first place.
>
Did that now and have changed also the topic to here --> https://lists.ipfire.org/pipermail/development/2018-February/004011.html .
Best,
Erik
next prev parent reply other threads:[~2018-02-06 9:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1517416528.2586.92.camel@ipfire.org>
2018-02-01 8:41 ` ummeegge
2018-02-01 11:37 ` Michael Tremer
2018-02-01 14:43 ` ummeegge
2018-02-01 15:16 ` Michael Tremer
2018-02-02 19:49 ` ummeegge
2018-02-03 19:42 ` ummeegge
2018-02-06 9:37 ` ummeegge [this message]
2018-02-06 16:30 ` Michael Tremer
2018-01-30 17:44 Peter Müller
2018-01-30 20:57 ` 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=29B2F501-2E87-4252-BB50-C78107855534@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