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 `/etc/pam.d/common-password`: > if a shadow password hash will be shared between Debian 11 and older releases replace "yescrypt" with "sha512" for compatibility. My buster chroot already has "sha512" set. I tried to set "yescrypt" there but sudo still complains about the wrong password. Regards, Sergey On Wed, Aug 18, 2021 at 4:58 PM Roger Leigh <rle...@codelibre.net> wrote: > 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 environment? > > Regards, > Roger > > On 18/08/2021, 14:54, "Sergey Vlasov" <ser...@vlasov.me> wrote: > > 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. > > > >
