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:	Sat, 2 Jul 2011 20:50:35 +0400
From:	Solar Designer <solar@...nwall.com>
To:	Vasiliy Kulikov <segoon@...nwall.com>
Cc:	Ingo Molnar <mingo@...e.hu>,
	Andrew Morton <akpm@...ux-foundation.org>,
	kernel-hardening@...ts.openwall.com,
	Randy Dunlap <rdunlap@...otime.net>,
	"Eric W. Biederman" <ebiederm@...ssion.com>,
	"Serge E. Hallyn" <serge.hallyn@...onical.com>,
	Daniel Lezcano <daniel.lezcano@...e.fr>,
	Oleg Nesterov <oleg@...hat.com>, Tejun Heo <tj@...nel.org>,
	linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
	linux-security-module@...r.kernel.org
Subject: Re: [RFC] ipc: introduce shm_rmid_forced sysctl

On Fri, Jul 01, 2011 at 03:35:33PM +0400, Vasiliy Kulikov wrote:
> From -ow readme:
> 
> "Of course, this breaks the way things are defined, so some applications
> might stop working. In particular, expect most commercial databases to
> break. Apache and PostgreSQL are known to work, though. :-)"
> 
> http://www.openwall.com/linux/README.shtml
> 
> But as it was written in days of Linux 2.4.x, the situation could have
> changed.  A desktop system seems to work.

I wrote the above in 2.0.x days (circa 1998) and it was based on FUD
rather than on any real evidence of any breakage.  Apache and PostgreSQL
were a couple of known users of shared memory segments, and these did
not break.  I was not aware of any programs that presumably did break.
Of course, those probably do exist, but I don't recall anyone ever
reporting any to me (as maintainer of -ow patches), although the warning
quoted above might have played a role in such non-reporting.

Alexander
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ