<html><head></head><body>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.<br>
<br>
I'll investigate what's going on, sounds like its easy to reproduce.<br>
<br>
Cheers,<br>
Matt<br><br><div class="gmail_quote">On 22 April 2015 11:16:36 pm AWST, Steven Honeyman <stevenhoneyman@gmail.com> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k9mail">On 22 April 2015 at 15:39, Laurent Bercot <ska-dietlibc@skarnet.org> wrote:<br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"><br /> Hello,<br /> dropbear-2015.67, compiled with a recent (last week) musl libc,<br /> statically linked.<br /> The problem also occurs with dropbear-2014.66.<br /><br /> Since a few days ago (but I'm not sure when it started; in any<br /> case it's less than a month ago), every git pull and push over SSH<br /> from/to GitHub fails with the following message:<br /><br /> dbclient: Connection to git@github.com:22 exited: Integrity error (bad<br /> packet size $N)<br /><br /> $N is a nonsensical number, sometimes negative, but not always.<br /><br /> Connections to GitHub via the OpenSSH client *work*.<br /> Connections to git repositories other than GitHub via dbclient *work*.<br /> Connections to GitHub via dbclient *do not work*, whether my client<br
/> key is ECDSA or RSA. I don't use DSA.<br /><br /> Any idea of what's going on or what I could do to learn more ?<br /> It's probably a GitHub problem, but I figured I had more chances of<br /> finding knowledgeable people here :)<br /><br /> Thanks,<br /><br /> --<br /> Laurent<br /></blockquote><br />Hmm strange! I get the exact same behaviour with both musl and glibc,<br />so it's likely a dropbear problem.<br /><br />Steven<br /></pre></blockquote></div></body></html>