From: Christopher Baines <mail@cbaines.net>
To: Bengt Richter <bokr@bokr.com>
Cc: guix-devel@gnu.org
Subject: Re: Security related tooling project
Date: Fri, 23 Apr 2021 21:34:00 +0100 [thread overview]
Message-ID: <87eef0hhaf.fsf@cbaines.net> (raw)
In-Reply-To: <20210418024930.GA11854@LionPure>
[-- Attachment #1: Type: text/plain, Size: 575 bytes --]
Bengt Richter <bokr@bokr.com> writes:
> Given that crims &co monitor developer discussions to discover
> unfixed vulnerabilities and clues re exploiting them,
> what are your ideas to avoid building a tool that can be abused?
>
> E.g., How will your tool avoid leaking info during an embargo window
> while trusted developers are secretly/privately fixing
> critical vulns?
That's a point to consider I think. Most of what I'm thinking about is
for published vulnerabilities in software packaged for Guix, but you
raise a valid point, so thanks for bringing it up.
Chris
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]
next prev parent reply other threads:[~2021-04-23 20:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-03 10:41 Security related tooling project Christopher Baines
2021-04-03 16:13 ` Security related tooling project OFF TOPIC PRAISE Joshua Branson
2021-04-04 8:17 ` Christopher Baines
2021-04-04 13:35 ` Joshua Branson
2021-04-03 21:44 ` Security related tooling project Léo Le Bouter
2021-04-04 8:24 ` Christopher Baines
2021-04-04 5:09 ` Chris Marusich
2021-04-04 8:27 ` Christopher Baines
2021-04-04 10:43 ` Xinglu Chen
2021-04-04 20:32 ` Chris Marusich
2021-04-17 15:20 ` Ludovic Courtès
2021-04-18 2:49 ` Bengt Richter
2021-04-23 20:34 ` Christopher Baines [this message]
2021-04-23 20:32 ` Christopher Baines
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=87eef0hhaf.fsf@cbaines.net \
--to=mail@cbaines.net \
--cc=bokr@bokr.com \
--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 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).