Compare commits

...

2 commits

Author SHA1 Message Date
9d31798da6 Version 1.5, update Changelog.md
All checks were successful
Run Unit Tests / build-and-run-unit-tests (push) Successful in 14s
Build for Releases / ensure-release-exists (push) Successful in 0s
Build for Releases / push-build-x86_64 (push) Successful in 7s
Build for Releases / push-build-aarch64 (push) Successful in 57s
Build for Releases / push-build-x86_64_debian (push) Successful in 31s
Build for Releases / push-build-aarch64_debian (push) Successful in 2m2s
2024-10-21 17:38:53 +09:00
1c06462ca7 Fix where symlink marked invalid still created v1 2024-10-21 17:35:55 +09:00
2 changed files with 8 additions and 1 deletions

View file

@ -2,6 +2,13 @@
## Upcoming Changes
## Version 1.5
Previous file-format-v1 implementation of "safe links" still created a symlink
if a relative or absolute link existed in the file. This version fixes this, and
prevents invalid symlinks from being created. (This check is only done if the
bit-flag is set in the file as mentioned in the file-format spec for v1 files.)
## Version 1.4
Do "safe links" behavior by default: symlinks pointing to outside of archived

View file

@ -3717,7 +3717,7 @@ int simple_archiver_parse_archive_version_1(FILE *in_f, int_fast8_t do_extract,
uint_fast8_t link_extracted = 0;
uint_fast8_t skip_due_to_map = 0;
uint_fast8_t skip_due_to_invalid = 0;
uint_fast8_t skip_due_to_invalid = is_invalid ? 1 : 0;
if (fread(buf, 1, 2, in_f) != 2) {
return SDAS_INVALID_FILE;