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
Hi Roger,
I compared `/etc/shadow` and `/etc/passwd` across my host and from inside
the testable chroot environments, no difference, I also checked
`/etc/pam.d/common-password` and it looks that bullseye uses `yescrypt` for
hashing while buster uses `sha512`.
It also says in
Hi,
I'm not personally familiar with the changes in the latest Debian release, but
please check that all the password, shadow password files etc. are all copied
into the chroot and are self-consistent with one another. Are the host files
using a hash type not supported by the chroot
Package: schroot
Version: 1.6.10-12
Severity: important
X-Debbugs-Cc: ser...@vlasov.me
Dear Maintainer,
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
4 matches
Mail list logo
