linux-kernel - change in protections of /proc/$pid/mem

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

Message-ID: <CAGXu5jKOYOR0m+iza3SPM8qeirJjsFS3vvp300x-rvd4qnAc9w@mail.gmail.com>
Date:	Wed, 18 Jan 2012 12:56:52 -0800
From:	Kees Cook <keescook@...gle.com>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	linux-kernel@...r.kernel.org, Roland McGrath <roland@...k.frob.com>
Subject: change in protections of /proc/$pid/mem

Hi,

In e268337dfe26dfc7efd422a804dbb27977a3cccc, the logic for interacting
with /dev/$pid/mem was changed. It seems that the requirement that the
reader/writer must be actively attached to the inferior has been
dropped. Is this wise, to allow multiple read/writers of /dev/$pid/mem
even if they are not ptracing? The protection has been there for a
while, and I don't see the reason for removing it. I can't find a
discussion about this change -- where did that happen?

-Kees

-- 
Kees Cook
ChromeOS Security
--
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/