From: Marius Bakke <mbakke@fastmail.com>
To: Alex Vong <alexvong1995@gmail.com>,
Christopher Lemmer Webber <cwebber@dustycloud.org>
Cc: guix-devel@gnu.org
Subject: Re: Plan for Guix security (was Re: Long term plan for GuixSD security: microkernels, ocap, RISC-V support)
Date: Wed, 26 Dec 2018 14:42:03 +0100 [thread overview]
Message-ID: <87muos8kwk.fsf@fastmail.com> (raw)
In-Reply-To: <877efxp8xs.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 894 bytes --]
Hello!
Alex Vong <alexvong1995@gmail.com> writes:
> Besides, I remember we have discuss about hardening before. Should I
> start a new hardening branch? (although I don't time to work on it right
> now). I think this is something we can do now.
>
> My idea is to create a new guix module (guix build hardening) which
> should contains various build flags. Then we should modifiy each build
> system to import from this new module and fix any build error caused by
> it. We can ask the build farm to evaluate this new branch, right?
>
>
> What do you think?
Thank you for taking the initiative! This sounds great to me. I
imagine the build systems could get an argument along the lines of
#:hardening-flags '(pie fortify stack-protector ...).
For gnu-build-system, I suppose we'd build up CFLAGS, LDFLAGS and
friends? We'll also have to modify all packages that override those
variables.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2018-12-26 13:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-23 12:27 Long term plan for GuixSD security: microkernels, ocap, RISC-V support Christopher Lemmer Webber
2018-08-23 12:58 ` Ricardo Wurmus
2018-08-23 13:43 ` Christopher Lemmer Webber
2018-08-24 12:52 ` Ludovic Courtès
2018-08-24 12:46 ` Ludovic Courtès
2018-08-30 12:31 ` Ludovic Courtès
2018-09-24 14:14 ` Ludovic Courtès
2018-09-24 15:24 ` Joshua Branson
2018-09-24 17:26 ` Jonathan Brielmaier
2018-12-09 23:00 ` Adonay Felipe Nogueira
2018-12-31 16:16 ` Christopher Lemmer Webber
2018-12-25 21:56 ` Plan for Guix security (was Re: Long term plan for GuixSD security: microkernels, ocap, RISC-V support) Alex Vong
2018-12-26 13:42 ` Marius Bakke [this message]
2019-01-05 17:47 ` Ludovic Courtès
2018-12-26 17:48 ` Joshua Branson
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=87muos8kwk.fsf@fastmail.com \
--to=mbakke@fastmail.com \
--cc=alexvong1995@gmail.com \
--cc=cwebber@dustycloud.org \
--cc=guix-devel@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.