Description
In commands/extract.rs line 25, the conflict-detection list_archive call uses SecurityConfig::default(), ignoring --allow-solid-archives. This means users extracting a solid 7z archive without --force or --atomic will hit a SecurityViolation at the list step, even when --allow-solid-archives is passed.
Reproduction
cargo run --bin exarch -- extract tests/fixtures/solid.7z /tmp/out/ --allow-solid-archives
# Fails at conflict-detection step with SecurityViolation (solid archives not allowed)
# Workaround: use --force or --atomic
Expected
--allow-solid-archives should be passed to the SecurityConfig used for conflict detection as well.
Severity
Medium — usability regression introduced alongside #119 fix.
Description
In
commands/extract.rsline 25, the conflict-detectionlist_archivecall usesSecurityConfig::default(), ignoring--allow-solid-archives. This means users extracting a solid 7z archive without--forceor--atomicwill hit aSecurityViolationat the list step, even when--allow-solid-archivesis passed.Reproduction
Expected
--allow-solid-archivesshould be passed to theSecurityConfigused for conflict detection as well.Severity
Medium — usability regression introduced alongside #119 fix.