dbclient reports integrity errors with GitHub

Matt Johnston matt at ucc.asn.au
Thu Apr 23 07:46:05 AWST 2015

It sounds like something's going wrong with the cryptographic key setup. The packet size is the first thing decrypted so if they key is wrong the size will be wrong.

I'll investigate what's going on, sounds like its easy to reproduce.


On 22 April 2015 11:16:36 pm AWST, Steven Honeyman <stevenhoneyman at gmail.com> wrote:
>On 22 April 2015 at 15:39, Laurent Bercot <ska-dietlibc at skarnet.org>
>>  Hello,
>>  dropbear-2015.67, compiled with a recent (last week) musl libc,
>> statically linked.
>>  The problem also occurs with dropbear-2014.66.
>>  Since a few days ago (but I'm not sure when it started; in any
>> case it's less than a month ago), every git pull and push over SSH
>> from/to GitHub fails with the following message:
>> dbclient: Connection to git at github.com:22 exited: Integrity error
>> packet size $N)
>> $N is a nonsensical number, sometimes negative, but not always.
>>  Connections to GitHub via the OpenSSH client *work*.
>>  Connections to git repositories other than GitHub via dbclient
>>  Connections to GitHub via dbclient *do not work*, whether my client
>> key is ECDSA or RSA. I don't use DSA.
>>  Any idea of what's going on or what I could do to learn more ?
>> It's probably a GitHub problem, but I figured I had more chances of
>> finding knowledgeable people here :)
>>  Thanks,
>> --
>>  Laurent
>Hmm strange! I get the exact same behaviour with both musl and glibc,
>so it's likely a dropbear problem.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ucc.gu.uwa.edu.au/pipermail/dropbear/attachments/20150423/eb1dabe0/attachment.htm 

More information about the Dropbear mailing list