From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] OpenVPN: Prevent internal server error cause of bad header wrapper
Date: Tue, 03 Jul 2018 10:52:29 +0100 [thread overview]
Message-ID: <5151d8fbf09ed5632c1d39bd70af7432ca6c4a3f.camel@ipfire.org> (raw)
In-Reply-To: <1530534365.8568.1.camel@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1305 bytes --]
Yes, I just did.
I collected all the patches and merged all the package updates first and today I
merged all other smaller changes.
Best,
-Michael
On Mon, 2018-07-02 at 14:26 +0200, ummeegge wrote:
> Hi,
> just wanted to know if this fix will be applied ?
>
> Best,
>
> Erik
>
>
> Am Donnerstag, den 21.06.2018, 11:12 +0200 schrieb Erik Kapfer:
> > This fixes #11772 .
> >
> > If the X509 are deleted, the openvpnctrl output generates a bad
> > header wrapper error from the CGI
> > which causes an internal server error. The redirection of the
> > openvpnctrl output fixes this.
> >
> > Signed-off-by: Erik Kapfer <erik.kapfer(a)ipfire.org>
> > ---
> > html/cgi-bin/ovpnmain.cgi | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/html/cgi-bin/ovpnmain.cgi b/html/cgi-bin/ovpnmain.cgi
> > index 4bc3473..5cd19a0 100644
> > --- a/html/cgi-bin/ovpnmain.cgi
> > +++ b/html/cgi-bin/ovpnmain.cgi
> > @@ -1181,7 +1181,7 @@ SETTINGS_ERROR:
> > delete $confighash{$cgiparams{'$key'}};
> > }
> >
> > - system ("/usr/local/bin/openvpnctrl -drrd $name");
> > + system ("/usr/local/bin/openvpnctrl -drrd $name
> > &>/dev/null");
> > }
> > while ($file = glob("${General::swroot}/ovpn/ca/*")) {
> > unlink $file;
next prev parent reply other threads:[~2018-07-03 9:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-21 9:12 Erik Kapfer
2018-07-02 12:26 ` ummeegge
2018-07-03 9:52 ` Michael Tremer [this message]
2018-07-03 12:18 ` ummeegge
2018-07-03 14:31 ` Michael Tremer
2018-07-03 17:40 ` ummeegge
2018-07-04 13:59 ` Michael Tremer
2018-07-04 22:59 ` 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=5151d8fbf09ed5632c1d39bd70af7432ca6c4a3f.camel@ipfire.org \
--to=michael.tremer@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