Re: [LEDE-DEV] [PATCH] build: reintroduce md5 checksums for generated firmware images

2016-08-17 Thread Stefan Lippers-Hollmann
Hi On 2016-08-18, Karl Palsson wrote: > Why not just add sha256 sum rather than going back to md5? [...] Generating md5sums in addition to sha256sums files only affects build time slightly, but doesn't increase the firmware size itself. Given that apparently nothing currently requires a sha256su

Re: [LEDE-DEV] [PATCH] build: reintroduce md5 checksums for generated firmware images

2016-08-17 Thread Karl Palsson
Why not just add sha256 sum rather than going back to md5? Cheers, Karl P Stefan Lippers-Hollmann wrote: > Commit 83175687c81bee594885d0738cfd488673f5a3fb "build: remove > image specific checksum code" dropped the generation of md5 > checksums in favour of only shipping sha256 ones. > > A defa

[LEDE-DEV] [PATCH] build: reintroduce md5 checksums for generated firmware images

2016-08-17 Thread Stefan Lippers-Hollmann
Commit 83175687c81bee594885d0738cfd488673f5a3fb "build: remove image specific checksum code" dropped the generation of md5 checksums in favour of only shipping sha256 ones. A default Lede installation however doesn't enable busybox' sha256sum applet, which makes confirming the checksum on the devi