|
1 | 1 | # Change Log
|
2 | 2 |
|
| 3 | +## Version 0.12.3 - 2025-04-21 |
| 4 | + |
| 5 | +- (fix) Automatic image offset detection (for images using a custom |
| 6 | + header) did not work correctly if the header contained a string that |
| 7 | + would be identified as the start of a v1 section header (these were |
| 8 | + only used before dwarfs-0.3.0). If there was either `"DWARFS\x02\x00"` |
| 9 | + or `"DWARFS\x02\x01"` in the header, offset detection would fail. |
| 10 | + The check has been modified to peek further into the data and ensure |
| 11 | + this *really* is a v1 section header, and also checking if the next |
| 12 | + section header position can be derived from the length field. It is |
| 13 | + still possible to construct a file system image where offset detection |
| 14 | + will ultimately fail, but it is much less likely with the change. |
| 15 | + |
| 16 | +- (build) The build process for the release binaries has been further |
| 17 | + tweaked to reduce binary size. The `dwarfs-fuse-extract` binary now |
| 18 | + again supports extracting files by pattern; I didn't realize that |
| 19 | + this was actually a widely used feature before dropping it in the |
| 20 | + last release. `dwarfs-universal` is now linked against LibreSSL's |
| 21 | + `libcrypto` instead of OpenSSL's. This significantly reduces the size |
| 22 | + at the expense slightly slower cryptographic hash functions. However, |
| 23 | + this will likely *only* be perceivable when using `--tool=dwarfsck` |
| 24 | + with either `--check-integrity` or `--checksum`. The binaries from the |
| 25 | + release tarballs are still linked against `libcrypto` from OpenSSL. |
| 26 | + |
3 | 27 | ## Version 0.12.2 - 2025-04-16
|
4 | 28 |
|
5 | 29 | - (fix) A performance regression introduced in v0.12.0 was fixed. This
|
|
0 commit comments