From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/3165 Path: news.gmane.org!not-for-mail From: Luca Barbato Newsgroups: gmane.linux.lib.musl.general Subject: Re: Best place to discuss other lightweight libraries? Date: Tue, 23 Apr 2013 23:25:56 +0200 Message-ID: <5176FC64.30700@gentoo.org> References: <20130422233110.GU20323@brightrain.aerifal.cx> <1366678495.18069.154@driftwood> <20130423014639.GW20323@brightrain.aerifal.cx> <20130422220430.53d0b1a5.idunham@lavabit.com> <20130423134724.GY20323@brightrain.aerifal.cx> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1366752370 26258 80.91.229.3 (23 Apr 2013 21:26:10 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 23 Apr 2013 21:26:10 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-3169-gllmg-musl=m.gmane.org@lists.openwall.com Tue Apr 23 23:26:14 2013 Return-path: Envelope-to: gllmg-musl@plane.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by plane.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1UUkj6-00083J-Uq for gllmg-musl@plane.gmane.org; Tue, 23 Apr 2013 23:26:13 +0200 Original-Received: (qmail 17744 invoked by uid 550); 23 Apr 2013 21:26:12 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Original-Received: (qmail 17736 invoked from network); 23 Apr 2013 21:26:12 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130411 Thunderbird/17.0.5 In-Reply-To: <20130423134724.GY20323@brightrain.aerifal.cx> Xref: news.gmane.org gmane.linux.lib.musl.general:3165 Archived-At: On 04/23/2013 03:47 PM, Rich Felker wrote: > Well the accepted wisdom is "almost true": for practical use of mobile > wifi, you need not just wpa_supplicant but also some controlling > process that's capable of: > > 1. Choosing which network to connect to. > 2. Managing keys. > 3. Logic for what to do when signal is lost. > 4. Automating nonsense click-through agreements on public wifi. > ... > > The existing solutions all manage the above very poorly. Respectively, > they have: > > 1. No way to manage network priority/preference order. > 2. Annoying popups to ask for key rather than having it be part of the > configuration of the network, and storing the keys in obscure places. > 3. Annoying network-hopping. > 4. Minimal or no auto-click-through; even when it does work, you can > get burned if your web browser happens to attempt a load before it > succeeds. A correct one needs to encapsulate the connection somehow so > that no connection is exposed to the user at all until the > click-through succeeds. connman is the closest I found so far, it uses dbus and glib so isn't exactly a fit in this list. lu