linux-kernel - Re: New Security Features, Please Comment

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: <20081204000858.6c79003a@lxorguk.ukuu.org.uk>
Date:	Thu, 4 Dec 2008 00:08:58 +0000
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Miquel van Smoorenburg <miquels@...tron.nl>
Cc:	Geoffrey McRae <geoff@...idhost.com>,
	Nick Andrew <nick@...k-andrew.net>,
	linux-kernel@...r.kernel.org
Subject: Re: New Security Features, Please Comment

> Well, in this particular case, and with this API, perhaps not.

ptrace, patching your own binary, kill etc.

> It would be great if you could say 'limit setuid() to saved-uid + uids
> 1000-2000' or something like that.

For the fsuid

> If then the userlevel NFS server gets owned you can at least be sure
> none of the files in /bin have been modified ..

The userland nfsd uses fsuid.. thats important. Acting on behalf of
another user for file purposes does make sense. I can see a
"setfsuidlist()" call making sense too, but uid/euid/saved uid don't make
sense in this context.

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