From: Philip Balister <philip@balister.org>
To: "Reshetova, Elena" <elena.reshetova@intel.com>,
"yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Package naming "exceptions" in Yocto
Date: Thu, 14 Jan 2016 08:02:42 -0500 [thread overview]
Message-ID: <56979C72.8080309@balister.org> (raw)
In-Reply-To: <2236FBA76BA1254E88B949DDB74E612B41A4F981@IRSMSX102.ger.corp.intel.com>
Please note there is a security page on the wiki:
https://wiki.yoctoproject.org/wiki/Security
and there is a security list at:
yocto-security@yoctoproject.org
The list isn't very active, but it should be copied on all security
discussions. If you are interested you should be subscribed to this list.
If I hadn't read the email, I wouldn't have realized this was about
security issues.
Philip
On 01/14/2016 02:43 AM, Reshetova, Elena wrote:
> Hi,
>
>
>
> I have a small question about "exceptional" names of packages in yocto/OE.
> Kernel package is being one example with the name "linux-yocto" vs.
> traditional "linux_kernel".
>
> Are there more such yocto-specific packages (of course excluding FW and
> other bsp-related packages)? A look over the package list didn't reveal any,
> but I wanted to double check.
>
>
>
> The reason I am asking is that in case when we try to determine the package
> CVEs against the NVD database, in these particular exception cases, we
> probably want to check not only "linux-yocto", but also "linux_kernel" open
> package CVEs with regards to specified version to make sure we cover as much
> as we can.
>
>
>
> Best Regards,
> Elena.
>
>
>
>
>
>
next prev parent reply other threads:[~2016-01-14 13:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-14 7:43 Package naming "exceptions" in Yocto Reshetova, Elena
2016-01-14 13:02 ` Philip Balister [this message]
2016-01-14 14:33 ` Reshetova, Elena
2016-01-14 15:28 ` akuster
2016-01-14 17:58 ` Khem Raj
2016-01-14 22:10 ` Paul Eggleton
2016-01-18 11:14 ` Reshetova, Elena
2016-01-18 11:26 ` Paul Eggleton
2016-01-18 13:57 ` Reshetova, Elena
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=56979C72.8080309@balister.org \
--to=philip@balister.org \
--cc=elena.reshetova@intel.com \
--cc=yocto@yoctoproject.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.