From owner-freebsd-security@freebsd.org Thu May 14 08:00:45 2020 Return-Path: Delivered-To: freebsd-security@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id E57062E89E4 for ; Thu, 14 May 2020 08:00:45 +0000 (UTC) (envelope-from mw@semihalf.com) Received: from mail-qk1-x730.google.com (mail-qk1-x730.google.com [IPv6:2607:f8b0:4864:20::730]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49N3rD3rlPz42DY for ; Thu, 14 May 2020 08:00:44 +0000 (UTC) (envelope-from mw@semihalf.com) Received: by mail-qk1-x730.google.com with SMTP id 190so2170610qki.1 for ; Thu, 14 May 2020 01:00:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=semihalf-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=cB3J7ZE78gDd30LUIuT3vAoeMa2g7RCBN6ZnOWUUHJM=; b=b1QkI4cUdScsrEfkQ1nuwPQE12n+1O/j8lDrRQ8RFcIwjm7v1k7UPd4A1AOGAdIIH4 oiUNlx8J72xdxGq+OqyVBAqr4vYQNcGo6FiJ0Xl9SPfETZG154bUQbr8CkuqnaBKeoJU 1OZ67RJLA9vxMX08hcYpkc5gAE2UjW7zSEULv14Z6NzsqCIGf6XFGSzsyEGJB40JqaDs gPwyQ4Z8GP3R49ETg9jri2YYrsf5XLZis3/aH9zqbMWEMK2ons1k3UUZ6mKyZuIcYwgo d27/ls+Tbw9UbAa5BoTKB/9lkQ5MX0xLv5rmPN6029RX7GbSiFeJWl8sQdx+5Xxbg17v hj1w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=cB3J7ZE78gDd30LUIuT3vAoeMa2g7RCBN6ZnOWUUHJM=; b=ISu2BSYZ8RV08cVTaL2wK3aadckYjC3s/BM7QK8M+qSx96ddRKbVsT27qazkSGAJb8 bStgeMPKggdxBLPB6IC4RDWC5iAdMa7oldMWGVOyYXfMBqgCgwoSBdIRmxDX4xmxua1g qkSUsWIWvUFWELB5o0yYoSj1fcVLXaKCfvSIGAw8/sx9/bKKRCGSw8Q3CnZVrL9kFAP/ I4Mk92rL9TwjROVpljE3tB1id9gM+YTACE4RH8nn7MCHgn6GBX69LmrcqQ+zxs8yhtcB EZGs0LUqEeBnmSKh0H54Qo52+g8NqqJcQIJPhdtWT1dJrmakiLyXRb7mepY5jyoG8yce KG+w== X-Gm-Message-State: AOAM5335r05sggW0f50F6eevHUSit7uNnqJx6xgeOSHf9oNkPW4EuzOX JSIpAWZeTUTAs+ZFXry6u8s6uuN/BPgEggkzW07Rdg== X-Google-Smtp-Source: ABdhPJwEMog2pfOZUJEyanJk1SdaT0R9oFHeSjVngtQZuLlccdxbg4RijuzoGfz/yl8j+n0ZH2yHdVqcDReE1Q8OWME= X-Received: by 2002:a37:9bcb:: with SMTP id d194mr3596847qke.16.1589443243239; Thu, 14 May 2020 01:00:43 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Marcin Wojtas Date: Thu, 14 May 2020 10:00:31 +0200 Message-ID: Subject: Re: ASLR/PIE status in FreeBSD HEAD To: Ed Maste Cc: freebsd-security@freebsd.org, Rafal Jaworowski Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 49N3rD3rlPz42DY X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=semihalf-com.20150623.gappssmtp.com header.s=20150623 header.b=b1QkI4cU; dmarc=none; spf=none (mx1.freebsd.org: domain of mw@semihalf.com has no SPF policy when checking 2607:f8b0:4864:20::730) smtp.mailfrom=mw@semihalf.com X-Spamd-Result: default: False [-4.29 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[semihalf-com.20150623.gappssmtp.com:s=20150623]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-security@freebsd.org]; DMARC_NA(0.00)[semihalf.com]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[semihalf-com.20150623.gappssmtp.com:+]; RCVD_IN_DNSWL_NONE(0.00)[0.3.7.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; IP_SCORE(-1.99)[ip: (-9.17), ipnet: 2607:f8b0::/32(-0.33), asn: 15169(-0.42), country: US(-0.05)]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Security issues \[members-only posting\]" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 May 2020 08:00:46 -0000 Hi, wt., 5 maj 2020 o 12:03 Marcin Wojtas napisa=C5=82(a): > > pon., 4 maj 2020 o 17:24 Ed Maste napisa=C5=82(a): > > > > On Mon, 20 Apr 2020 at 10:22, Marcin Wojtas wrote: > > > > > > Indeed I thought of kyua and measuring buildworld execution time for > > > stressing the DUT and having the first comparison numbers for the low > > > price. > > > > > > Do you think it is possible to get help here, i.e. is there a FreeBSD > > > devops team, maintaining the Jenkins CI whose spare cycles could be > > > used for this purpose? Or is this a field requiring external help fro= m > > > interested parties? > > > > There aren't a lot of spare cycles to go around, but putting > > automation in place so that tests like this can easily be performed is > > certainly something that's in the Jenkins team's domain. > > Of course the available bandwidth is a limitation, but IMO we should > start with defining the requirements so that eventually it could be > added to the backlog. > > > > > > Yes, making use of something actively maintained would be great. Do > > > you see a need for IO stressing/benchmarking for the discussed cases? > > > > In the fullness of time I think it's important, but my opinion is that > > it's really functional tests that we need, for enabling features in > > -CURRENT; we can work on benchmarking before and after changing a > > default. > > Understood. Since there seem to be no blockers / major objections at > this point, how do you suggest proceed with the topic? How about > having a live discussion with interested parties, so that we can > establish at least a rough plan allowing to achieve the enablement of > this (and possibly other) feature in a foreseeable perspective? > Any thoughts about having a live discussion on the ALSR/PIE enablement topi= c? Best regards, Marcin