Modify

Opened 6 years ago

Closed 5 years ago

Last modified 2 years ago

#9350 closed defect (obsolete)

dropbear Not started during First Boot

Reported by: Raghu Pobbi Venkatachalapathy <raghupv30@…> Owned by: developers
Priority: normal Milestone: Barrier Breaker 14.07
Component: packages Version: Trunk
Keywords: Cc: raghupv30@…

Description

Steps to Replicate:

  1. Checkout the latest trunk source (bleeding edge r26748)
  2. In make menuconfig select Kernel Module for IPV6 (Network Support-> IPV6->kmod-ipv6) and also the device as Tplink WR1043ND. Also enable crond as well
  3. Build the firmware from this source and flash it to Tplink WR1043ND
  4. During First Boot Login via telnet and change the password using passwd to access via dropbear
  5. Dropbear server is never started before/after executing passwd and hence also telnetd is stopped after executing passwd. Now the device has no telnet and no dropbear access. The rsa and dsa key files for dropbear are generated at /tmp but never copied to /etc/dropbear directory. Even the crond isn't started during first boot

This issue is seen "only when IPV6 support" is enabled in menuconfig. The device is not starting dropbear during First Boot which could be busy building file system.

Attachments (0)

Change History (4)

comment:1 follow-up: Changed 6 years ago by jow

The crond is never started automatically unless a crontab exists.
As for the dropbear issue, did you wait until the overlay filesystem was built completely before changing the password?

comment:2 in reply to: ↑ 1 Changed 6 years ago by Raghu Pobbi Venkatachalapathy <raghupv30@…>

Replying to jow:

The crond is never started automatically unless a crontab exists.

Thanks, after creating a crontab entry before crond startup, i see the crond being started during first boot. So cron is not an issue.

As for the dropbear issue, did you wait until the overlay filesystem was built completely before changing the password?

Regarding dropbear, i have tried executing passwd after 3 minutes and still find no dropbear server being started.
I believe the dropbear server should be started in init.d scripts at startup. passwd might just ensure use new login credentials as it is stored in /etc/passwd
A small modification to start dropbear server after few secounds of generating key(rss and dss files) makes it working. But i believe there will be better solution for this problem.

Code: /etc/init.d/cron

/usr/bin/dropbearkey -t $keytype -f /tmp/$key 2>&- >&- && sleep 10 && exec /etc/rc.common "$initscript" start
Its just the device takes very long time to build filesystem when IPV6 is enabled and for some reason the generated key files are not copied to /etc/dropbear directory.

comment:3 Changed 5 years ago by nbd

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

comment:4 Changed 2 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

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


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

 
Note: See TracTickets for help on using tickets.