From: "Jérémie Roquet" <jroquet@arkanosis.net>
To: Daniel Shahaf <d.s@daniel.shahaf.name>
Cc: "Zsh Hackers' List" <zsh-workers@zsh.org>
Subject: Re: Security
Date: Mon, 28 Dec 2020 12:08:55 +0100 [thread overview]
Message-ID: <CAFOazAMbEsSvBRV5U6nfaVWuLAr5XXQ436coP8g20mPvU4eiBA@mail.gmail.com> (raw)
In-Reply-To: <20201228104612.GC10030@tarpaulin.shahaf.local2>
Le lun. 28 déc. 2020 à 11:46, Daniel Shahaf <d.s@daniel.shahaf.name> a écrit :
>
> Jérémie Roquet wrote on Mon, Dec 28, 2020 at 01:11:10 +0100:
> > That's fair. So, for anyone wondering what this security.txt thing is
> > […]
> > The specification is intended to become a standard
>
> Are you sure about this? The Internet Draft's "Intended status" is
> "Informational", as opposed to "Standards track".
Well, I'm not sure, then. The website says “proposed standard”… I
guess it depends on who you ask.
> > but isn't yet; its ability to become one is also driven by its adoption, of
> > course (the usual chicken-and-egg problem).
That's the only thing I'm sure of: it seems rather well received, but
it has yet to see a wider adoption before one can say it's a standard,
hence my note.
Best regards,
--
Jérémie
next prev parent reply other threads:[~2020-12-28 11:09 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 ` 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 ` Jérémie Roquet [this message]
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=CAFOazAMbEsSvBRV5U6nfaVWuLAr5XXQ436coP8g20mPvU4eiBA@mail.gmail.com \
--to=jroquet@arkanosis.net \
--cc=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).