unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: ng0 <ngillmann@runbox.com>
Cc: guix-devel@gnu.org
Subject: Re: Call for volunteer(s) for Guix "security" web page
Date: Tue, 27 Sep 2016 14:04:29 -0400	[thread overview]
Message-ID: <20160927180429.GI2569@jasmine> (raw)
In-Reply-To: <87lgykmeru.fsf@we.make.ritual.n0.is>

On Thu, Sep 22, 2016 at 10:04:37AM +0000, ng0 wrote:
> In my opinion this could be extended later by something similar to
> https://security.gentoo.org/ and its subpages.
> As we don't have much on that topic currently, we can't write about
> it. If this would be too much for the website, an inclusion in the
> manual of which security measurements a vanilla Guix offers would be
> good.
> One example: I stumbled upon our /dev/mem configuration only when I
> wanted to use flashrom for internal flashing. This is not documented
> anywhere.

It's a good idea, but of course somebody needs to actually do the work
:)

My primary goal for this page right now is to make it easy to for anyone
to learn how to contact us about security issues. I'm hoping this page
is the first result on DuckDuckGo and Google for "guix security".

  reply	other threads:[~2016-09-27 18:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-16 16:14 Call for volunteer(s) for Guix "security" web page Leo Famulari
2016-09-22 10:04 ` ng0
2016-09-27 18:04   ` Leo Famulari [this message]
2016-09-25 22:52 ` Leo Famulari
2016-09-27  8:58   ` Ludovic Courtès
2016-09-27 18:16     ` Leo Famulari
2016-09-28 21:08       ` Ludovic Courtès
2016-09-27 18:26     ` Leo Famulari
2016-09-28 21:07       ` Ludovic Courtès
2016-09-29 15:04       ` Leo Famulari
2016-09-30 12:08         ` Ludovic Courtès
2016-09-30 18:06           ` Leo Famulari

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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=20160927180429.GI2569@jasmine \
    --to=leo@famulari.name \
    --cc=guix-devel@gnu.org \
    --cc=ngillmann@runbox.com \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).