From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 43344138247 for ; Thu, 9 Jan 2014 23:25:21 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 3901DE0B7E; Thu, 9 Jan 2014 23:25:16 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 33107E0A5F for ; Thu, 9 Jan 2014 23:25:15 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp.gentoo.org (Postfix) with ESMTP id 4692933F46E for ; Thu, 9 Jan 2014 23:25:14 +0000 (UTC) X-Virus-Scanned: by amavisd-new using ClamAV at gentoo.org X-Spam-Flag: NO X-Spam-Score: -1.088 X-Spam-Level: X-Spam-Status: No, score=-1.088 tagged_above=-999 required=5.5 tests=[AWL=-0.965, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.121, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no Received: from smtp.gentoo.org ([IPv6:::ffff:127.0.0.1]) by localhost (smtp.gentoo.org [IPv6:::ffff:127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gT2dC0BFepNm for ; Thu, 9 Jan 2014 23:25:08 +0000 (UTC) Received: from plane.gmane.org (plane.gmane.org [80.91.229.3]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTPS id EF54A33ECA5 for ; Thu, 9 Jan 2014 23:25:06 +0000 (UTC) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1W1OyF-0005PE-MJ for gentoo-dev@gentoo.org; Fri, 10 Jan 2014 00:25:03 +0100 Received: from 71-17-69-121.yktn.hsdb.sasknet.sk.ca ([71.17.69.121]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 10 Jan 2014 00:25:03 +0100 Received: from dirtyepic by 71-17-69-121.yktn.hsdb.sasknet.sk.ca with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 10 Jan 2014 00:25:03 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-dev@lists.gentoo.org From: Ryan Hill Subject: [gentoo-dev] Re: [PATCH] To enable ssp default in Gcc the toolchain.eclass need some changes. Date: Thu, 9 Jan 2014 17:30:46 -0600 Organization: Gentoo Message-ID: <20140109173046.65952ac8@caribou.gateway.pace.com> References: <7554031.Sacz2dxc8i@laptop1.gw.ume.nu> <1389304629.424.44.camel@belkin5> <52CF1D7C.4030700@gentoo.org> <20140109232116.398080f1@gentoo.org> <52CF22C6.6030907@gentoo.org> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/wYUBfUU1qq+vJmRPV5lkp2u"; protocol="application/pgp-signature" X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 71-17-69-121.yktn.hsdb.sasknet.sk.ca X-Newsreader: Claws Mail 3.9.3 (GTK+ 2.24.22; x86_64-pc-linux-gnu) X-Archives-Salt: ac52c229-6fc2-4070-94ef-41d1ad7deb1b X-Archives-Hash: 3e7b6a0586098072d983a2a18b5a88de --Sig_/wYUBfUU1qq+vJmRPV5lkp2u Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Thu, 09 Jan 2014 17:29:26 -0500 "Rick \"Zero_Chaos\" Farina" wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 >=20 > On 01/09/2014 05:21 PM, Micha=C5=82 G=C3=B3rny wrote: > > Dnia 2014-01-09, o godz. 17:06:52 > > "Anthony G. Basile" napisa=C5=82(a): > >=20 > >> On 01/09/2014 04:57 PM, Pacho Ramos wrote: > >>> What are the advantages of disabling SSP to deserve that "special" > >>> handling via USE flag or easily disabling it appending the flag? > >> > >> There are some cases where ssp could break things. I know of once cas= e=20 > >> right now, but its somewhat exotic. Also, sometimes we *want* to brea= k=20 > >> things for testing. I'm thinking here of instance where we want to te= st=20 > >> a pax hardened kernel to see if it catches abuses of memory which woul= d=20 > >> otherwise be caught by executables emitted from a hardened toolchain. = =20 > >> Take a look at the app-admin/paxtest suite. > >=20 > > Just to be clear, are we talking about potential system-wide breakage > > or single, specific packages being broken by SSP? In other words, are > > there cases when people will really want to disable SSP completely? > >=20 > > Unless I'm misunderstanding something, your examples sound like you > > just want -fno-stack-protector per-package. I don't really think you > > actually want to rebuild whole gcc just to do some testing on a single > > package... > >=20 > Or just as easily set -fno-stack-protector in CFLAGS in make.conf. >=20 > I never felt manipulating cflags with use flags was a great idea, but in > this case is does feel extra pointless. >=20 > Personally I don't feel this is needed, and the added benefit of > clearing up a bogus "noblah" use flag makes me smile. >=20 > Zorry, do we really need this flag? Yes, we do. I want a way to disable it at a toolchain level. --=20 Ryan Hill psn: dirtyepic_sk gcc-porting/toolchain/wxwidgets @ gentoo.org 47C3 6D62 4864 0E49 8E9E 7F92 ED38 BD49 957A 8463 --Sig_/wYUBfUU1qq+vJmRPV5lkp2u Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQEcBAEBCgAGBQJSzzEmAAoJEO04vUmVeoRjFBAH/R+wEd24zuXA9zFFl4H7gQXx Xoi/0t/hCKYgslMw+BHsLm8FIwoTuc7GmSbQwnoogBmL3ETkl6x7nRBQd0b0eGUH t3kSsG/N8Fgabqny71G/T67ur0efKp/c6bBIqIQCDg2vMwqowP3wh33n8roJytI8 ZvRvJnuIVNps9TiFiRnnHwGjfv8a5WUSMr3in8qBOikgQKKt6loj0USzfyhWJyLU /RMk2FVN1tSMG+fFNudpHMnRpHruitNb7x+qjIFYHmbUY/3EUN3KBoHixMtJP93m SsbjO3onZdlxynxRt9O+U08K5/gOekxwS/aY723KMIvqvsLQUOuXV6HabusuDp4= =Zi9M -----END PGP SIGNATURE----- --Sig_/wYUBfUU1qq+vJmRPV5lkp2u--