public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: ummeegge <ummeegge@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 14:18:15 +0200	[thread overview]
Message-ID: <1530620295.8483.5.camel@ipfire.org> (raw)
In-Reply-To: <5151d8fbf09ed5632c1d39bd70af7432ca6c4a3f.camel@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1150 bytes --]

Hi Michael,
thanks for merging. I have seen that you´d applied version 1 of this
patch
https://git.ipfire.org/?p=ipfire-2.x.git;a=blobdiff;f=html/cgi-bin/ovpnmain.cgi;h=c0c7cff6d87f6e18206129ab196172be61683a38;hp=5cd19a0f38f564c54e672814e0b5918134889b17;hb=15a3aa45cf27c61a581f892b5f3a3905335a12b0;hpb=8ae4010b312830bce82721325f0aeae524b2810a

but there´s a version 2 of it 
https://patchwork.ipfire.org/patch/1842/ 
which we should in any case prefer.

This is my fault since i didn´t use the same commit name, just used the same message-id in the commit.

Sorry for that.

Best,

Erik

P.S. I do have some more OpenVPN patches (extensions no bugs), should i commit some more or should we wait until the next release ?

Am Dienstag, den 03.07.2018, 10:52 +0100 schrieb Michael Tremer:
> 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
> > 

  reply	other threads:[~2018-07-03 12:18 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
2018-07-03 12:18     ` ummeegge [this message]
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=1530620295.8483.5.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