Matt Johnston
Matt Johnston
I've pushed a few changes on top of this, and added in PR #281 from @HansH111 . `stricthostkeychecking=yes` is changed a bit, previously it was asking whether to add.
Can you get a tcpdump/wireshark capture of the failed session? My first thoughts would be either DNS or network MTU has problems.
Dropbear delays 5 seconds from accepting the connection and sending the first packet. Did you compile Dropbear, or where is the package from? DNS seems a likely reason if it's...
What hardware and OS is Dropbear running on? What client are you using from each network?
Can you send "ssh -vvv" output from both the fast and the slow networks? Thanks
It looks like the newlines got broken, can you try paste it differently?
OK, nothing obvious there. Are there any other connections being made to the SSH server at the same time by chance? (Wondering if it's the pre-auth per-IP limit. Seems unlikely).
Dropbear always reads `/etc/shadow` first for a crypt, then falls back to `/etc/passwd`. I'll update it to handle `'x'` specially, I had missed that.
The `fuzzstandalone` code performs a kind of regression testing, using a fixed corpus of fuzz results that previously was created by running oss-fuzz. The fuzzstandalone harness just feeds in pre-existing...
> I see what you mean about it failing - that seems like a pre-existing bug being triggered the corpus, I'll investigate. There's a mismatch between the fuzzing malloc wrapper...