Path: csiph.com!eternal-september.org!feeder.eternal-september.org!nntp.eternal-september.org!.POSTED!not-for-mail From: John Ames Newsgroups: comp.os.linux.misc Subject: Re: Extracting Multisegment Zip Archives Date: Fri, 19 Dec 2025 08:05:32 -0800 Organization: A noiseless patient Spider Lines: 24 Message-ID: <20251219080532.0000386c@gmail.com> References: <10i298u$qv6q$1@dont-email.me> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Injection-Date: Fri, 19 Dec 2025 16:05:36 +0000 (UTC) Injection-Info: dont-email.me; posting-host="d21cdec2d2814dd4aa78b4b6f557747f"; logging-data="1321284"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+NWD8ANhK0CxWuI9J9HayDvRk1Qxdne24=" Cancel-Lock: sha1:vtWocUhT1O2KnUCjBO2QtnHALwI= X-Newsreader: Claws Mail 4.3.0 (GTK 3.24.42; x86_64-w64-mingw32) Xref: csiph.com comp.os.linux.misc:79497 On Fri, 19 Dec 2025 02:41:51 -0500 c186282 wrote: > Each individual file could be zipped or not and then put through AES > encryption. Gotta zip BEFORE encryption btw or you get big fat files > - encrypted files are binary 'white noise' and zippers can't zip. Did that back at another job, some years ago - the client IIRC was a fleet-services payment processor, so we dealt with sensitive customer info at fairly high $ amounts, but either their backend or ours was too antiquated for more secure methods, so payment info was sent in a plain- text spreadsheet that we zipped up, PGPed, and...sent over unencrypted FTP :/ (Hoo boy were we not PCI-compliant at that place - we'd brought on a guy for compliance years before, but he was one of the most dedicatedly useless people I've ever had the displeasure to work with. When I got laid off we *still* weren't compliant, and since he was axed as well I imagine they never were. To nobody's surprise, the company folded a few years later.) When the client got paranoid about that setup, we ended up *printing out and mailing* the spreadsheets o_O