From: Artem Mygaiev <joculator@gmail.com>
To: xen-devel@lists.xenproject.org
Subject: [COVERITY ACCESS] for Embedded/Automotive team
Date: Fri, 18 Nov 2016 15:36:22 +0200 [thread overview]
Message-ID: <CAJwc6KthkHwkPZYeDO+dAkCqv5r6PQTPdLskoNezUWgCkrbd1Q@mail.gmail.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hello
I would like to request access to Coverity Scan project. Hereby, I:
- agree to follow the security response process.
- undertake to report security issues discovered to the security team
(security@xenproject.org) within 3 days of discovery.
- agree to disclose the issue only to the security team and not to
any other third party
- waive their (security team) right to select the disclosure time
line. Discoveries will follow the default time lines given in the
policy.
We work with Xen on ARM since 2012. Our primary goal is to introduce
Xen for embedded and in particular in automotive SW domains. Our
current activities are: ARM-based SoCs support (Renesas, TI, etc.), PV
drivers development (audio, video, input, etc.), co-processors support
and trusted environment support through OP-TEE integration. All of our
work is public and published in OSS mailing lists. We would like to
contribute in stability of Xen overall and Xen on ARM in particular
since this is absolutely critical for most of embedded applications.
Best regards,
Artem Mygaiev
-----BEGIN PGP SIGNATURE-----
Version: Mailvelope v1.5.2
Comment: https://www.mailvelope.com
wsFcBAEBCAAQBQJYLwPFCRBNzzYYJgaZIAAAk9oP/0A3r08qWawNKfjQO/AQ
GE3MH13ZdzCI853XQlThVMZ6nBto1wmRXBzcySwjg6fb/J0E5e69ZB46c+LE
DeXeFRT5uHAUO0Jl8dDUD+N2pZrX4V98IbES3BZlEeVfS2oy3nFys1Q764vv
vK1Dhh26vW/ryk++ysyzc5ngo7yP2FqL5b6qhJ3LgmlFBE68yxpE9+LVijVP
E5VzSJWcQicJdJ0dtHga8vP3+TMCMEnlUXERZTdMPKeHjLhmX8azfK9TRAaU
KHXtlUuF5M0nfX1NynKJ4Z8aTMaHtF/fjyWfw9LeuhvEHu1oM/L5uOfnLA1O
SmXkGJqvLM6PZ2sgowyhFOXgMpewMdZovAZE6KqUPndsBwEX/rT49kFR29j+
Wo6thMDSg3IFWjHPdnizmHBZ5bJ5K7YTJJiW6RSoL1ngtCT69LXA0KaBuGjX
qSld1p2bOLKQVG/uhUT3/x0Hxd/lrJi+hPO7OwP47CqAHLGwqJaxWDUmPCIj
EImyxcsUJ0dHbqwHK1LZhnK+N0TF+DlrEGWwNRXQMwtALpL+97HRyIiPQwsD
lHwkcwAz0mtqmIPFhoe1xaYdBmr5ZXO2dhIPratASS1NqQFpVpMBG1XxzGSF
7aAZwtKqXaBxv6KWl65BmsUweL35zZW4BOR/aaEVlYi5/eOjy8L58uERPCJL
F83h
=6eKi
-----END PGP SIGNATURE-----
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next reply other threads:[~2016-11-18 13:36 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-18 13:36 Artem Mygaiev [this message]
2016-11-18 13:56 ` [COVERITY ACCESS] for Embedded/Automotive team Andrew Cooper
2016-11-18 15:28 ` Konrad Rzeszutek Wilk
2016-11-18 20:55 ` Julien Grall
2016-11-19 16:53 ` Lars Kurth
2016-11-22 11:51 ` Julien Grall
2016-11-22 11:55 ` Lars Kurth
2016-11-22 13:06 ` Artem Mygaiev
2016-11-22 13:42 ` Andrew Cooper
2016-11-22 13:54 ` Artem Mygaiev
2016-11-28 10:27 ` Lars Kurth
2016-11-28 11:01 ` Artem Mygaiev
2016-11-29 14:21 ` Artem Mygaiev
2016-11-29 14:27 ` Julien Grall
2016-11-29 15:04 ` Lars Kurth
2016-11-30 11:14 ` Artem Mygaiev
2016-11-29 15:09 ` Artem Mygaiev
2016-11-29 16:12 ` Julien Grall
2016-11-29 18:19 ` Stefano Stabellini
2016-11-30 11:15 ` Artem Mygaiev
2016-11-30 19:10 ` Stefano Stabellini
2016-11-30 19:21 ` Andrew Cooper
2016-12-01 13:44 ` Artem Mygaiev
2016-11-22 9:00 ` Artem Mygaiev
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=CAJwc6KthkHwkPZYeDO+dAkCqv5r6PQTPdLskoNezUWgCkrbd1Q@mail.gmail.com \
--to=joculator@gmail.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 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).