linux-kernel - Re: syscall: introduce sendfd() syscall (v.2)

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

Message-ID: <20141205132250.6f2f9ec1@lxorguk.ukuu.org.uk>
Date:	Fri, 5 Dec 2014 13:22:50 +0000
From:	One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>
To:	Alex Dubov <alex.dubov@...il.com>
Cc:	linux-kernel@...r.kernel.org, viro@...iv.linux.org.uk,
	corbet@....net, richardcochran@...il.com
Subject: Re: syscall: introduce sendfd() syscall (v.2)


> 2.a. If task A has sufficient capabilities to send signals to task B, then
> task A is already in position to do anything it wants with task B, including
> killing it outright.

Not entirely true.

- We have securirty models like SELinux
- We have namespaces and being able to send an fd between namespaces is
  not quite as flexible as you would make it

I suspect therefore it needs security hooks but otherwise looks more sane
than the current AF_UNIX approach.

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