From owner-freebsd-current@freebsd.org Thu Jul 28 00:19:01 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DBA49BA7A7D for ; Thu, 28 Jul 2016 00:19:01 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: from mail-it0-f46.google.com (mail-it0-f46.google.com [209.85.214.46]) (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 AF7E11E71; Thu, 28 Jul 2016 00:19:01 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: by mail-it0-f46.google.com with SMTP id f6so155746476ith.1; Wed, 27 Jul 2016 17:19:01 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:reply-to:in-reply-to:references :from:date:message-id:subject:to:cc; bh=geOKPkxl9e18h0o+FF9jvwFRwMT1gmMlgaiu7TYAFzs=; b=ZeWWw65/bsq+wFOH0RMoE0iCgeP1bueXgX5ZNrFSLqv5eI1PJZLLuZUk6LfOAmQs2b Ywrxfcc3mfKPQvlbOHFhnJyDejAAiEBhbdjWrjXlNJ8EwYNjWH8iV275i2fdNc+WlftF fGpMqwSEzvcVSg4YpYubxYGjGReUqJNLg/CTjeP7QEqKzRy5f8g9bZGCxdXQL68Z+Yt4 mBPXFo5znd0ypeLLQvgOlPWLnCHV7ECaUccDayvQ9wiqHDAhTC6tIUiXAddRDYRAQwtH TJVF/dR98Ro12nfiNQPkHxZumw94AhYUpllsOeUUoUq25ZjSVjgpH/Bm0ClWj+hUZFZO /+9Q== X-Gm-Message-State: ALyK8tJm6H2VqCxA3WtRkThZWM9O+CtNgKSCmuebNjLab7X8qYIZzYlLXbcRn6uKLEQ1hg== X-Received: by 10.36.9.137 with SMTP id 131mr103249909itm.89.1469664673638; Wed, 27 Jul 2016 17:11:13 -0700 (PDT) Received: from mail-it0-f43.google.com (mail-it0-f43.google.com. [209.85.214.43]) by smtp.gmail.com with ESMTPSA id o74sm3889614ioe.37.2016.07.27.17.11.13 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 27 Jul 2016 17:11:13 -0700 (PDT) Received: by mail-it0-f43.google.com with SMTP id j124so65501864ith.1; Wed, 27 Jul 2016 17:11:13 -0700 (PDT) X-Received: by 10.36.3.193 with SMTP id e184mr36939588ite.34.1469664673174; Wed, 27 Jul 2016 17:11:13 -0700 (PDT) MIME-Version: 1.0 Reply-To: cem@freebsd.org Received: by 10.36.233.67 with HTTP; Wed, 27 Jul 2016 17:11:12 -0700 (PDT) In-Reply-To: <20160728000530.GH13428@mutt-hardenedbsd> References: <20160727225527.GG13428@mutt-hardenedbsd> <20160728000530.GH13428@mutt-hardenedbsd> From: Conrad Meyer Date: Wed, 27 Jul 2016 17:11:12 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: SafeStack in base To: Shawn Webb Cc: freebsd-current , Ed Maste Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Jul 2016 00:19:02 -0000 On Wed, Jul 27, 2016 at 5:05 PM, Shawn Webb wrote: > On Wed, Jul 27, 2016 at 05:02:07PM -0700, Conrad Meyer wrote: >> The problem appears to be an upstream limitation of >> -fsanitize=safe-stack: "Most programs, static libraries, or individual >> files can be compiled with SafeStack as is. ??? Linking a DSO with >> SafeStack is not currently supported." [0] >> >> That probably needs to be addressed upstream before it can be enabled globally. > > Gotcha. If I'm reading correctly, then, SafeStack can only be enabled in > bsd.prog.mk (and _not_ bsd.lib.mk). Is that correct? That is my reading of the page. I'll admit my total experience with -fsanitize=safe-stack is limited to glancing at the web page 5 minutes ago, so don't consider my take authoritative. Best, Conrad