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  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:	Tue, 28 Jun 2011 06:43:54 +0530
From:	Balbir Singh <>
To:	Vasiliy Kulikov <>
	Andrew Morton <>,
	Al Viro <>,
	David Rientjes <>,
	Stephen Wilson <>,
	KOSAKI Motohiro <>,, Eric Paris <>,
	Solar Designer <>
Subject: Re: [PATCH 1/2] proc: restrict access to /proc/PID/io

On Fri, Jun 24, 2011 at 5:38 PM, Vasiliy Kulikov <> wrote:
> /proc/PID/io may be used for gathering private information.  E.g. for
> openssh and vsftpd daemons wchars/rchars may be used to learn the
> precise password length.  Restrict it to processes being able to ptrace
> the target process.

Hmm.. How do I reproduce this, won't they be enough randomness around
rchar/wchar by the time the attacker reads it?

> ptrace_may_access() is needed to prevent keeping open file descriptor of
> "io" file, executing setuid binary and gathering io information of the
> setuid'ed process.

Balbir Singh
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists