public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: "Kienker, Fred" <fkienker@at4b.com>
To: development@lists.ipfire.org
Subject: RE: dnsmasq 2.75, including latest patches from 2016-01-08
Date: Sat, 09 Jan 2016 13:24:58 -0500	[thread overview]
Message-ID: <H000006e001956d1.1452363898.mail.at4b.net@MHS> (raw)
In-Reply-To: <569024E2.2010800@ipfire.org>

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

I will help test this. I likely have the most firewalls affected by this 
issue and can usually spot issues quickly. It is deployed on my test 
system right now and will go to more systems as soon as it shows to be 
stable there. Thanks so much for your hard work on this issue.

Best,
Fred Kienker

-----Original Message-----
From: Matthias Fischer [mailto:matthias.fischer(a)ipfire.org] 
Sent: Friday, January 08, 2016 4:07 PM
To: IPFire: Development-List
Subject: dnsmasq 2.75, including latest patches from 2016-01-08

Hi,

if anyone wants to test, too:

Download:
http://people.ipfire.org/~mfischer/dnsmasq_275_2016_01_08
MD5: f4433dc8df2b86fc16732499d0e0fb94

For new patches included, see:
http://git.ipfire.org/?p=people/mfischer/ipfire-2.x.git;a=commit;h=89188f08c0b7dca3b6cb2b6fd9b412345589569e

This is the compiled binary, nothing more is needed.

- Copy to '/usr/sbin'
- Stop 'dnsmasq' (/etc/init.d/dnsmasq stop)
- Rename (don't forget backing up the *old* version!)
- Start 'dnsmasq' (/etc/init.d/dnsmasq start).

Best,
Matthias



  reply	other threads:[~2016-01-09 18:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-08 21:06 Matthias Fischer
2016-01-09 18:24 ` Kienker, Fred [this message]
2016-01-09 19:35   ` Matthias Fischer
     [not found] <5697447D.4060701@dailydata.net>
2016-01-14 17:42 ` Matthias Fischer
2016-01-14 18:42   ` R. W. Rodolico
2016-01-14 22:50   ` Kienker, Fred

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=H000006e001956d1.1452363898.mail.at4b.net@MHS \
    --to=fkienker@at4b.com \
    --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