aboutsummaryrefslogtreecommitdiffstats
path: root/package/system/fwtool/Makefile
diff options
context:
space:
mode:
authorJo-Philipp Wich <jo@mein.io>2019-10-17 16:59:11 +0200
committerJo-Philipp Wich <jo@mein.io>2019-10-17 17:07:12 +0200
commit889b841048c5eb7f975135cab363f1fdd9b6cfa1 (patch)
treebcf1dc4aa8c685e5992033d86dbbb2fbc1012324 /package/system/fwtool/Makefile
parent6caf437652d858e5795ee16bdaf9f0436d2488f9 (diff)
downloadupstream-889b841048c5eb7f975135cab363f1fdd9b6cfa1.tar.gz
upstream-889b841048c5eb7f975135cab363f1fdd9b6cfa1.tar.bz2
upstream-889b841048c5eb7f975135cab363f1fdd9b6cfa1.zip
fwtool: do not omit final 16 byte when image does not contain signature
The fwutil command will interpret the final 16 byte of a given firmware image files as "struct fwimage_trailer". In case these bytes do look like a valid trailer, we must ensure that we print them out along with the remainder of the image to not accidentally truncate non-trailer-images by 16 bytes when they're piped through fwtool, e.g. as part of an image verification command sequence. Some command sequences pipe images through fwtool in order to strip any possible metadata, certificate or signature trailers and do not expect bare images without any of that metadata to get truncated as other non- fwtool specific metadata is expected at the end of the file, e.g. an information block with an md5sum in case of the combined image format. Signed-off-by: Jo-Philipp Wich <jo@mein.io>
Diffstat (limited to 'package/system/fwtool/Makefile')
-rw-r--r--package/system/fwtool/Makefile2
1 files changed, 1 insertions, 1 deletions
diff --git a/package/system/fwtool/Makefile b/package/system/fwtool/Makefile
index 901081c1f4..283be8d77a 100644
--- a/package/system/fwtool/Makefile
+++ b/package/system/fwtool/Makefile
@@ -8,7 +8,7 @@
include $(TOPDIR)/rules.mk
PKG_NAME:=fwtool
-PKG_RELEASE:=1
+PKG_RELEASE:=2
PKG_FLAGS:=nonshared