All of lore.kernel.org
 help / color / mirror / Atom feed
From: Doug Goldstein <cardoe@cardoe.com>
To: xen-devel <xen-devel@lists.xenproject.org>
Subject: [COVERITY ACCESS] for Doug Goldstein
Date: Fri, 29 Jan 2016 10:16:04 -0600	[thread overview]
Message-ID: <56AB9044.305@cardoe.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1357 bytes --]

Hi all,

I agree to the conditions in the Xen Project Security [1] and Coverity
[2] Contribution guidelines.

I have been a Gentoo Linux developer since 2001 and involved with
downstream packaging of virtualization products in Gentoo for at least 8
years with a specific focus on QEMU, libvirt, KVM and now days Xen. I've
been a libvirt contributor in the past (with commit access) but for the
last year and half I've found my time consumed in other parts of the
stack. Most recently I've been contributing to Xen. My day job for the
last 8 years has been focused on shipping Linux based devices into
hostile environments and improving the security so that we have some
confidence that they are secure and untampered with. So I have a
personal vested interest in ensuring security holes are plugged and not
left around or provided to organizations with an interest in exploiting
them. Because of this I would like access to the Coverity results to
help plug anything that comes up.

My GPG key is not in the strong web of trust since I have very few
signatures so I can understand if that's a hold up. I'll look forward to
exchanging some signatures at the next Xen Developer Summit either way.

[1] http://www.xenproject.org/security-policy.html
[2] http://xenproject.org/help/contribution-guidelines.html

-- 
Doug Goldstein


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 959 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

             reply	other threads:[~2016-01-29 16:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-29 16:16 Doug Goldstein [this message]
2016-01-29 16:28 ` [COVERITY ACCESS] for Doug Goldstein Konrad Rzeszutek Wilk
2016-01-29 17:14 ` Andrew Cooper
2016-02-01 10:15 ` Wei Liu
2016-02-09 15:18 ` Ian Campbell

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=56AB9044.305@cardoe.com \
    --to=cardoe@cardoe.com \
    --cc=xen-devel@lists.xenproject.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.
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.