From: Adithya Balakumar <Adithya.Balakumar@toshiba-tsip.com>
To: isar-users@googlegroups.com, amikan@ilbers.de
Cc: kazuhiro3.hayashi@toshiba.co.jp, dinesh.kumar@toshiba-tsip.com,
shivanand.kunijadar@toshiba-tsip.com,
sai.sathujoda@toshiba-tsip.com,
adithya.balakumar@toshiba-tsip.com
Subject: [PATCH v2 0/2] Fix reproducibility of /etc/shadow file when image built on different days
Date: Wed, 6 Mar 2024 11:44:21 +0530 [thread overview]
Message-ID: <20240306061423.1088541-1-Adithya.Balakumar@toshiba-tsip.com> (raw)
The third field in the /etc/shadow file (sp_lstchg) contains the date of
the last password change expressed as the number of days since Jan 1, 1970.
As this is a relative time, creating a user today will result in:
username:17238:0:99999:7:::
whilst creating the same user tomorrow will result in:
username:17239:0:99999:7:::
This impacts reproducibility of images when built on different days.
Since /etc/shadow honours SOURCE_DATE_EPOCH, this patchset makes the
SOURCE_DATE_EPOCH variable available when the /etc/shadow file is
created/modified.
Changes in v2:
- Replaced "! -z" with "-n" while checking for value of SOURCE_DATE_EPOCH
- Handle failure if bitbake var for SOURCE_DATE_EPOCH is empty
Adithya Balakumar (2):
isar-bootstrap.inc: Export SOURCE_DATE_EPOCH variable
image-account-extension.bbclass: Export SOURCE_DATE_EPOCH variable
meta/classes/image-account-extension.bbclass | 4 ++++
meta/recipes-core/isar-bootstrap/isar-bootstrap.inc | 4 ++++
2 files changed, 8 insertions(+)
--
2.39.2
next reply other threads:[~2024-03-06 6:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-06 6:14 Adithya Balakumar [this message]
2024-03-06 6:14 ` [PATCH v2 1/2] isar-bootstrap.inc: Export SOURCE_DATE_EPOCH variable Adithya Balakumar
2024-03-06 6:14 ` [PATCH v2 2/2] image-account-extension.bbclass: " Adithya Balakumar
2024-03-11 12:09 ` [PATCH v2 0/2] Fix reproducibility of /etc/shadow file when image built on different days Uladzimir Bely
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=20240306061423.1088541-1-Adithya.Balakumar@toshiba-tsip.com \
--to=adithya.balakumar@toshiba-tsip.com \
--cc=amikan@ilbers.de \
--cc=dinesh.kumar@toshiba-tsip.com \
--cc=isar-users@googlegroups.com \
--cc=kazuhiro3.hayashi@toshiba.co.jp \
--cc=sai.sathujoda@toshiba-tsip.com \
--cc=shivanand.kunijadar@toshiba-tsip.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox