[VU+ Solo2] root password cannot be changed

[birdman]

I don't want to install strace if I am performing a typo or doing something incorrectly

Which is a pity, as it should show what that passwd command is doing.

what is the exact command to change the password

It's passwd, which should prompt you for a new password.

You could try:

type passwd
ls -l /usr/bin/passwd*

just to check it all looks OK. You should see:

root@mbtwin:~# type passwd
passwd is /usr/bin/passwd
root@mbtwin:~# ls -l /usr/bin/passwd*
lrwxrwxrwx    1 root     root            22 Nov 22 19:02 /usr/bin/passwd -> /usr/bin/passwd.shadow
-rwsr-xr-x    1 root     root         40960 Nov 21 08:52 /usr/bin/passwd.shadow

 

[sivhead]

Now samba is working the command passwd works also. that's good to know that the samba fix resolves this issue. (or could be a skin change as I have changed to RED-HD from Magic-FHD so it was either a skin or a samba fix.. damnn why did I have to make 2 changes at once... Well if someone else gets the issue at least we can see what skin they have and if they have a samba issue.

 

[judge]

A skin has nothing to do with a password.

 

[sivhead]

I thought that but I thought I better mention it as I did 2 changes. I would have also thought that samba would have nothing to do with telnet either with the passwd command not working

 

[ArowonA]

Ignore this re-read somethings

 

[birdman]

A skin has nothing to do with a password.

Neither does samba.

 

[janski74]

I also have the same problem. The biggest problem is that when logging in to the system with putty it does not ask for root password at all! It just logs you in immediately after given root username. Also, I cannot change/set the root password (I have had it set before and it has worked just fine).
When I try to change the password, nothing happens (please see the output below). Shadow-file shows that there is no password set at all. I think this problem appeared with the latest 037-build.
--
Welcome to OpenViX for gbquadplus
openvix 3.2 gbquadplus

gbquadplus login: root
Last login: Fri Mar 4 18:43:59 EET 2016 from 192.168.10.55 on pts/0
root@gbquadplus:~# passwd
root@gbquadplus:~#
root@gbquadplus:~# passwd -S
root NP 05/18/2015 0 99999 7 -1
root@gbquadplus:~#
root@gbquadplus:~# grep root /etc/shadow
root::16573:0:99999:7:::
root@gbquadplus:~#

 

[janski74]

Update, passwd -command does not change other users either...

I also have the same problem. The biggest problem is that when logging in to the system with putty it does not ask for root password at all! It just logs you in immediately after given root username. Also, I cannot change/set the root password (I have had it set before and it has worked just fine).
When I try to change the password, nothing happens (please see the output below). Shadow-file shows that there is no password set at all. I think this problem appeared with the latest 037-build.
--
Welcome to OpenViX for gbquadplus
openvix 3.2 gbquadplus

gbquadplus login: root
Last login: Fri Mar 4 18:43:59 EET 2016 from 192.168.10.55 on pts/0
root@gbquadplus:~# passwd
root@gbquadplus:~#
root@gbquadplus:~# passwd -S
root NP 05/18/2015 0 99999 7 -1
root@gbquadplus:~#
root@gbquadplus:~# grep root /etc/shadow
root::16573:0:99999:7:::
root@gbquadplus:~#

 

[birdman]

Last login: Fri Mar 4 18:43:59 EET 2016 from 192.168.10.55 on pts/0
root@gbquadplus:~# passwd
root@gbquadplus:~#

That was reported several months ago, and I requested that the use run the command thrpugh strace so we could see what was happening, as when I type that it all works as expected.
But there was no response.

If you want to help, install strace, then run:

strace -f -o passwd.log passwd

and post the log (the passwd.log file) here/. Since you haven't typed anything it won't contain any password information.

 

[janski74]

Sorry, I could not get strace installed.

The problem still persist. But I was able to set a root password with usermod.
Here is the info how, in case there are people who has the same problem:

This will encrypt your password:
openssl passwd

And then you will use the encrypted password here:
usermod -p encrypted password root

After this I was asked root password and I was able to log in with it. I noticed that the encrypted password were shown now in both passwd and shadow -files. I did remove the password from passwd -file so that it now looks like this:
root:x:0:0:root:/home/root:/bin/sh

I still cannot change any passwords with passwd -command.

That was reported several months ago, and I requested that the use run the command thrpugh strace so we could see what was happening, as when I type that it all works as expected.
But there was no response.

If you want to help, install strace, then run:

strace -f -o passwd.log passwd

and post the log (the passwd.log file) here/. Since you haven't typed anything it won't contain any password information.

 

[birdman]

Sorry, I could not get strace installed.

Why not? It should install from the standard feeds.

 

[janski74]

I cannot find it from the feeds...

Why not? It should install from the standard feeds.

 

[birdman]

I cannot find it from the feeds...

opkg install strace

 

[janski74]

Ok, thanks! Didn't know it was that easy
Log-file is attached here:
View attachment passwd.log

opkg install strace

 

[birdman]

Your passwd is wandering off into Samba territory.
Looks like something in the file /etc/pam.d/common-password is causing that. Any chance you could post that here (it's just a configuration file).
The command is sending a message to the system log, so if you run:

grep passwd /var/log/messages

after trying the passwd command (no need for strace) then you would get that text, which may help.

I presume you have configured Samba on the box in some way. Do you remember what you did?

 

[janski74]

Hi again and thanks for the help birdman. Actually no, I haven't done a thing with Samba and as far as I know, I don't even have it installed?!?
I have also re-flashed the box two times (to build 036 and 037) but it didn't help...

Anyway here is the output you asked:

root@gbquadplus:~# grep passwd /var/log/messages
Mar 5 13:31:09 gbquadplus authpriv.err passwd[2140]: pam_unix(passwd:chauthtok): unrecognized option [obscure]
Mar 6 23:55:14 gbquadplus authpriv.err passwd[23929]: pam_unix(passwd:chauthtok): unrecognized option [obscure]
Mar 6 23:55:18 gbquadplus authpriv.err passwd[23956]: pam_unix(passwd:chauthtok): unrecognized option [obscure]
Mar 7 09:13:57 gbquadplus authpriv.err passwd[23352]: pam_unix(passwd:chauthtok): unrecognized option [obscure]

Your passwd is wandering off into Samba territory.
Looks like something in the file /etc/pam.d/common-password is causing that. Any chance you could post that here (it's just a configuration file).
The command is sending a message to the system log, so if you run:

grep passwd /var/log/messages

after trying the passwd command (no need for strace) then you would get that text, which may help.

I presume you have configured Samba on the box in some way. Do you remember what you did?

 

[janski74]

Sorry, forgot to send common-password -file. Here it is:

#
# /etc/pam.d/common-password - password-related modules common to all services
#
# This file is included from other service-specific PAM config files,
# and should contain a list of modules that define the services to be
# used to change user passwords. The default is pam_unix.

# Explanation of pam_unix options:
#
# The "sha512" option enables salted SHA512 passwords. Without this option,
# the default is Unix crypt. Prior releases used the option "md5".
#
# The "obscure" option replaces the old `OBSCURE_CHECKS_ENAB' option in
# login.defs.
#
# See the pam_unix manpage for other options.

# here are the per-package modules (the "Primary" block)
password [success=1 default=ignore] pam_unix.so obscure sha512
# here's the fallback if no module succeeds
password requisite pam_deny.so
# prime the stack with a positive return value if there isn't one already;
# this avoids us returning an error just because nothing sets a success code
# since the modules above will each just jump around
password required pam_permit.so
# and here are more per-package modules (the "Additional" block)
password optional pam_smbpass.so nullok use_authtok use_first_pass

Hi again and thanks for the help birdman. Actually no, I haven't done a thing with Samba and as far as I know, I don't even have it installed?!?
I have also re-flashed the box two times (to build 036 and 037) but it didn't help...

Anyway here is the output you asked:

root@gbquadplus:~# grep passwd /var/log/messages
Mar 5 13:31:09 gbquadplus authpriv.err passwd[2140]: pam_unix(passwd:chauthtok): unrecognized option [obscure]
Mar 6 23:55:14 gbquadplus authpriv.err passwd[23929]: pam_unix(passwd:chauthtok): unrecognized option [obscure]
Mar 6 23:55:18 gbquadplus authpriv.err passwd[23956]: pam_unix(passwd:chauthtok): unrecognized option [obscure]
Mar 7 09:13:57 gbquadplus authpriv.err passwd[23352]: pam_unix(passwd:chauthtok): unrecognized option [obscure]

 

[birdman]

Sorry, forgot to send common-password -file. Here it is:
.....
# and here are more per-package modules (the "Additional" block)
password optional pam_smbpass.so nullok use_authtok use_first_pass

That's the line which causes the problem.
You could comment it out, but the real question is how it came to be there in the first place. It's added by the samba-base package. Have you installed that?

 

[janski74]

yep, that did the trick. Now passwd works as it is supposed to work...

Indeed this samba -issue is weird. I haven't installed anything like that to the box. The only option that I can think of, is that the store which I bought the box from, sent a new image some time ago. Maybe this image has samba installed and configured wrong, maybe...

Anyway. thanks a lot for the great support birdman!

That's the line which causes the problem.
You could comment it out, but the real question is how it came to be there in the first place. It's added by the samba-base package. Have you installed that?

 

[birdman]

Anyway. thanks a lot for the great support birdman!

You're welcome.
Now I feel have to set up my system then other way round to find out what it is(n't) doing.
Fortunately I have a system setup through qemu in a VirtualBox Debian installation for such messing around.