linux-kernel - Re: A desktop environment[1] kernel wishlist

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20141027162220.GV7996@ZenIV.linux.org.uk>
Date:	Mon, 27 Oct 2014 16:22:20 +0000
From:	Al Viro <viro@...IV.linux.org.uk>
To:	Bastien Nocera <hadess@...ess.net>
Cc:	Andy Lutomirski <luto@...capital.net>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: A desktop environment[1] kernel wishlist

On Mon, Oct 27, 2014 at 05:09:06PM +0100, Bastien Nocera wrote:

> > > By having a well-known protocol and defined semantics on top of that
> > > communication channel. I could try and re-explain why kdbus is needed,
> > > but I wouldn't do as good a job as the people working on it, so best to
> > > refer to the individual threads about kdbus on this list.
> > >
> > 
> > I didn't do a good job asking the question, then.
> > 
> > What's wrong with fds in the context of communicating with a
> > container?  What does kdbus do container-wise that helps?
> 
> Nothing's wrong with using fd's. They're just a very poor API.

For a proof by assertion it's too transparent, for any other kind of
explanation - far too short on details...
--
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/