| 2015-09-21 08:03:24 |
Madper Xie |
bug |
|
|
added bug |
| 2015-09-21 08:03:24 |
Madper Xie |
attachment added |
|
test.patch https://bugs.launchpad.net/bugs/1497883/+attachment/4470114/+files/test.patch |
|
| 2015-09-21 08:08:15 |
Madper Xie |
description |
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.
I can reproduce the issue in ubuntu 14.04.3.
The version of dropbear is 2013.60-1ubuntu2.1
`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. |
|
| 2015-09-21 08:18:24 |
Ubuntu Foundations Team Bug Bot |
tags |
|
patch |
|
| 2015-09-21 08:18:31 |
Ubuntu Foundations Team Bug Bot |
bug |
|
|
added subscriber Ubuntu Review Team |
| 2015-09-21 13:23:23 |
Madper Xie |
nominated for series |
|
Ubuntu Trusty |
|
| 2015-09-22 05:18:31 |
Madper Xie |
bug task added |
|
oem-priority |
|
| 2016-05-30 09:51:19 |
Ara Pulido |
bug task added |
|
dropbear (Ubuntu Trusty) |
|
| 2016-05-30 11:28:22 |
Ara Pulido |
oem-priority: status |
New |
Incomplete |
|
| 2016-07-18 16:23:01 |
Matt Johnston |
attachment added |
|
dropbear-2013.60-iovlimit.diff https://bugs.launchpad.net/ubuntu/+source/dropbear/+bug/1497883/+attachment/4702927/+files/dropbear-2013.60-iovlimit.diff |
|
| 2016-08-08 13:33:26 |
Madper Xie |
tags |
patch |
patch verification-done |
|
| 2016-08-08 13:33:36 |
Madper Xie |
tags |
patch verification-done |
patch |
|
| 2017-02-08 06:30:06 |
Yuan-Chen Cheng |
bug task deleted |
oem-priority |
|
|
| 2017-05-02 10:53:59 |
gerald.yang |
attachment added |
|
dropbear_2013.60-1ubuntu2.2.debdiff https://bugs.launchpad.net/ubuntu/+source/dropbear/+bug/1497883/+attachment/4870747/+files/dropbear_2013.60-1ubuntu2.2.debdiff |
|
