Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
To: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] dnsmasq2.73 security issue & fix
Date: Sun, 17 May 2015 19:13:55 +0100	[thread overview]
Message-ID: <5558DA63.9090704@darbyshire-bryant.me.uk> (raw)

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

Hi All,

I know some of you are following the dnsmasq bleeding edge.  Please be aware there's a buffer overflow style security issue in (according to the dnsmasq list) all test/release candidate versions of 2.73.  2.73rc8 includes a fix.  Openwrt CC trunk 45693 has been updated to the fixed rc8 version.

It's worth upgrading not only to address the security issue but also to get the latest dnssec udp fragmentation/tcp fallback handling enhancements.

Hope that helps.

-- 
Thanks,

Kevin@Darbyshire-Bryant.me.uk



[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4791 bytes --]

                 reply	other threads:[~2015-05-17 18:14 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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

  List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5558DA63.9090704@darbyshire-bryant.me.uk \
    --to=kevin@darbyshire-bryant.me.uk \
    --cc=cerowrt-devel@lists.bufferbloat.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