From: Jonathan Nieder <jrnieder@gmail.com>
To: "Kyle J. McKay" <mackyle@gmail.com>
Cc: Git mailing list <git@vger.kernel.org>
Subject: Re: git_inetd_server: run git-http-backend using inetd
Date: Thu, 17 Jul 2014 19:22:08 -0700 [thread overview]
Message-ID: <20140718022208.GQ12427@google.com> (raw)
In-Reply-To: <8E3CD89B-2E47-4CA8-8F3D-598A9BE2AD9F@gmail.com>
Kyle J. McKay wrote:
> On Jul 17, 2014, at 15:10, Jonathan Nieder wrote:
>> It was added to respond to a feature request within Debian but it is
>> intended to eventually go upstream. I'm glad you found this issue
>> before that could happen. :)
>
> Is there some reason the patch is not opt-in at runtime?
Yes, it's a feature for server admins to control where clients
connect, to control where the load goes. If the client has to enable
it explicitly, that defeats the purpose.
I'd much rather fix it than turn it off completely.
[...]
>> Should git automatically disable the SRV lookups when it sees one of
>> the six domains named in RFC6762, or is there some system library call
>> that can use mDNS when appropriate automatically (or get partway there
>> without having to hard-code the domains)?
>
> Sadly I think mDNS support is relegated to an add-on package on
> Linux. And Avahi [1] is the package that generally provides it
> there. The recommended interface for C is the avahi-client API (see
> [2]). However, that is Avahi-only.
[...]
> Even if the choice is to just disable SRV lookups for mDNS hosts at
> a minimum the code will have to determine whether or not the given
> host name is a mDNS name and it can't reliably do that for a host
> name without any dots in it without at least looking at the default
> domain name and possibly the search domain(s) as well.
>
> I think it would be much simpler just to make this opt-in via a
> config option
Thanks for these details. I'll file a bug and mull it over some more.
RFC 6762 makes it clear that what the package is currently doing is
wrong. Given that Debian's libc knows nothing about mdns on its own,
I think I'll need to parse resolv.conf (that's what libc-ares does).
Jonathan
next prev parent reply other threads:[~2014-07-18 2:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-17 21:28 git_inetd_server: run git-http-backend using inetd Kyle J. McKay
2014-07-17 22:10 ` Jonathan Nieder
2014-07-17 23:38 ` Kyle J. McKay
2014-07-18 2:22 ` Jonathan Nieder [this message]
2014-07-18 6:48 ` Kyle J. McKay
2014-07-18 17:16 ` Jonathan Nieder
2014-07-19 0:08 ` Kyle J. McKay
2014-07-19 0:19 ` Jonathan Nieder
2014-07-19 1:54 ` Kyle J. McKay
2014-07-19 6:21 ` Torsten Bögershausen
2014-07-19 17:06 ` Jonathan Nieder
2014-07-20 6:10 ` Torsten Bögershausen
2014-07-20 15:25 ` Torsten Bögershausen
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=20140718022208.GQ12427@google.com \
--to=jrnieder@gmail.com \
--cc=git@vger.kernel.org \
--cc=mackyle@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).