linux-kernel - RE: [PATCH V3 08/14] Tools: hv: Gather DNS information

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: <426367E2313C2449837CD2DE46E7EAF9236C20E7@SN2PRD0310MB382.namprd03.prod.outlook.com>
Date:	Fri, 17 Aug 2012 21:41:42 +0000
From:	KY Srinivasan <kys@...rosoft.com>
To:	Greg KH <gregkh@...uxfoundation.org>
CC:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"devel@...uxdriverproject.org" <devel@...uxdriverproject.org>,
	"olaf@...fle.de" <olaf@...fle.de>,
	"apw@...onical.com" <apw@...onical.com>,
	"ben@...adent.org.uk" <ben@...adent.org.uk>
Subject: RE: [PATCH V3 08/14] Tools: hv: Gather DNS information



> -----Original Message-----
> From: Greg KH [mailto:gregkh@...uxfoundation.org]
> Sent: Friday, August 17, 2012 1:17 PM
> To: KY Srinivasan
> Cc: linux-kernel@...r.kernel.org; devel@...uxdriverproject.org; olaf@...fle.de;
> apw@...onical.com; ben@...adent.org.uk
> Subject: Re: [PATCH V3 08/14] Tools: hv: Gather DNS information
> 
> On Fri, Aug 17, 2012 at 05:07:22PM +0000, KY Srinivasan wrote:
> > > On Thu, Aug 16, 2012 at 06:32:19PM -0700, K. Y. Srinivasan wrote:
> > > > Now, gather DNS information. Invoke an external script (that can be
> > > > distro dependent) to gather the DNS information.
> > >
> > > Where is that script?  Why a script, this really isn't in a standard
> > > method for all Linux distros?  If not, why not work to do that like the
> > > freedesktop.org people have done for other system configuration items?
> >
> > We debated this issue on this mailing list for a long time. The consensus was
> that
> > we would invoke  external "distro" specific scripts for both configuring the
> interface
> > as well as gathering information that could not be gathered in a distro
> independent
> > fashion. That is what I have implemented here. This code specifies the interface
> to this
> > external script. If these external scripts are not there, it is not fatal - on the SET
> side,
> > the interface will not be configured and on the get side some attributes that are
> to be
> > gathered via these external scripts will not be collected.
> 
> I've applied the first 7 patches here, feel free to submit the rest when
> you answer the other questions I asked as well.

Greg,

I have tried to answer your questions in other emails I have sent out on this thread.
To summarize, the current implementation (with external scripts) does not preclude
using Network Manager where it makes sense (in the external scripts).

If you think it will be useful to have example scripts, I could send the scripts I
have used to test this code as example code. The reason I did not send the 
scripts is because (a) not having these scripts is not fatal to this code and 
(b) Given that this is a distro specific script, I did not want code checked 
into the kernel tree that was very distro specific.

Let me know if I have addressed your concerns and if I can re-send the
remaining 7 patches.  
 
Regards,

K. Y


--
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/