zsh-workers
 help / color / mirror / code / Atom feed
From: "Jérémie Roquet" <jroquet@arkanosis.net>
To: Phil Pennock <zsh-workers+phil.pennock@spodhuis.org>,
	 Daniel Shahaf <d.s@daniel.shahaf.name>
Cc: "Zsh Hackers' List" <zsh-workers@zsh.org>
Subject: Re: Security
Date: Sun, 27 Dec 2020 23:40:23 +0100	[thread overview]
Message-ID: <CAFOazAOFxerpsmFB6QKMa1krjDu9Ke3G+Z4vYrz=sHY9bpYHBQ@mail.gmail.com> (raw)
In-Reply-To: <X+kBRpTydSUosZNw@fullerene.field.pennock-tech.net>

Le dim. 27 déc. 2020 à 22:49, Phil Pennock
<zsh-workers+phil.pennock@spodhuis.org> a écrit :
>
> On 2020-12-25 at 16:06 +0000, Daniel Shahaf wrote:
> > a separate -security@ list might be a good idea, or at least an alias.)
>
> zsh-security@ now exists, we're kicking the tires.

Daniel, Phil, would it be possible to advertise for this new list on
the mailing lists page?

  http://zsh.sourceforge.net/Arc/mlist.html

… and maybe set up a security.txt as well?

  https://securitytxt.org/

That's not yet a widely recognized standard, but I believe someone
unfamiliar with a project yet familiar with security would start by
looking there if there's is a contact address.

Thanks!

-- 
Jérémie


  reply	other threads:[~2020-12-27 22:40 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           ` Security Phil Pennock
2020-12-27 22:40             ` Jérémie Roquet [this message]
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='CAFOazAOFxerpsmFB6QKMa1krjDu9Ke3G+Z4vYrz=sHY9bpYHBQ@mail.gmail.com' \
    --to=jroquet@arkanosis.net \
    --cc=d.s@daniel.shahaf.name \
    --cc=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).