From: Jan Kiszka <jan.kiszka@siemens.com>
To: Adithya Balakumar <Adithya.Balakumar@toshiba-tsip.com>,
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
Subject: Re: [PATCH 0/2] Fix reproducibility of /etc/shadow file when image built on different days
Date: Mon, 4 Mar 2024 15:30:11 +0100 [thread overview]
Message-ID: <49459d60-af0c-4c2c-bd65-d3cb2771c0c8@siemens.com> (raw)
In-Reply-To: <20240304103716.1100116-1-Adithya.Balakumar@toshiba-tsip.com>
On 04.03.24 11:37, Adithya Balakumar wrote:
> 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.
>
Yeah, this is what I learned the hard way these days as well while
trying to make the kas container images bit-identical reproducible.
Jan
--
Siemens AG, Technology
Linux Expert Center
next prev parent reply other threads:[~2024-03-04 14:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-04 10:37 Adithya Balakumar
2024-03-04 10:37 ` [PATCH 1/2] isar-bootstrap.inc: Export SOURCE_DATE_EPOCH variable Adithya Balakumar
2024-03-04 16:06 ` Gylstorff Quirin
2024-03-05 4:33 ` Adithya.Balakumar
2024-03-04 10:37 ` [PATCH 2/2] image-account-extension.bbclass: " Adithya Balakumar
2024-03-05 4:19 ` Uladzimir Bely
2024-03-05 4:38 ` Adithya.Balakumar
2024-03-04 14:30 ` Jan Kiszka [this message]
2024-03-04 14:34 ` [PATCH 0/2] Fix reproducibility of /etc/shadow file when image built on different days MOESSBAUER, Felix
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=49459d60-af0c-4c2c-bd65-d3cb2771c0c8@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=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