From owner-freebsd-arch@FreeBSD.ORG Thu May 28 01:19:18 2015 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4CE00493 for ; Thu, 28 May 2015 01:19:18 +0000 (UTC) (envelope-from shawn.webb@hardenedbsd.org) Received: from mail-qc0-f170.google.com (mail-qc0-f170.google.com [209.85.216.170]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 15EFAA3E for ; Thu, 28 May 2015 01:19:17 +0000 (UTC) (envelope-from shawn.webb@hardenedbsd.org) Received: by qcmi9 with SMTP id i9so11713051qcm.0 for ; Wed, 27 May 2015 18:19:17 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:date:message-id:organization :user-agent:in-reply-to:references:mime-version:content-type; bh=PSGqtn6aXZR37eR6YGapUSgsuLU9Q2Gy7IiYDwchrsA=; b=F6fznnP6yeTZvagCEVnc9kNRzhNiIcCiJ5Cj01UJB/zpK6ngwZz++56Ntn7y2JLZGR KEiQJLRgPc3aDo/D/HaJgoI6Fx1hesmeuE2geWAjuQcDXT8ZMOqkHQoVA+9Ax45xUzqX G8/4NItgKYLvnZUsbQth+80jLDOYdoAwEO+zM3tz/i9BVR7zJmAMH8mbocY2KVLZ8YTZ i+YllUhiHxMmi+XZY/mH9WTz+Qil3w36607jYCawWMwuOqhdC3zC2x+EV/9S1el4IU6g sfDKn6QJ4FiJf7Vmcbywvwf4UhX1GWfLc7GwBspL7XygrHT+nk2CacPeUE6Kfa5DhWeb R4BQ== X-Gm-Message-State: ALoCoQlOOtkov7exNakm95iyg08zWkgehPyDeyT8xR9di1uLcf1cl2Wrs38QZVOCESIto0QQbPqB X-Received: by 10.55.22.143 with SMTP id 15mr360119qkw.85.1432775957105; Wed, 27 May 2015 18:19:17 -0700 (PDT) Received: from shawnwebb-laptop.localnet (c-73-200-186-132.hsd1.md.comcast.net. [73.200.186.132]) by mx.google.com with ESMTPSA id i197sm369225qhc.36.2015.05.27.18.19.15 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 27 May 2015 18:19:16 -0700 (PDT) From: Shawn Webb To: Ed Maste Cc: Warner Losh , Pedro Giffuni , Alfred Perlstein , "freebsd-arch@freebsd.org" Subject: Re: ASLR work into -HEAD ? Date: Wed, 27 May 2015 21:19:15 -0400 Message-ID: <3637667.CG6MV3lcfQ@shawnwebb-laptop> Organization: HardenedBSD User-Agent: KMail/4.14.3 (FreeBSD/11.0-CURRENT; KDE/4.14.3; amd64; ; ) In-Reply-To: References: <555CADB6.202@FreeBSD.org> <2503264.OAH5YVL1Fd@shawnwebb-laptop> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2596045.YBsWsGe7M1"; micalg="pgp-sha256"; protocol="application/pgp-signature" X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 May 2015 01:19:18 -0000 --nextPart2596045.YBsWsGe7M1 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="us-ascii" On Wednesday, 27 May 2015 20:31:12 Ed Maste wrote: > On 27 May 2015 at 20:00, Shawn Webb wrot= e: > > At the FreeBSD Developer Summit at EuroBSDCon 2014, Ed Maste said o= n > > behalf of the FreeBSD Foundation that he (and by extension, the > > Foundation) would block the ASLR patch from being merged into HEAD = if we > > didn't provide a mechanism for disabling ASLR as a non-root user on= a > > per-binary basis. >=20 > I said no such thing. >=20 > I did have reservations about various aspects of the ASLR work and > also passed on concerns of others. I certainly did not say that I (or= > the Foundation) would block the work unless certain conditions were > met. The Foundation doesn't have authority to block a change, anyway.= >=20 > I did say that we'd need the ability to disable ASLR on a per-process= > basis, with my specific interest being use by the debugger. After talking with Ed in private, I realized that I must have misunders= tood=20 the situation. He was mainly curious about how to satisfy existing=20 functionality in gdb and lldb. He didn't mean to convey that he would b= lock=20 the merge of the patch. I must have misunderstood. I still dislike the=20= feature, but it'll remain in the patch upstream. I fear that I may be growing tired of non-technical discussions involvi= ng=20 politics. As I said to Adrian Chadd in IRC, over the last nearly two ye= ars,=20 I've kissed so many shoes to get this in, I've now grown weary and cyni= cal. Unless someone has actual technical input regarding the patch itself, I= 'm=20 going to refrain from commenting further. If you have technical input=20= regarding the patch, please comment on the diff at Phabricator. Thanks, =2D-=20 Shawn Webb HardenedBSD GPG Key ID: 0x6A84658F52456EEE GPG Key Fingerprint: 2ABA B6BD EF6A F486 BE89 3D9E 6A84 658F 5245 6EEE --nextPart2596045.YBsWsGe7M1 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part. Content-Transfer-Encoding: 7Bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAABCAAGBQJVZm0TAAoJEGqEZY9SRW7uyosP/ROW7gWZ6B4d1lQOU85qnXhr HcIoWoSGcSyS4WwJgm1arjaH4ph5esVgXTiTk3lyk0t0H1E/385QYWl2lYzTd+EP mWQAv7ck3cjDm1EUuJsewOpgzBCY4m3blIUJ7xvAbJX/U1ZbuXOovChFPyRpRuuz vMa/Ujj7aUI131R9ovMI9a+Use4wCwgtY2/Mpb5x2/tJFwF0wobUWCpBjKoiFVSu S9L3x4mNimuX+0rzamVCvjq1SpFhc03f58F07/6Y7Rx89+HsaEByI9ZoynmSYvaq IZRV1eoh3GYyZU7MRSV9+Kx93HIaVnszjf4vFyIl80GcbOeoy5vobQnsZw/UNMU5 nWtSvK6smsHUd6wvvING6jVueBLD5BCIXPd3jnRCiomXSKgu0xgee91YaPPNSS1E 0KSGiGYYS3HPXmmpkuRG8b5Tg5CTdkhnTaiCYaG0Qhy02Bvd7LF6rvARe1eBwvgJ QvFzRc+KNX8D2nfZXqMKeHYcWj13VAY0kfg9rVThOG49Eh6Se3cMvVaX3lObz4GY iKMASRpJoRz5P4QfHASTR7VuA5Jx8N97loywS62473ZOrxGAJR/Wj5SnrLBFcBOc dGIyNjc72p9CqE3Iz1l8aGqzeHkUm3OQxhE5Ye7RxfiJw4lW3HA4oSE0d9rOgU6W c+SyAY1wL+xxcfXpwBqg =rOyv -----END PGP SIGNATURE----- --nextPart2596045.YBsWsGe7M1--