From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/3168 Path: news.gmane.org!not-for-mail From: Kurt H Maier Newsgroups: gmane.linux.lib.musl.general Subject: Re: Best place to discuss other lightweight libraries? Date: Tue, 23 Apr 2013 17:50:23 -0400 Message-ID: <20130423215023.GA34795@intma.in> 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=us-ascii X-Trace: ger.gmane.org 1366753837 9100 80.91.229.3 (23 Apr 2013 21:50:37 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 23 Apr 2013 21:50:37 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-3172-gllmg-musl=m.gmane.org@lists.openwall.com Tue Apr 23 23:50:41 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 1UUl6l-0004KQ-Ha for gllmg-musl@plane.gmane.org; Tue, 23 Apr 2013 23:50:39 +0200 Original-Received: (qmail 29838 invoked by uid 550); 23 Apr 2013 21:50:38 -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 29830 invoked from network); 23 Apr 2013 21:50:38 -0000 Content-Disposition: inline In-Reply-To: <20130423134724.GY20323@brightrain.aerifal.cx> Xref: news.gmane.org gmane.linux.lib.musl.general:3168 Archived-At: On Tue, Apr 23, 2013 at 09:47:24AM -0400, Rich Felker wrote: > > 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. > ... wpa_supplicant can do 1., unless you mean choosing between ethernet and wifi. but it supports priority weighting on access points.. 2. is pretty trivial since you can easily wpa_cli >> /etc/wpa.conf or similar. I've never been sure why typing 'dhclient eth0' is seen as more onerous than running a polling daemon to save you the trouble. Can you elucidate more on 3? if the signal is lost, wpa_supplicant rescans and connects to any configured network, or else sleeps and rescans later. 4. will never be solved satisfactorally, since that garbage is not predictable. the database of tedious TOS crap will never stop expanding. > 1. No way to manage network priority/preference order. wpa_supplicant has priority= to do this. > 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. What is less obscure than the wpa_supplicant config file? > 3. Annoying network-hopping. this can also be fixed with priority= > 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. There are lots of useful things that can be done with this concept of an encapsulated connection. I get burned by this on my work laptop, which likes to spam VPN connection attempts back to corporate. khm