selinux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Smalley <stephen.smalley.work@gmail.com>
To: William Roberts <bill.c.roberts@gmail.com>
Cc: Laurent Bigonville <bigon@debian.org>,
	SElinux list <selinux@vger.kernel.org>
Subject: Re: CFLAGS overridden by distribution build system
Date: Fri, 29 May 2020 14:18:35 -0400	[thread overview]
Message-ID: <CAEjxPJ5N8Htq0uEekR7M7mt17_h7rRSzHU=kRBU_F02JfxO4ew@mail.gmail.com> (raw)
In-Reply-To: <CAFftDdr3A=rKcbzWcMDmz-XrqBTGd7mNbLLxt2vzU71DsqZ_9w@mail.gmail.com>

On Fri, May 29, 2020 at 1:15 PM William Roberts
<bill.c.roberts@gmail.com> wrote:
>
> On Fri, May 29, 2020 at 11:40 AM Stephen Smalley
> <stephen.smalley.work@gmail.com> wrote:
> >
> > On Fri, May 29, 2020 at 12:05 PM William Roberts
> > <bill.c.roberts@gmail.com> wrote:
> > >
> > > On Fri, May 29, 2020 at 8:31 AM Stephen Smalley
> > > <stephen.smalley.work@gmail.com> wrote:
> > > >
> > > > On Sat, May 23, 2020 at 11:59 AM William Roberts
> > > > <bill.c.roberts@gmail.com> wrote:
> > > > >
> > > > > On Sat, May 23, 2020 at 5:57 AM Laurent Bigonville <bigon@debian.org> wrote:
> > > > > >
> > > > > > Hello,
> > > > > >
> > > > > > The current build system of the userspace is setting a lot of CFLAGS,
> > > > > > but most of these are overridden by the distributions when building.
> > > > > >
> > > > > > Today I received a bug report[0] from Christian Göttsche asking me to
> > > > > > set -fno-semantic-interposition again in libsepol. I see also the same
> > > > > > flag and also a lot of others set in libselinux and libsemanage build
> > > > > > system.
> > > > >
> > > > > Why would it be again? The old DSO design made that option impotent.
> > > > > Clang does it by default.
> > > > >
> > > > > >
> > > > > > For what I understand some of these are just needed for code quality
> > > > > > (-W) and could be controlled by distributions but others might actually
> > > > > > need to be always set (-f?).
> > > > >
> > > > > If you look at the Makefiles overall in all the projects, you'll see hardening
> > > > > flags, etc. Libsepol has a pretty minimal set compared to say libselinux, but
> > > > > they all get overridden by build time CFLAGS if you want.
> > > > >
> > > > > >
> > > > > > Shouldn't the flags that always need to be set (which ones?) be moved to
> > > > > > a "override CFLAGS" directive to avoid these to be unset by distributions?
> > > > >
> > > > > If you we're cleaver with CFLAGS before, you could acually circumvent
> > > > > the buildtime
> > > > > DSO stuff. While i'm not opposed to adding it to immutable flag, if
> > > > > you're setting
> > > > > CFLAGS, you're on your own. At least with the current design.
> > > > >
> > > > > I have no issues with adding it to override, but we would have to
> > > > > overhaul a bunch
> > > > > of them and make them consistent.
> > > >
> > > > I'm inclined to agree with Laurent here - we should always set this
> > > > flag in order to preserve the same behavior prior to the patches that
> > > > removed hidden_def/hidden_proto and switched to relying on this
> > > > instead.
> > >
> > > Theirs a lot of features that rely on particular cflags, consider hardening
> > > options. A lot of the warnings/error stuff is not just a code hygiene, but also
> > > spotting potential issues that could arise as security issues. If one starts
> > > tinkering with cflags, you can really change the code quite a bit. This is why
> > > some places only approve sanctioned builds of crypto libraries.
> >
> > I think the difference here is that we made a change in the source
> > code (hidden_def/hidden_proto removal) that requires use of
> > -fno-semantic-interposition to preserve existing behavior.
> >
> > > But one of the things to consider is that for clang builds, clang
> > > doesn't support
> > > this option, so we would need to move the compiler checking code into each
> > > projects root makefile and ensure any consuming subordinate leafs add a
> > > default, or move it to the global makefile and make sure each leaf that needs it
> > > has a default.
> >
> > I think clang does support it now? https://reviews.llvm.org/D72724
>
> Yeah but that bug is all 2020 stuff. It is in the clang-10 release. I
> verified that
> with a local build from here:
>   - https://apt.llvm.org/
> So anything sub clang-10 won't support it, do you want to tie us to that
> new of a clang?

No, I guess not.  So I guess our options are to leave it alone and
just make sure it is well documented or complicate the Makefiles.

  reply	other threads:[~2020-05-29 18:18 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-23 10:56 CFLAGS overridden by distribution build system Laurent Bigonville
2020-05-23 15:59 ` William Roberts
2020-05-29 13:31   ` Stephen Smalley
2020-05-29 16:04     ` William Roberts
2020-05-29 16:40       ` Stephen Smalley
2020-05-29 17:15         ` William Roberts
2020-05-29 18:18           ` Stephen Smalley [this message]
2020-05-29 20:59             ` William Roberts
2020-06-01  9:34               ` Petr Lautrbach
2020-06-02 18:55                 ` [PATCH] README: start a section for documenting CFLAGS bill.c.roberts
2020-06-04 19:03                   ` Stephen Smalley
2020-06-08 15:37                     ` [PATCH v2] " bill.c.roberts
2020-06-08 16:21                       ` Stephen Smalley
2020-06-08 22:34                         ` William Roberts
2020-06-08 22:38                         ` [PATCH v3] " bill.c.roberts
2020-06-09 11:57                           ` Stephen Smalley

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAEjxPJ5N8Htq0uEekR7M7mt17_h7rRSzHU=kRBU_F02JfxO4ew@mail.gmail.com' \
    --to=stephen.smalley.work@gmail.com \
    --cc=bigon@debian.org \
    --cc=bill.c.roberts@gmail.com \
    --cc=selinux@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).