Opened 6 years ago

Closed 6 years ago

Last modified 4 years ago

#10537 closed defect (invalid)

Password not set & SSH is inaccesible

Reported by: Aswin Paranji <aswin.paranji@…> Owned by: developers
Priority: normal Milestone: Barrier Breaker 14.07
Component: packages Version: Trunk
Keywords: Cc:


The password is not set on the router even after setting the password in router's administration page. The "Password changed successfully" message is seen. However, on the top it still says password not set.

Due to this, the router cannot be accessed using ssh.

is there any other way to access the router.

Attachments (0)

Change History (7)

comment:1 Changed 6 years ago by hnyman <hannu.nyman@…>

If you are talking about a newly compiled firmware, you are probably running into the effects of the newly introduced shadow password usage. (Init scripts have been changed to expect shadow passwords, but their usage is not forcibly turned on for old .config files for compilation. New configs will have the correct setting by default.)

You have to either build .config from scratch or change the option by hand. Check if CONFIG_BUSYBOX_CONFIG_FEATURE_SHADOWPASSWDS is enabled in your .config:

menuconfig > Base system > busybox > Login/Password Management Utilities > Support for shadow passwords.

Read #10405, #10412, #10393, ...

comment:2 Changed 6 years ago by aswin.paranji@…

Thanks for the info.
cleaning up the '.config' really solved the problem.

Please close the ticket.

comment:3 Changed 6 years ago by Mike van Lammeren <mike@…>

I do have CONFIG_BUSYBOX_CONFIG_FEATURE_SHADOWPASSWDS set in my .config, and I still can't get ssh logins to work. After I tftp the image to my Buffalo router, I telnet in, set the root password with passwd, then reboot, and it refuses to let me log in via ssh.

Here are some log entries from the attempt:

Dec  5 16:04:29 OpenWrt dropbear[2353]: Child connection from
Dec  5 16:04:31 OpenWrt authpriv.warn dropbear[2353]: Bad password attempt for 'root' from

comment:4 Changed 6 years ago by jow

You must also ensure that both Busybox and base-files get rebuild after updating the .config . Additionally if you embed an /etc/passwd you have to update it as well.

comment:5 Changed 6 years ago by Mike van Lammeren <mike@…>

Yes, thank you -- it was an old /etc/passwd file.

comment:6 Changed 6 years ago by jow

  • Resolution set to invalid
  • Status changed from new to closed

Config issue

comment:7 Changed 4 years ago by jow

  • Milestone changed from Attitude Adjustment 12.09 to Barrier Breaker 14.07

Milestone Attitude Adjustment 12.09 deleted

Add Comment

Modify Ticket

as closed .
The resolution will be deleted. Next status will be 'reopened'.

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.