Opened 2 years ago

Last modified 2 years ago

#20724 new defect

Annoying bug in dropbox refusing public-key auth sometimes

Reported by: anonymous Owned by: developers
Priority: normal Milestone:
Component: packages Version: Trunk
Keywords: Cc:


Dont know when this started but it's now since over a year or so. It happens a lot, seems random, dont know how this is triggered, that a connect via Putty is refused with the error message:

Using username "root".
Authenticating with public key "..."
Server refused public-key signature despite accepting key!

Doing a retry works fine and dropbox accepting this (most) time.

Dropbox version is 2015.68

Dropbox config as simple as:

config dropbear
	option RootPasswordAuth 'off'
	option PasswordAuth 'off'
	option GatewayPorts 'on'
	option Port '2022'

Attachments (0)

Change History (6)

comment:1 Changed 2 years ago by anonymous

Dropbox or dropbear? title says dropbox, config says dropbear...

is there even a Dropbox client in OpenWrt?

comment:2 Changed 2 years ago by anonymous

your issue might be related to ticket #20711 - check the permissions of the config file

comment:3 Changed 2 years ago by anonymous

Please no troll answers, thank you. It is clear what this ticket is about, dropbear. And no, if the permission was broken how the hell would it work most of connects then, no? That ticket is totally not related to this...

comment:4 Changed 2 years ago by anonymous

never had a problem using auth key. try to re-create a new key and create new putty profile.

comment:5 Changed 2 years ago by anonymous

I'd like to confirm this bug report.

I have come across this issue myself and reported it directly to dropbear author back in Feb-2015 (running CC trunk r44203 and dropbear 2014.65-2 and PuTTY 0.63)

I haven't noticed it in recent weeks/months, but this might be due to the fact that I'm not connecting to OpenWrt as often as I used to.

comment:6 Changed 2 years ago by hnyman

I just ran into this with a rev48720 DD trunk build when connecting with Putty 0.66.

Like the original poster said, Dropbear occasionally rejects the public key login and falls back to asking password. Not always, but sometimes. The same client will probably connect successfully the next time.

Short googling revealed one possible explanation:
faulty requirement for ssh2 signature padding in the ssh server

I haven't yet checked Dropbear sources, but thought to document the possible explanation here in any case.

Add Comment

Modify Ticket

as new .

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

Note: See TracTickets for help on using tickets.