From: Peter Stephenson <p.w.stephenson@ntlworld.com>
To: zsh-workers@zsh.org
Subject: Re: Security
Date: Wed, 23 Dec 2020 17:17:23 +0000 [thread overview]
Message-ID: <806b1f2900ba9eea0de965c9cdf68299cbc55247.camel@ntlworld.com> (raw)
In-Reply-To: <9ukE0EnlTIntEcJ7b7nLSoq5E3XfeB-HtfyHk1Vmzoh_NojpSpL_amjhCixUBdb164pmStO4by1oduUBR0zCJpK0xGzrh2uz42flRXt96-8=@protonmail.com>
On Wed, 2020-12-23 at 05:53 +0000, reportyigit46 wrote:
> Hello,
> I can’t get answer from Oliver. Which one can give me answer?
You might want to try zsh-infra@zsh.org which is the small number
of people who have direct responsibility for the zsh site, so
all of necessity trustworthy --- I don't think there's anything
more specific.
pws
> Thank you,
>
>
> Açık Paz, Ara 20, 2020 16:46, Jérémie Roquet <jroquet@arkanosis.net> yazdı:
> > Hi,
> >
> > Le dim. 20 déc. 2020 à 14:13, reportyigit46
> > <reportyigit46@protonmail.com> a écrit :
> > > I want to share security issue. Can you share e-mail of security team ?
> >
> > If it's a security issue in zsh, you can get in touch with Oliver,
> > Bart, and of course Peter. You might want to cc. Stephane as well, as
> > he's some experience on the matter (eg. Shellshock).
> >
> > I've put all of them in cc.
> >
> > Best regards,
> >
> > --
> > Jérémie
>
>
next prev parent reply other threads:[~2020-12-23 17:17 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 ` Peter Stephenson [this message]
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 ` 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=806b1f2900ba9eea0de965c9cdf68299cbc55247.camel@ntlworld.com \
--to=p.w.stephenson@ntlworld.com \
--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).