All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lars Kurth <lars.kurth@xen.org>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Security Response Problem Update
Date: Wed, 08 Feb 2012 17:16:30 +0000	[thread overview]
Message-ID: <4F32ADEE.6020006@xen.org> (raw)
In-Reply-To: <1328719383.6133.68.camel@zakaz.uk.xensource.com>

No problem: will do it tomorrow

On 08/02/2012 16:43, Ian Campbell wrote:
> Hi Lars,
>
> Please can we amend the Security Process [0] to add to the end of the
> section "5. Advisory public release:" text like:
>
>          Published advisories will be added to the Security
>          Announcements[1] wiki page.
>
> (with the link in the appropriate syntax/place)
>
> The reason is that this document also serves as our checklist for things
> to do when making a security announcement and this will serve to remind
> us to update that page.
>
> Thanks.
>
> [0] http://www.xen.org/projects/security_vulnerability_process.html
> [1] http://wiki.xen.org/wiki/Security_Announcements
>

  reply	other threads:[~2012-02-08 17:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-08 16:43 Security Response Problem Update Ian Campbell
2012-02-08 17:16 ` Lars Kurth [this message]
2012-02-14 16:01 ` Lars Kurth

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=4F32ADEE.6020006@xen.org \
    --to=lars.kurth@xen.org \
    --cc=Ian.Campbell@citrix.com \
    --cc=xen-devel@lists.xensource.com \
    /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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.