From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: zsh-workers@zsh.org
Subject: [PATCH] FAQ, METAFAQ: Mention zsh-security@.
Date: Mon, 5 Apr 2021 22:32:41 +0000 [thread overview]
Message-ID: <20210405223240.20164-1-danielsh@tarpaulin.shahaf.local2> (raw)
---
Already added to Arc/mlist.html by Phil.
Cheers,
Daniel
Doc/Zsh/metafaq.yo | 8 +++++++-
Etc/FAQ.yo | 5 +++++
2 files changed, 12 insertions(+), 1 deletion(-)
diff --git a/Doc/Zsh/metafaq.yo b/Doc/Zsh/metafaq.yo
index e69a0976c..ca7f26adf 100644
--- a/Doc/Zsh/metafaq.yo
+++ b/Doc/Zsh/metafaq.yo
@@ -34,7 +34,7 @@ uref(http://zsh.sourceforge.net/).
texinode(Mailing Lists)(The Zsh FAQ)(Availability)(Introduction)
sect(Mailing Lists)
cindex(mailing lists)
-Zsh has 3 mailing lists:
+Zsh has several mailing lists:
startitem()
item(tt(<zsh-announce@zsh.org>))(
@@ -47,6 +47,12 @@ User discussions.
item(tt(<zsh-workers@zsh.org>))(
Hacking, development, bug reports and patches.
)
+item(tt(<zsh-security@zsh.org>))(
+Private mailing list (the general public cannot subscribe to it) for discussing
+bug reports with security implications, i.e., potential vulnerabilities.
+
+If you find a security problem in zsh itself, please mail this address.
+)
enditem()
To subscribe or unsubscribe, send mail
diff --git a/Etc/FAQ.yo b/Etc/FAQ.yo
index 3e90a6c4e..171b2f9d7 100644
--- a/Etc/FAQ.yo
+++ b/Etc/FAQ.yo
@@ -2542,6 +2542,11 @@ label(62)
)
(posting to the last one is currently restricted).
+ Finally, there is a private mailing list (the general public cannot subscribe
+ to it) for discussing bug reports with security implications, i.e., potential
+ vulnerabilities: mytt(zsh-security@zsh.org). If you find a security problem
+ in zsh itself, please mail this address.
+
Note that you should only join one of these lists: people on
zsh-workers receive all the lists, and people on zsh-users will
also receive the announcements list.
reply other threads:[~2021-04-05 22:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20210405223240.20164-1-danielsh@tarpaulin.shahaf.local2 \
--to=d.s@daniel.shahaf.name \
--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).