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: <alpine.LNX.1.10.0805021609400.6463@fbirervta.pbzchgretzou.qr>
Date:	Fri, 2 May 2008 16:10:35 +0200 (CEST)
From:	Jan Engelhardt <jengelh@...ozas.de>
To:	Chris Mason <chris.mason@...cle.com>
cc:	Jeff Mahoney <jeffm@...e.com>,
	Tim Gardner <tim.gardner@...onical.com>,
	jeffschroeder@...puter.org, linux-fsdevel@...r.kernel.org,
	kernel-team@...ts.ubuntu.com, linux-kernel@...r.kernel.org,
	linux-btrfs@...r.kernel.org, John Johansen <jjohansen@...e.de>
Subject: Re: Btrfs v0.14 Released


On Friday 2008-05-02 14:52, Chris Mason wrote:
>>
>> An alternative approach, and IMHO better suited, is to:
>>
>> 	make -C ${kdir} all I_HAZ_AN_APPARMOR=1
                       ^
                     M=$PWD

>This is better than the current situation (oops without any clues),

If it oopses, then you probably also get a compile-time warning on
that remove_suid line. And in that case, you can catch it with at least 
a compile-time typecheck so as to not make the user head straight into 
an oops, is not it?
--
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