I also have problems with setting passwords in current master branch. I
only can provide a hacky workaround. I added the following lines to my
image recipe to inject the passwords manually after rootfs creation:
RETRO_USER_PASSWORD ?= "retro"
ROOT_USER_PASSWORD ?= "root"
ROOTFS_POSTPROCESS_COMMAND += "set_root_passwd;"
ROOTFS_POSTPROCESS_COMMAND += "set_retro_passwd;"
set_root_passwd() {
ROOTPW_ENCRYPTED="$(openssl passwd -6 -salt xyz ${ROOT_USER_PASSWORD})"
sed -i "s%^root:[^:]*:%root:${ROOTPW_ENCRYPTED}:%"
${IMAGE_ROOTFS}/etc/shadow
}
set_retro_passwd() {
RETROPW_ENCRYPTED="$(openssl passwd -6 -salt xyz
${RETRO_USER_PASSWORD})"
sed -i "s%^retro:[^:]*:%retro:${RETROPW_ENCRYPTED}:%"
${IMAGE_ROOTFS}/etc/shadow
}
Am 30.08.21 um 14:54 schrieb Matthias Klein:
Hello,
I am trying to find a working alternative for the old -P option.
Previous:
EXTRA_USERS_PARAMS = "usermod -P toor root;"
The suggestions from this thread don't seem to work:
https://lists.openembedded.org/g/openembedded-core/topic/84548199
Current:
hash="$(python3 -c "import crypt; print(crypt.crypt('toor',
crypt.METHOD_SHA512))")"
EXTRA_USERS_PARAMS = "usermod -p ${hash} root;"
The hashed password does not seem to be escaped properly in the
extrausers-bbclass. The password in the shadow file is missing $ characters.
Is there a way (with the current master branch) to define a password?
Many greetings,
Matthias
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#54605): https://lists.yoctoproject.org/g/yocto/message/54605
Mute This Topic: https://lists.yoctoproject.org/mt/85249985/21656
Group Owner: [email protected]
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
