Bug 12306 - xz applet not reporting errors
Summary: xz applet not reporting errors
Status: NEW
Alias: None
Product: Busybox
Classification: Unclassified
Component: Other (show other bugs)
Version: 1.31.x
Hardware: All Linux
: P5 normal
Target Milestone: ---
Assignee: unassigned
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-11-02 17:23 UTC by Jeff Pohlmeyer
Modified: 2019-11-02 17:25 UTC (History)
2 users (show)

See Also:
Host:
Target:
Build:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jeff Pohlmeyer 2019-11-02 17:23:38 UTC 
With previous versions of busybox the xz applet would report an error and exit with error status if the input was invalid:


echo ThisIsNotXZ | busybox xz -dc ; echo $?

xz: corrupted data
1


But the latest version does not show any error message and exits with zero:

echo ThisIsNotXZ | busybox xz -dc ; echo $?
0


I have not checked for sure, but this might be caused by commit 42f454b13b8d972e85acd7f046065ec69af4d206

"dpkg-deb: work around bogus error message when working with XZ compressed packages"