From: Philipp Psurek <philipp.psurek@gmail.com>
To: "Martin Hundebøll" <martin@hundeboll.net>
Cc: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] [PATCH] batman-adv: Check size information when reassembling fragments
Date: Tue, 25 Nov 2014 22:16:28 +0100 [thread overview]
Message-ID: <1416950188.2605.3.camel@gmail.com> (raw)
In-Reply-To: <5474CCF8.9030008@hundeboll.net>
[-- Attachment #1: Type: text/plain, Size: 1303 bytes --]
Hi Martin, hi Sven, hi all,
thanks for working on my bug.
Am Dienstag, den 25.11.2014, 19:39 +0100 schrieb Martin Hundebøll:
> Can you please test this patch, and report back if it fixes your crash?
After I tweeted about this bug in my Community with link to my thread in
this ML telling there is no gateway for now and switching the VM to
3.17.4 8,5 hours from now; the VM didn't crush. It might be the attacker
is sleeping because there were no gateway announced through DHCP or some
changes in the new version prevent the kernel panic:
35e95fae72ddb67ef94395d99abc48589ce17875
dd8aaf1f380e008044857d7d2293e8e2824772b8
5a282822a9e472a41a7e2db71903a1c6654c634a
dmesg screams “UDP: bad checksum.” all the time, but it's to soon to
tell.
I test this patch if the VM crashes again. If the VM didn't crash until
Sunday I do a kernel downgrade to 3.17.3 or 3.16.7 with your patch and
report. Or should I implement your patch immediately on the old kernel
to prove your work without waiting? It would be much convenient to
implement this during an actual attack and it would much more prove your
work.
I'll report soon. Thanks for your work and Batman-adv.
Best regards
Philipp
________________________
Freifunk Rheinland e. V.
– Funkzelle Wuppertal –
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-11-25 21:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-25 18:06 [B.A.T.M.A.N.] [PATCH] batman-adv: Check size information when reassembling fragments Sven Eckelmann
2014-11-25 18:11 ` Christian Huldt
2014-11-25 18:39 ` Martin Hundebøll
2014-11-25 21:16 ` Philipp Psurek [this message]
2014-11-30 10:36 ` Philipp Psurek
2014-11-30 11:20 ` Philipp Psurek
2014-11-30 12:26 ` Martin Hundebøll
2014-11-30 13:35 ` Philipp Psurek
2014-11-30 13:40 ` Martin Hundebøll
2014-11-30 14:07 ` Philipp Psurek
2014-11-30 17:04 ` Philipp Psurek
2014-11-30 18:11 ` Philipp Psurek
2014-11-30 18:35 ` Philipp Psurek
2014-11-30 20:04 ` Philipp Psurek
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=1416950188.2605.3.camel@gmail.com \
--to=philipp.psurek@gmail.com \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=martin@hundeboll.net \
/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