public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: hostapd 2.7 - patches still needed?
Date: Tue, 05 Mar 2019 19:19:47 +0100	[thread overview]
Message-ID: <f271bd22-f2b2-4e63-c772-2b51f572b125@ipfire.org> (raw)
In-Reply-To: <5C5B5F40-3945-418E-B382-174FBA567922@ipfire.org>

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

Hi,

Since both - 'hostapd' AND 'wpa_supplicant' - needed an update, I sent
in a patch series. Please see below "Patch 1/2 hostapd..." and "Patch
2/2 wpa_supplicant...").

Obsolete patches were deleted. I kept the two important ones.

I hope its correct this way.

Both applied here.

Best,
Matthias

On 05.03.2019 10:36, Michael Tremer wrote:
> Hi,
> 
>> On 4 Mar 2019, at 12:50, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
>> 
>> Hi,
>> 
>> can anyone tell me if the 'rebased-v2.6...'-patches for 'hostapd 2.6'
>> are still needed in 'hostapd 2.7’?
> 
> No, those are not required any more because those vulnerabilities should be fixed in the 2.7 release.
> 
>> I made a quick testrun and most of them answer with "Reversed (or
>> previously applied) patch detected!”
> 
> Indeed.
> 
>> As I see it, 'hostapd-2.6-noscan.patch' should probably stay, line
>> numbers would have to be adjusted.
>> 
>> The same applies to 'hostapd-2.3_increase_EAPOL-timeouts.patch’.
> 
> Please keep those patches. It is fine that the lines might have moved. That is why we have patch which takes care of this. There is no need to touch them if they still apply.
> 
> Best,
> -Michael
> 
>> Any hints?
>> 
>> Best,
>> Matthias
> 
> 


  parent reply	other threads:[~2019-03-05 18:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-04 12:50 Matthias Fischer
2019-03-05  9:36 ` Michael Tremer
2019-03-05 17:30   ` Matthias Fischer
2019-03-05 18:19   ` Matthias Fischer [this message]
2019-03-05 11:32 ` Arne Fitzenreiter
2019-03-05 17:36   ` Matthias Fischer

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=f271bd22-f2b2-4e63-c772-2b51f572b125@ipfire.org \
    --to=matthias.fischer@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