From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/3170 Path: news.gmane.org!not-for-mail From: Rich Felker Newsgroups: gmane.linux.lib.musl.general Subject: Re: Best place to discuss other lightweight libraries? Date: Tue, 23 Apr 2013 22:37:39 -0400 Message-ID: <20130424023739.GC20323@brightrain.aerifal.cx> 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> <20130423215023.GA34795@intma.in> 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 1366771070 7185 80.91.229.3 (24 Apr 2013 02:37:50 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 24 Apr 2013 02:37:50 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-3174-gllmg-musl=m.gmane.org@lists.openwall.com Wed Apr 24 04:37:54 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 1UUpak-0007nX-5V for gllmg-musl@plane.gmane.org; Wed, 24 Apr 2013 04:37:54 +0200 Original-Received: (qmail 10155 invoked by uid 550); 24 Apr 2013 02:37:52 -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 10140 invoked from network); 24 Apr 2013 02:37:52 -0000 Content-Disposition: inline In-Reply-To: <20130423215023.GA34795@intma.in> User-Agent: Mutt/1.5.21 (2010-09-15) Xref: news.gmane.org gmane.linux.lib.musl.general:3170 Archived-At: On Tue, Apr 23, 2013 at 05:50:23PM -0400, Kurt H Maier wrote: > 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.. OK. > 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. Because you don't have a keyboard, you have a 3-4" touchscreen. And you want it to keep working as you move from place to place without any interaction. > 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. I'm not sure what the ideal behavior is, but I know all the existing ones have bad behavior. > 4. will never be solved satisfactorally, since that garbage is not > predictable. the database of tedious TOS crap will never stop > expanding. Agree, but it still needs to be solved, even if the solution requires frequent updates to be fully effective. With decent heuristics though I think it could be fully automated for most sites with just a few exceptions for really weird ones.. > > 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. Agreed. I think really most users should _always_ be running in an environment where only root sees the real network interfaces and applications just see a virtual network routed through the real one. Rich