From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: [COVERITY ACCESS] for Doug Goldstein Date: Fri, 29 Jan 2016 11:28:39 -0500 Message-ID: <20160129162839.GC22787@char.us.oracle.com> References: <56AB9044.305@cardoe.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aPBuj-0000G0-Vu for xen-devel@lists.xenproject.org; Fri, 29 Jan 2016 16:28:50 +0000 Content-Disposition: inline In-Reply-To: <56AB9044.305@cardoe.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Doug Goldstein Cc: xen-devel List-Id: xen-devel@lists.xenproject.org On Fri, Jan 29, 2016 at 10:16:04AM -0600, Doug Goldstein wrote: > 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. +1 to provide Coverity access to Doug. > > 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 > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel