Bug#393608: libnss-mdns: Edits nsswitch.conf, throwing away my changes
On Fri, 12.01.07 12:59, Loïc Minier ([EMAIL PROTECTED]) wrote:
Hi!
Sorry for the late response. I have just come back from .au and still
am eating thhrough 800+ non-spam mails, which arrived since I left.
On Fri, Jan 12, 2007, Lennart Poettering wrote:
Short: If built with --enable-legacy nss-mdns is only half-way IPv6
capable. If built with --disable-legacy nss-mdns is fully IPv6 capable.
Thanks!
So is there any difference between
/usr/lib/libnss_mdns{,4,6}{,_minimal}*so.2 with --disable-legacy?
Yes.
the moudle name suffix 4, 6, or specifies the family of the addresses
that
are resolved. i.e. specifies whether A, or both RRs should be
looked for.
If --enable-legacy is passed, than only IPv4 UDP packets will be used
for resolving - unless avahi-daemon is found in which case also IPv6
UDP packets are used.
If --disable-legacy is passed nss-mdns relies exclusively on
avahi-daemon and thus both IPv4 UDP and IPv6 UDP is used (depending on
the daemon config).
The _minimal just modifies the behaviour for host names not ending
in .local and addresses not starting with 169.254/fe80::.
Yeah, I know, it's confusing. ;-)
The major issue is to understand that you can resolve A records via
both IPv4 and IPv6 and the same is true for records. A records
are address records for IPv4, and are records for IPv6 addresses.
Is that cleared up now?
Greetings from Sydney (where linux.conf.au will start in a few days).
Happy conferencing!
The conferences have been awesome! Rock! Rock! Rock! ;-)
if you are interested you can watch Trent's and my Avahi talk at lca:
http://mirror.linux.org.au/linux.conf.au/2007/video/monday/monday_1150_GNOME.ogg
(Theora)
http://0pointer.de/public/avahi-presentation-lca2007.pdf
And another one of me talking about PulseAudio:
http://mirror.linux.org.au/pub/linux.conf.au/2007/video/talks/211.ogg (Theora)
http://0pointer.de/public/pulseaudio-presentation-lca2007.pdf
Have fun!
Lennart
--
Lennart Poettering; lennart [at] poettering [dot] net
ICQ# 11060553; GPG 0x1A015CC4; http://0pointer.net/lennart/
Bug#393608: libnss-mdns: Edits nsswitch.conf, throwing away my changes
Hi, (I'm Cc:ing the bug so that I can point people at the explanations you gave.) On Sun, Feb 04, 2007, Lennart Poettering wrote: the moudle name suffix 4, 6, or specifies the family of the addresses that are resolved. i.e. specifies whether A, or both RRs should be looked for. Ok; I thought it was influencing use of IPv4 or v6 or any for resolution, not record types, but this is cleared up now. If --enable-legacy is passed, than only IPv4 UDP packets will be used for resolving - unless avahi-daemon is found in which case also IPv6 UDP packets are used. Ok, no IPv6 mini-stack. If --disable-legacy is passed nss-mdns relies exclusively on avahi-daemon and thus both IPv4 UDP and IPv6 UDP is used (depending on the daemon config). Of course. The _minimal just modifies the behaviour for host names not ending in .local and addresses not starting with 169.254/fe80::. Ah, hmm ok. Yeah, I know, it's confusing. ;-) I suppose it would be nice to copy paste your mail in the next version of the documentation! :) The 4/6 names for the *.so are especially confusing because they are close to IPv4 and IPv6, not close to A and . The major issue is to understand that you can resolve A records via both IPv4 and IPv6 and the same is true for records. A records are address records for IPv4, and are records for IPv6 addresses. Is that cleared up now? It's ok, I've been playing a lot with v6 in the past and do understand the difference; thanks for clearing things up with respect to libnss-mdns! Bye, -- Loïc Minier [EMAIL PROTECTED]
Bug#393608: libnss-mdns: Edits nsswitch.conf, throwing away my changes
Hi There, On Sun, Dec 24, 2006 at 06:32:39PM +0100, Lo??c Minier wrote: tag 393608 + confirmed stop On Wed, Oct 18, 2006, Sam Morris wrote: I previously had 0.8-5 installed. Before that I had 0.8-4.2 with the same configuration (that I came to myself after consulting upstream's thoughts on the matter). The maintainer added postinst snippets in version 0.8-6 to revert the automatic additions of mdns entries in /etc/nsswitch.conf in prior versions. The postinst snippets in question are terribly broken as these are run for upgrades from versions 0.8-4.2 and 0.8-5 *AND* for initial installs and since there is no way to differenciate between a locally configured nsswitch.conf and an automatically modified nsswitch.conf, the removal of mdns entries in unconditional and will break the mdns setup of any system... I beleive it is worth noting that the recommended upstream string does not do IPv6, and given that IPv6 is a goal of etch (last time I checked?) it may be reasonable to enable that portion. Possibly at this stage may not be reasonable to do but I still think it's worth noting none the less. Cheers, Trent -- Lo?c Minier [EMAIL PROTECTED] Forget your stupid theme park! I'm gonna make my own! With hookers! And blackjack! In fact, forget the theme park! -- Bender -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#393608: libnss-mdns: Edits nsswitch.conf, throwing away my changes
On Tue, Dec 26, 2006, Trent Lloyd wrote: I beleive it is worth noting that the recommended upstream string does not do IPv6, and given that IPv6 is a goal of etch (last time I checked?) it may be reasonable to enable that portion. Possibly at this stage may not be reasonable to do but I still think it's worth noting none the less. I've checked with the upstream author and in fact this is not the case: - when built with --enable-legacy (as in the past), libnss-mdns will support A and requests but only over IPv4 - when built with --disable-legacy (as is the case now), libnss-mdns will forward the request to avahi which supports A and over both IPv4 and IPv6. Bye, -- Loïc Minier [EMAIL PROTECTED]
Bug#393608: libnss-mdns: Edits nsswitch.conf, throwing away my changes
Howdy, On Fri, Jan 12, 2007 at 01:02:06PM +0100, Lo?c Minier wrote: On Tue, Dec 26, 2006, Trent Lloyd wrote: I beleive it is worth noting that the recommended upstream string does not do IPv6, and given that IPv6 is a goal of etch (last time I checked?) it may be reasonable to enable that portion. Possibly at this stage may not be reasonable to do but I still think it's worth noting none the less. I've checked with the upstream author and in fact this is not the case: - when built with --enable-legacy (as in the past), libnss-mdns will support A and requests but only over IPv4 Yes however my point is to actually speak over IPv6 not just resolve addresses. - when built with --disable-legacy (as is the case now), libnss-mdns will forward the request to avahi which supports A and over both IPv4 and IPv6. Avahi also has IPv6 disabled by default (I hope to change this upstream at some point but it requires careful consideration and we may make some API changes to make this 'easier'), also I would assume that 'mdns4' would instruct avahi to only return IPv4 records (which is possible) I will need to confirm this with lennart however I doubt that is not the case. Cheers, Trent Bye, -- Lo?c Minier [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#393608: libnss-mdns: Edits nsswitch.conf, throwing away my changes
Hi, On Sat, Jan 13, 2007, Trent Lloyd wrote: - when built with --enable-legacy (as in the past), libnss-mdns will support A and requests but only over IPv4 Yes however my point is to actually speak over IPv6 not just resolve addresses. Yes, but please note that this *when built with --enable-legacy*, which isn't the case since version 0.8-6.1 in Debian. - when built with --disable-legacy (as is the case now), libnss-mdns will forward the request to avahi which supports A and over both IPv4 and IPv6. Avahi also has IPv6 disabled by default (I hope to change this upstream at some point but it requires careful consideration and we may make some API changes to make this 'easier'), also I would assume that 'mdns4' would instruct avahi to only return IPv4 records (which is possible) I will need to confirm this with lennart however I doubt that is not the case. Ok, so your remark is relevant for avahi. Perhaps you can simply request that avahi be built with IPv6 by default in Debian via a new bug report against avahi? Bye, -- Loïc Minier [EMAIL PROTECTED]
Bug#393608: libnss-mdns: Edits nsswitch.conf, throwing away my changes
tag 393608 + confirmed stop On Wed, Oct 18, 2006, Sam Morris wrote: I previously had 0.8-5 installed. Before that I had 0.8-4.2 with the same configuration (that I came to myself after consulting upstream's thoughts on the matter). The maintainer added postinst snippets in version 0.8-6 to revert the automatic additions of mdns entries in /etc/nsswitch.conf in prior versions. The postinst snippets in question are terribly broken as these are run for upgrades from versions 0.8-4.2 and 0.8-5 *AND* for initial installs and since there is no way to differenciate between a locally configured nsswitch.conf and an automatically modified nsswitch.conf, the removal of mdns entries in unconditional and will break the mdns setup of any system... -- Loïc Minier [EMAIL PROTECTED] Forget your stupid theme park! I'm gonna make my own! With hookers! And blackjack! In fact, forget the theme park! -- Bender
Bug#393608: libnss-mdns: Edits nsswitch.conf, throwing away my changes
severity 393608 important thanks This is a bug in the package and a policy violation, for discarding the user's local configuration. It is not in and of itself release-critical, because the bug only manifests when upgrading from particular unreleased versions of the package. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#393608: libnss-mdns: Edits nsswitch.conf, throwing away my changes
Hi Sam, On 10/17/06, Sam Morris [EMAIL PROTECTED] wrote: Package: libnss-mdns Version: 0.8-6 Severity: serious Justification: Policy 10.7.3 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The package threw away my changes to /etc/nsswitch.conf: [snip] From what version of libnss-mdns did you upgrade? Was it either 0.8-4.2 or 0.8-5? Thanks, Anand -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#393608: libnss-mdns: Edits nsswitch.conf, throwing away my changes
The package threw away my changes to /etc/nsswitch.conf: [snip] From what version of libnss-mdns did you upgrade? Was it either 0.8-4.2 or 0.8-5? I previously had 0.8-5 installed. Before that I had 0.8-4.2 with the same configuration (that I came to myself after consulting upstream's thoughts on the matter). Thanks, Anand -- Sam Morris http://robots.org.uk/ PGP key id 1024D/5EA01078 3412 EA18 1277 354B 991B C869 B219 7FDB 5EA0 1078 signature.asc Description: This is a digitally signed message part
Bug#393608: libnss-mdns: Edits nsswitch.conf, throwing away my changes
Package: libnss-mdns Version: 0.8-6 Severity: serious Justification: Policy 10.7.3 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The package threw away my changes to /etc/nsswitch.conf: - --- /etc/nsswitch.conf.pre-upgrade 2006-10-16 09:52:48.0 +0100 +++ /etc/nsswitch.conf 2006-10-17 01:26:20.0 +0100 @@ -8,7 +8,7 @@ group: compat shadow: compat - -hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4 +hosts: files dns networks: files protocols: db files - -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (530, 'testing'), (520, 'unstable'), (510, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-2-k7 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Versions of packages libnss-mdns depends on: ii base-files 3.1.16 Debian base system miscellaneous f ii libc62.3.6.ds1-4 GNU C Library: Shared libraries Versions of packages libnss-mdns recommends: pn zeroconf none (no description available) - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFNCOcshl/216gEHgRAsm+AKDZikuianz9vsxUyqtE0YDrHohk3wCgig4V dYPemj/NEAYYDIx1msBGZGA= =fTj3 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
