From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: xen-devel@lists.xensource.com
Subject: Publishing livepatch instructions for XSAs from livepatch wiki
Date: Tue, 2 Aug 2016 10:06:46 -0400 [thread overview]
Message-ID: <20160802140646.GA5112@char.us.oracle.com> (raw)
Hey,
My goal for Xen 4.8 is to get OSSTest to regularly test livepatch mechanism.
I am struggling with OSSTest but I am sure I will figure it out.
But in the meantime I was wondering what the community feels about publishing
step-by-step instructions on how to use livepatching for XSAs. When XSA-182
came out I prepared an document (see attached). Now that XSA 182 is public
it can be put on the Wiki page.
What I was wondering if folks would be OK with:
1). Linking it from http://wiki.xen.org/wiki/LivePatch?
2). Adding 'Security' and 'Livepatch' category to it?
(That means if one searches for 'security' you can find the livepatch
and say Xen Security policies and such).
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
reply other threads:[~2016-08-02 14:06 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=20160802140646.GA5112@char.us.oracle.com \
--to=konrad.wilk@oracle.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.