lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.1109231213580.31698@cobra.newdream.net>
Date:	Fri, 23 Sep 2011 12:15:37 -0700 (PDT)
From:	Sage Weil <sage@...dream.net>
To:	Noah Watkins <noahwatkins@...il.com>
cc:	ceph-devel@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] ceph: use kernel DNS resolver

On Fri, 23 Sep 2011, Noah Watkins wrote:
> On Thu, Sep 22, 2011 at 14:29, Sage Weil <sage@...dream.net> wrote:
> > Currently the dns resolution is handled by mount.ceph and 'rbd map/unmap'.
> > I don't think that will go away (at the very least need to support old
> > kernels).
> 
> This is good to know. I never encountered the DNS lookup because I've
> always used a non-standard installation path, avoiding mount.ceph.
> 
> > Allowing this in the raw kernel interface would be nice, but I don't think
> > we want make DNS_RESOLVER a strict dependency, since it's new, kind of
> > kludgey, and a ripe target for compiling out of small or secure kernels.
> > Can you make it build either with or without it?
> 
> I sent out a new version of the patch that defines a libceph specific 
> configuration option to use the in-kernel dns resolver.

So I was actually thinking we could just #ifdef off of 
CONFIG_DNS_RESOLVER, but I think your approach might be better because 
you'll see it in the config process and turn it on, vs having to dig 
through to wherever DNS_RESOLVER lives in kconfig.

Maybe it should default y though?

sage
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ