All of lore.kernel.org
 help / color / mirror / Atom feed
From: "rpjday@crashcourse.ca" <rpjday@crashcourse.ca>
To: akuster808 <akuster808@gmail.com>
Cc: docs@lists.yoctoproject.org
Subject: Re: [docs] what about more current security links for section 3.18 in dev manual?
Date: Fri, 21 Feb 2020 17:29:21 -0500 (EST)	[thread overview]
Message-ID: <alpine.LFD.2.21.2002211728080.12082@localhost.localdomain> (raw)
In-Reply-To: <ffb95f6b-72ea-cf64-24e9-b0a62942f006@gmail.com>

On Fri, 21 Feb 2020, akuster808 wrote:

> Robert,
>
>
>
> On 2/17/20 1:11 AM, rpjday@crashcourse.ca wrote:
>
>   currently perusing dev manual, 3.18, "Making Images More Secure",
> https://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#making-images-more-sec
> ure
> and the newest link there is from 2014 (even older ones are from 2012
> and 2009.
>
>   if people want to recommend newer online resources, i'll update the
> links in that section.
>
> I found this doc on-line an plan on adding a link in the meta-security layer.
>
> https://www.nccgroup.trust/us/our-research/improving-your-embedded-linux-security-posture-
> with-yocto/
>
> maybe its applicable for the YP docs?

  i was unaware of that paper, it looks pretty good, i can add that as
a link. still intersted in a couple more so i can submit them as a set
in one patch. anyone else? maybe online resources that don't
necessarily mention YP, but are embedded specific?

rday

  reply	other threads:[~2020-02-21 22:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-17  9:11 what about more current security links for section 3.18 in dev manual? rpjday
2020-02-21 19:07 ` [docs] " akuster
2020-02-21 22:29   ` rpjday [this message]
2020-02-21 22:49   ` rpjday

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=alpine.LFD.2.21.2002211728080.12082@localhost.localdomain \
    --to=rpjday@crashcourse.ca \
    --cc=akuster808@gmail.com \
    --cc=docs@lists.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.