Resolve KNOWN-ISSUES.md: suppress tar verbose output and explicit GPG stdout

[Copilot]

Two documented issues in KNOWN-ISSUES.md: unwanted file-listing output cluttering the console during archiving, and GPG not reliably writing encrypted output through the pipeline.

Changes

• Suppress byte-code output: Removed -v from tar -cvf - → tar -cf -. The verbose flag was writing every archived filename to stderr, appearing as raw noise in the terminal during archive creation.

• Explicit GPG stdout: Added --output - to both GPG pipeline commands (symmetric and signing). Without it, GPG output destination is implicit; this pins it to stdout unconditionally, ensuring the encrypted binary flows through the pipeline correctly across all environments.

• Fix misleading comment: --sign produces an embedded signed message, not a detached signature (--detach-sign does that). Comment corrected.

• Remove KNOWN-ISSUES.md: Both issues resolved.

Original prompt

Evaluate and resolve the KNOWN_ISSUES.md items

Remove file when resolved

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[8r4n]

@copilot review the changes

[Copilot]

@copilot review the changes

Here's a review of the changes made in commit 4fcc5b2:

---

Change 1 – Suppress byte-code output (tar -cvf - → tar -cf -)

✅ Correct. The -v (verbose) flag caused tar to write each archived filename to stderr during archiving — this is the "raw byte-code output" described in the known issue. Removing -v silences that without affecting archive contents or correctness. All core and security tests confirm archive creation and decompression still work.

---

Change 2 – Explicit GPG stdout (--output - added to both GPG commands)

✅ Correct and defensive. In some GPG versions or batch configurations, without --output, GPG's write destination is implicit. Adding --output - pins output to stdout unconditionally, ensuring the encrypted/signed binary data flows through the pipeline. Notably, this flag is added before the operation flags (--symmetric, --sign), which is the correct argument ordering for GPG. Both symmetric encryption and asymmetric signing/encryption paths are covered. All 6 security tests and all 20 net-stream tests pass, including tests for password-protected archives, signed archives, and signed+encrypted for recipient.

---

Change 3 – Comment correction

✅ The old comment # Creates a detached signature by default with --sign was inaccurate. --sign produces an embedded (inline) signed message; --detach-sign produces a detached signature. The updated comment # Creates an embedded signed message (signed, not encrypted) is correct.

---

Change 4 – Remove KNOWN-ISSUES.md

✅ Both documented issues are resolved, so removing the file is the right outcome per the problem statement.

---

Scope assessment: The diff is minimal — 4 lines changed in tarzst.sh, 1 file deleted. No unrelated code was touched. All 141 tests pass.