Conrol: tags 992430 moreinfo Sergey Vlasov wrote...
> When doing schroot into a buster chroot environment, sudo
> commands fail due to password not matching the current user password.
> There is no such problem for bullseye chroot environment.
>
> To reproduce:
>
> 0. make sure your current user belongs to sudo group
>
> 1. create buster chroot environment:
>
> $ sudo debootstrap buster /schroot-bug/buster
>
> 2. create schroot configuration file:
>
> $ cat << EOF | sudo tee /etc/schroot/chroot.d/buster
> [buster]
> type=directory
> directory=/schroot-bug/buster
> users=$USER
> profile=desktop
> personality=linux
> preserve-environment=false
> EOF
Unless I misunderstood, also install sudo in the chroot.
> 3. enter chroot:
>
> $ schroot -c buster
>
> 4. test sudo with your current password:
>
> $ sudo true
(...)
The following changes made the check pass:
1. On the *host*, change "yescrypt" to "sha512" in
/etc/pam.d/common-password
2. Change the password of that user (feel free to re-use the old one,
but we need the right hash).
3. Reboot (possibly not needed if you do the right things).
Can you confirm? Then this is stuff for README.Debian but otherwise
little schroot can do.
Regards,
Christoph
signature.asc
Description: PGP signature
