From: Phil Pennock <zsh-workers+phil.pennock@spodhuis.org>
To: zsh-workers@zsh.org
Subject: Re: Security
Date: Sun, 27 Dec 2020 16:48:54 -0500 [thread overview]
Message-ID: <X+kBRpTydSUosZNw@fullerene.field.pennock-tech.net> (raw)
In-Reply-To: <a5f44f89-bec5-487d-aee3-8c4eb4f521fa@www.fastmail.com>
On 2020-12-25 at 16:06 +0000, Daniel Shahaf wrote:
> Sorry for the delay. It sounds like you emailed _only_ Oliver, so he
> might simply be on holiday. In any case, to avoid a single point of
> failure, please email the details to zsh-infra@zsh.org. Thanks!
>
> Note to -workers@: Folks who have dealt with previous security issues
> (or are otherwise trusted) and aren't already on -infra@ are welcome to
> join. Just send a subscription request the usual way. (And yes,
> a separate -security@ list might be a good idea, or at least an alias.)
zsh-security@ now exists, we're kicking the tires. I set it to
closed-to-new-subscribers, so Daniel might clean up after me and open it
to let people ask in the usual way. (Sorry, I missed this thread before
and only saw it after closing out the stuff I had open for setup).
The -infra list is intended to be boring. Several of the people you
want looking at security stuff are not subscribed and probably don't
want the spam of discussions about mailing-list bounce rates,
certificate renewals, etc.
-Phil
next prev parent reply other threads:[~2020-12-27 21:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-20 13:13 Security reportyigit46
2020-12-20 13:46 ` Security Jérémie Roquet
2020-12-23 5:53 ` Security reportyigit46
2020-12-23 17:17 ` Security Peter Stephenson
2020-12-23 17:18 ` Security gi1242+zsh
2020-12-23 18:50 ` Security reportyigit46
2020-12-25 16:06 ` Security Daniel Shahaf
2020-12-27 21:48 ` Phil Pennock [this message]
2020-12-27 22:40 ` Security Jérémie Roquet
2020-12-27 23:37 ` Security Phil Pennock
2020-12-28 0:11 ` Security Jérémie Roquet
2020-12-28 10:46 ` Security Daniel Shahaf
2020-12-28 11:08 ` Security Jérémie Roquet
2020-12-28 10:50 ` Security Daniel Shahaf
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=X+kBRpTydSUosZNw@fullerene.field.pennock-tech.net \
--to=zsh-workers+phil.pennock@spodhuis.org \
--cc=zsh-workers@zsh.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.vuxu.org/mirror/zsh/
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).