| 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
| ||
|
Message-Id: <200808111853.13854.arnd@arndb.de> Date: Mon, 11 Aug 2008 18:53:13 +0200 From: Arnd Bergmann <arnd@...db.de> To: "Serge E. Hallyn" <serue@...ibm.com> Cc: Dave Hansen <dave@...ux.vnet.ibm.com>, containers@...ts.linux-foundation.org, Theodore Tso <tytso@....edu>, linux-kernel@...r.kernel.org Subject: Re: [RFC][PATCH 1/4] checkpoint-restart: general infrastructure On Monday 11 August 2008, Serge E. Hallyn wrote: > At the restart end, every resource which was checkpointed will have to > be re-created, and permissions checked against the privilege of the > task which did the restart. We may end up having to make use of the new > credentials for this. > > This could become unpleasant: if an unprivileged task asked a privileged > helper to create something for the unprivileged task to use (i.e. a > raw socket), then the user needs to be privileged to re-created the > resource. But it's necessary. Right. Of course, the hard part here will be to make it obvious to be safe. Having to check all sorts of permissions means there will be many opportunities for exploitable bugs. The best way I can think of for this would be to use existing syscalls (e.g. sched_setscheduler, setfsuid, ...) from user space whereever possible and do only the bare minimum for the restart part in the kernel. Arnd <>< -- 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/
Powered by blists - more mailing lists