linux-kernel - Re: Credentials test patch

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]

Date:	Mon, 17 Sep 2007 16:27:43 +0100
From:	David Howells <dhowells@...hat.com>
To:	viro@....linux.org.uk, hch@...radead.org, torvalds@...l.org
Cc:	dhowells@...hat.com, linux-kernel@...r.kernel.org
Subject: Re: Credentials test patch

David Howells <dhowells@...hat.com> wrote:

>  (1) Permit one process to change another process's cred struct.  This means
>      that a process wishing to read its own creds must use RCU read to do so,
>      and a lock must be held when replacing the cred struct.

Having thought about this some more, I've realised that this also doesn't work
if when one thread tries to alter another thread's creds that other thread's
cred struct is currently overridden.

>  (2) Explicitly update the cred struct on entry to syscalls that might want to
>      use it.

So, I think this has to be the best way to do things.  It's the cleanest,
certainly and probably has the lowest overhead overall.

This also means that I don't need that horrible __current_cred() function that
Linus so objects to (I do too).

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