linux-kernel - Re: [PATCH 0/2] iw: add GeoClue support

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] [day] [month] [year] [list]

Date:	Mon, 23 Aug 2010 23:29:06 +0100
From:	Bastien Nocera <hadess@...ess.net>
To:	"Luis R. Rodriguez" <lrodriguez@...eros.com>
Cc:	Luis Rodriguez <Luis.Rodriguez@...eros.com>,
	Johannes Berg <johannes@...solutions.net>,
	Kevin Hayes <kevin@...eros.com>,
	David Quan <David.Quan@...eros.com>,
	"linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"geoclue@...ts.freedesktop.org" <geoclue@...ts.freedesktop.org>
Subject: Re: [PATCH 0/2] iw: add GeoClue support

On Mon, 2010-08-23 at 15:22 -0700, Luis R. Rodriguez wrote:
> On Mon, Aug 23, 2010 at 03:15:07PM -0700, Bastien Nocera wrote:
> > On Mon, 2010-08-23 at 15:11 -0700, Luis R. Rodriguez wrote:
> > > On Mon, Aug 23, 2010 at 02:05:56PM -0700, Bastien Nocera wrote:
> > <snip>
> > > > No, I'm talking about what's exported by the providers. I don't really
> > > > care if they talk to other parts of the system using D-Bus though. I'm
> > > > talking about link 2) here.
> > > > 
> > > > [App] <-1-> [Geoclue master] <-2-> [Gypsy provider] <-3-> [Gypsy daemon]
> > > 
> > > Sorry I do not follow yet. Is the idea that you would prefer if
> > > client applications would never talk to providers directly and instead
> > > always used the master provider?
> > 
> > Exactly, and it's mentioned in the bugzilla
> 
> Thanks for the heads up, I haven't been grep'ing through the bugzilla.
> 
> > and was discussed on the mailing-list as well.
> 
> And am new there :)
> 
> This makes sense -- are there plans on removing all these exported
> library routines so that the only exposed thing is the master
> provider calls?
> 
> Based on your comments it seems changing the iw patch to just
> use the master provider would go more in line with current
> development focus.

Right. And file bugs if you have specific uses that don't work as
expected with the master provider.

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