Your message dated Tue, 28 May 2013 15:18:59 +0000
with message-id <[email protected]>
and subject line Bug#709179: fixed in dnsmasq 2.66-3
has caused the Debian Bug report #709179,
regarding Please automagically forward to dnscrypt-proxy if available
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
709179: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=709179
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: dnsmasq
Version: 2.66-2
Severity: wishlist
OpenDNS's DNSCrypt client for Linux (called 'dnscrypt-proxy')[0] is not yet
packaged for Debian but some people are already installing it from source
and it is of course possible that it will eventually be packaged. This is a
request that the dnsmasq package be enhanced to make it easy to use dnsmasq
along with dnscrypt-proxy and resolvconf.
Dnscrypt-proxy doesn't cache. So it makes sense to run dnsmasq with caching
turned on and configured to forward queries to dnscrypt-proxy at a loopback
address. The request is that this happen automagically when resolvconf is
also installed. Getting it to happen automagically on a resolvconfful
system just requires tweaking dnsmasq's resolvconf hook script.
Currently dnsmasq's resolvconf hook script gathers all nameserver addresses
from the resolvconf database, excludes dnsmasq's own listen address and
writes the remaining addresses to /var/run/dnsmasq/resolv.conf.
When dnscrypt-proxy is running only dnscrypt-proxy's address should be used.
Let's decide here and now that the name of dnscrypt-proxy's resolvconf
record will be "lo.dnscrypt". (Thus dnscrypt-proxy or its initscript will
do something like "echo 127.0.0.2 | resolvconf -a lo.dnscrypt".)
Dnsmasq's resolvconf hook script should thus be changed such that if
lo.dnscrypt is present, only the address from lo.dnscrypt will be written
to /var/run/dnsmasq/resolv.conf.
Once there is agreement I will submit a patch.
[0]https://github.com/opendns/dnscrypt-proxy
--- End Message ---
--- Begin Message ---
Source: dnsmasq
Source-Version: 2.66-3
We believe that the bug you reported is fixed in the latest version of
dnsmasq, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Simon Kelley <[email protected]> (supplier of updated dnsmasq package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.8
Date: Tue, 28 May 2013 14:39:51 +0000
Source: dnsmasq
Binary: dnsmasq dnsmasq-base dnsmasq-utils
Architecture: source i386 all
Version: 2.66-3
Distribution: unstable
Urgency: low
Maintainer: Simon Kelley <[email protected]>
Changed-By: Simon Kelley <[email protected]>
Description:
dnsmasq - Small caching DNS proxy and DHCP/TFTP server
dnsmasq-base - Small caching DNS proxy and DHCP/TFTP server
dnsmasq-utils - Utilities for manipulating DHCP leases
Closes: 709179
Changes:
dnsmasq (2.66-3) unstable; urgency=low
.
* Update resolvconf script for dnscrypt-proxy integration. (closes: #709179)
Checksums-Sha1:
5ba11f733d26dc729ac9a60a37b327367a68c126 1150 dnsmasq_2.66-3.dsc
d8ce1f3c1910ddad5170e9998a647e7dae1d3877 19720 dnsmasq_2.66-3.diff.gz
ff11d794d05fec063f9528feeb8b7f839505ce0c 391326 dnsmasq-base_2.66-3_i386.deb
4af8e6ff0079f472057ffac4a4e68b3707601949 18596 dnsmasq-utils_2.66-3_i386.deb
0f2b1e4fc80eb1dcd60b607433ac488ea7e0bda3 15712 dnsmasq_2.66-3_all.deb
Checksums-Sha256:
22a7cf7b5eaf132372cd7f40487c95464249b5ec9f90472aac1e60dfa6e6f43a 1150
dnsmasq_2.66-3.dsc
9d22c7e97498db14fcd7b219e39205b5894dc19930c6fedef49cdee7f8330b7c 19720
dnsmasq_2.66-3.diff.gz
232ecddeddb132e79525ada30fedbb425c8fb5cdbd24fd3832c9ea72d3c6db33 391326
dnsmasq-base_2.66-3_i386.deb
34d394dbe155f798829858281d32d55638c43a2fc49d28ee6fb5e7cbc0f5840e 18596
dnsmasq-utils_2.66-3_i386.deb
093f5ac5fa5bf7c9f9c8620533498bd014f42e0af1f1f9fd66c6b62b95c3113b 15712
dnsmasq_2.66-3_all.deb
Files:
7c4bc687091ffa86c174b252b95396e2 1150 net optional dnsmasq_2.66-3.dsc
454f5e05eb50692d55cb075a546a6127 19720 net optional dnsmasq_2.66-3.diff.gz
67c06d4a0fa3adc98a06ca53e13dc2c5 391326 net optional
dnsmasq-base_2.66-3_i386.deb
e9e6c7c92aa5fbcac38959b0a0ccc2dd 18596 net optional
dnsmasq-utils_2.66-3_i386.deb
d5283db4590ff5d9a219dd0f63731bd2 15712 net optional dnsmasq_2.66-3_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iEYEARECAAYFAlGktHAACgkQKPyGmiibgrf5lQCgiwlY9Jf99+UT+G0H4emdV+FL
bvIAnRP4qrNKT1TQyAUg/RwEl9tT4Teu
=oAQI
-----END PGP SIGNATURE-----
--- End Message ---
