I'm connecting via ssh to our platform running dropbear. If I cat /var/log/syslog, I'm seeing the connection break with the following:
Write failed: Broken pipe
The syslog is about 2MB size.
`xxd /dev/zero` can reproduce the issue 100%.
[Impact]
* In fact it is really an annoying bug due to I can't visit my syslog or other large file via cat.
[Test Case]
The minimum reproducer should be:
* system A running a dropbear as a ssh server.
* ssh username@systemA from system B. (A and B should be different computer.)
* xxd /dev/zero
* the connection will be broken.
[Regression Potential]
* I find the patch from upstream. And it already been merged. So I think it's safe to merge it into ubuntu.
[Other Info]
* The latest dropbear-2015.68 can't reproduce the issue.
* After a bisect I find this patch fixed the issue: https://github.com/mkj/dropbear/commit/db688e3
* There is a bit conflict if you apply above commit. The fixed version is attached.
I'm connecting via ssh to our platform running dropbear. If I cat /var/log/syslog, I'm seeing the connection break with the following:
Write failed: Broken pipe
The syslog is about 2MB size.
`xxd /dev/zero` can reproduce the issue 100%.
[Impact]
* In fact it is really an annoying bug due to I can't visit my syslog or other large file via cat.
[Test Case]
The minimum reproducer should be:
* system A running a dropbear as a ssh server.
* ssh username@systemA from system B. (A and B should be different computer.)
* xxd /dev/zero
* the connection will be broken.
[Regression Potential]
* I find the patch from upstream. And it already been merged. So I think it's safe to merge it into ubuntu.
[Other Info] /github. com/mkj/ dropbear/ commit/ db688e3
* The latest dropbear-2015.68 can't reproduce the issue.
* After a bisect I find this patch fixed the issue: https:/
* There is a bit conflict if you apply above commit. The fixed version is attached.