#2952 closed enhancement (not_a_bug)
Openssh, dropbear, etc. with wtmp, lastlog and utmp support if busybox is configured to support them
| Reported by: | Davide Guerri <d.guerri@…> | Owned by: | developers |
|---|---|---|---|
| Priority: | normal | Milestone: | Features Paradise |
| Component: | packages | Version: | |
| Keywords: | Cc: |
Description
By default applications like openssh and dropbear are configured with the following flags:
--disable-lastlog --disable-utmp --disable-wtmp
At the present time there is no way to enable lastlog, utmp and wtmp usage even if dropbear is configured with utmp and wtmp support.
Attachments (0)
Change History (6)
comment:1 in reply to: ↑ description Changed 10 years ago by Davide Guerri <d.guerri@…>
comment:2 Changed 10 years ago by blogic
- Milestone changed from Kamikaze to Kamikaze Features Paradize
comment:3 Changed 10 years ago by lars@…
I just searched lastlog in openwrt. It would be nice to see the facts about the last login when logging in via ssh.
Would be nice if you implement this in future releases.
comment:4 Changed 7 years ago by arokh <trondah@…>
If you enable utmp/wtmp/last/who in busybox and compile dropbear/openssh with the right options, it works fine.
I really don't understand why it's disabled, it adds nothing to the firmware size except value.
comment:5 Changed 3 years ago by anonymous
Most of the openwrt systems are having small diskspace by default. and thus enabling it by default is risky. My thought though, correct me if I am wrong.
comment:6 Changed 3 years ago by nbd
- Resolution set to not_a_bug
- Status changed from new to closed
Correct. If we even want to support this, it should be optional. People are free to submit patches to implement that, but we won't do it ourselves
Replying to Davide Guerri <d.guerri@caspur.it>:
I mean "even if busybox is configured with utmp and wtmp support"