From: "Livius" <egyszeregy@freemail.hu>
To: openembedded-core@lists.openembedded.org
Subject: Re: Forced password change in first login
Date: Tue, 19 Jul 2022 12:38:49 -0700 [thread overview]
Message-ID: <21049.1658259529123357494@lists.openembedded.org> (raw)
In-Reply-To: <7de31512-a9f1-4682-15a5-06b53da83458@theobroma-systems.com>
[-- Attachment #1: Type: text/plain, Size: 597 bytes --]
I got this "feature" on Yocto project of Xilinx ( https://xilinx-wiki.atlassian.net/wiki/spaces/A/pages/18841883/Yocto ) rel-v2022.1 (honister). It seems to me my Linux kernel uses SHA-512 in default because after my first password change i could se the ident number of this encryption in /etc/shadow ( https://www.cyberciti.biz/faq/understanding-etcshadow-file/ ). For all of my pre-made users from Yocto recipes if they had SHA-256 password hash, in first login it was forced to change. I could solve it after that i realizedm my Linux build likes to generate SHA-512 password has in run-time.
[-- Attachment #2: Type: text/html, Size: 679 bytes --]
prev parent reply other threads:[~2022-07-19 19:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-24 11:17 Forced password change in first login Livius
2022-06-03 21:45 ` Livius
2022-07-18 20:28 ` [OE-core] " Quentin Schulz
2022-07-18 21:48 ` Livius
2022-07-19 12:57 ` [OE-core] " Quentin Schulz
2022-07-19 19:38 ` Livius [this message]
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=21049.1658259529123357494@lists.openembedded.org \
--to=egyszeregy@freemail.hu \
--cc=openembedded-core@lists.openembedded.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