** Also affects: liboobs (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- newusers uses crypt insted of md5, intrepid installer doesn't use sha512
+ newusers, liboobs uses crypt insted of md5, intrepid installer doesn't use
sha512
** Changed in: liboobs (Ubuntu)
** Changed in: user-setup (Ubuntu)
Sourcepackagename: ubiquity => user-setup
** Also affects: migration-assistant (Ubuntu)
Importance: Undecided
Status: New
** Changed in: migration-assistant (Ubuntu)
Importance: Undecided => Medium
Status: New => Triaged
--
newusers uses cr
./d-i/source/migration-assistant/ma-script-utils: $chroot $ROOT chpasswd
-m < Triaged
** Changed in: shadow (Ubuntu)
Status: Confirmed => Triaged
** Changed in: ubiquity (Ubuntu)
Importance: Undecided => Medium
** Summary changed:
- newusers uses crypt insted of md5
+ newusers
I'd like to set ENCRYPT_METHOD to SHA512 by default to match the changes
made in PAM for Intrepid. Additionally, this will require that ubiquity
not call "chpasswd" with the "-m" flag, which overrides the
/etc/login.defs setting. (This may need to change in d-i as well?)
** Also affects: ubiqui
The debian 4.1.0-1 version fixed this (MD5_CRYPT_ENAB can be set to
yes).
Note that the prefered solution would be to define ENCRYPT_METHOD to MD5.
(ENCRYPT_METHOD was introduced in 4.1.0 to allow new password encryption
methods).
--
newusers uses crypt insted of md5
https://bugs.launchpad.net/
Or, at least, it only works if PAM is compiled out and
MD5_CRYPT_ENAB=yes in /etc/login.defs. It doesn't look like it's
implemented in the PAM case.
--
newusers uses crypt insted of md5
https://bugs.launchpad.net/bugs/51551
You received this bug notification because you are a member of Ubuntu
Bug
Mm, yes. From the code, it looks like simply nobody ever implemented MD5
hashes in newusers.
** Changed in: shadow (Ubuntu)
Importance: Undecided => Medium
--
newusers uses crypt insted of md5
https://bugs.launchpad.net/bugs/51551
You received this bug notification because you are a member of
I guess I could mention that I got the comment about $1$ from the shadow
man page. the newusers man page describes the input file being just
like a passwd file entry with a few things left out, but all the columns
there. That's probably all that's needed to repro this from the
interface viewpoint
I used this input file:
[EMAIL PROTECTED]:/home/xeno/shop/ubtest# cat newusers
ubu3Ubuntu Test User 3:/home/ubu3:/bin/bash
---snip---
newusers newusers
and I got the following password line which clearly doesn't have a hash
beginning with $1$:
ubu3:8xhfvFsxMIXh2:13671:0:9:7:::
---snip---
I confirm that I just demonstrated this behavior exists on my Feisty
install on my laptop. I made a user ubu3, and it's password in shadow
does NOT being with $1$.
--
newusers uses crypt insted of md5
https://bugs.launchpad.net/bugs/51551
You received this bug notification because you are a memb
10 matches
Mail list logo
