From: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
To: Paul Eggleton <paul.eggleton@linux.microsoft.com>,
"docs@lists.yoctoproject.org" <docs@lists.yoctoproject.org>
Subject: RE: [docs] [PATCH 2/9] ref-manual: add a note about hard-coded passwords
Date: Fri, 22 Apr 2022 09:35:59 +0000 [thread overview]
Message-ID: <e92fa932b4594c58a007b4db5cc70551@axis.com> (raw)
In-Reply-To: <52c5571a8664a7547caed420ea83d77ab5d21d0f.1650591341.git.paul.eggleton@linux.microsoft.com>
> -----Original Message-----
> From: docs@lists.yoctoproject.org <docs@lists.yoctoproject.org> On Behalf
> Of Paul Eggleton
> Sent: den 22 april 2022 03:41
> To: docs@lists.yoctoproject.org
> Subject: [docs] [PATCH 2/9] ref-manual: add a note about hard-coded
> passwords
>
> From: Paul Eggleton <paul.eggleton@microsoft.com>
>
> It seems prudent to point out that hard-coding passwords in the manner
> detailed in the example is not a good idea in production. This type of
> mistake has unfortunately been made by many device vendors (outside of
> the Yocto Project context) leading to security vulnerabilities.
>
> Signed-off-by: Paul Eggleton <paul.eggleton@microsoft.com>
> ---
> documentation/ref-manual/classes.rst | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/documentation/ref-manual/classes.rst b/documentation/ref-manual/classes.rst
> index 6ba792d..13cc2bb 100644
> --- a/documentation/ref-manual/classes.rst
> +++ b/documentation/ref-manual/classes.rst
> @@ -576,6 +576,13 @@ Finally, here is an example that sets the root password::
> usermod -p '${PASSWD}' root; \
> "
>
> +.. note::
> +
> + From a security perspective, hardcoding a default password is not
> + generally a good idea. It is recommended that you do not do this if you are
I would suggest adding "or even legal in some jurisdictions" after "good idea".
> + building a production image.
> +
> +
> .. _ref-classes-features_check:
>
> ``features_check.bbclass``
> --
> 1.8.3.1
//Peter
next prev parent reply other threads:[~2022-04-22 16:52 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-22 1:40 [PATCH 0/9] Release documentation for 4.0 Paul Eggleton
2022-04-22 1:40 ` [PATCH 1/9] migration-3.4: add missing entry on EXTRA_USERS_PARAMS Paul Eggleton
2022-04-22 10:30 ` [docs] " Quentin Schulz
2022-04-22 10:41 ` Richard Purdie
2022-04-22 1:40 ` [PATCH 2/9] ref-manual: add a note about hard-coded passwords Paul Eggleton
2022-04-22 9:35 ` Peter Kjellerstedt [this message]
2022-04-22 1:40 ` [PATCH 3/9] ref-manual: mention wildcarding support in INCOMPATIBLE_LICENSE Paul Eggleton
2022-04-22 9:37 ` [docs] " Peter Kjellerstedt
2022-04-22 1:40 ` [PATCH 4/9] ref-manual: add mention of vendor filtering to CVE_PRODUCT Paul Eggleton
2022-04-22 1:40 ` [PATCH 5/9] ref-manual: add KERNEL_DEBUG_TIMESTAMPS Paul Eggleton
2022-04-22 1:40 ` [PATCH 6/9] ref-manual: add XZ_THREADS and ZSTD_THREADS Paul Eggleton
2022-04-22 10:40 ` [docs] " Quentin Schulz
2022-04-22 11:46 ` Richard Purdie
2022-04-22 12:47 ` Quentin Schulz
2022-04-22 12:50 ` Richard Purdie
2022-04-22 1:40 ` [PATCH 7/9] ref-manual: add empty-dirs QA check and QA_EMPTY_DIRS* Paul Eggleton
2022-04-22 9:50 ` [docs] " Peter Kjellerstedt
2022-04-22 10:51 ` Quentin Schulz
2022-04-22 1:40 ` [PATCH 8/9] migration-guides: complete migration guide for 4.0 Paul Eggleton
2022-04-22 11:10 ` [docs] " Quentin Schulz
2022-04-22 12:09 ` Richard Purdie
2022-04-22 1:40 ` [PATCH 9/9] migration-guides: add release notes " Paul Eggleton
2022-04-22 11:17 ` [docs] " Quentin Schulz
2022-04-22 11:18 ` [docs] [PATCH 0/9] Release documentation " Quentin Schulz
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=e92fa932b4594c58a007b4db5cc70551@axis.com \
--to=peter.kjellerstedt@axis.com \
--cc=docs@lists.yoctoproject.org \
--cc=paul.eggleton@linux.microsoft.com \
/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.