Control: retitle 979617 tcplay: new upstream version 3.3 (includes VeraCrypt support)
I've just confirmed what Johannes said about tcplay 3.3 building easily on debian. I uploaded 3.3-0.1 to unstable as an NMU to DELAYED/15, after cleaning up the packaging a little bit. I've imported all the history of the tcplay package from snapshots.debian.org into a git repo (using "gbp import-dscs --debsnap tcplay"), and then made my packaging changes on top of that synthetic history. I published that git repository (history + my changes) at https://salsa.debian.org/debian/tcplay on the debian/unstable branch. Hopefully this NMU is welcomed in the helpful spirit i intended with it! But if you think it's a bad idea, I don't mind it being NACK'ed. In the course of doing the cleanup i noticed a few weird things about the packaging for libtcplay, that i wasn't sure how to best fix, so i just recorded them in the BTS. I also cleaned up upstream's manpages a bit, and reported those fixes upstream at https://github.com/bwalex/tc-play/pull/84 There are probably more things that could be cleaned up upstream (the modern toolchain makes a lot of complaints about the tcplay source), but i haven't tried to fix or even report those yet. I've also tested a backported version of 3.3-0.1 to debian stable, and it seems to work fine to create an interoperable VeraCrypt volume (methodology described below). The backport to bookworm required nothing more than a new entry in debian/changelog, which is published on the debian/bookworm branch in salsa (but not uploaded anywhere yet). I tested on a dual-boot x86_64 system where /dev/vda5 is a slice visible to both a Debian stable installation with tcplay 3.3-0.1~bpo12+1 and a Windows 11 system with VeraCrypt 1.26.7 (64-bit) installed. On the Debian side, i did: ``` tcplay --create --device=/dev/vda5 --pbkdf-prf=SHA256-VC cryptsetup open --type=tcrypt /dev/vda5 vera mkfs -t vfat /dev/mapper/vera mount /dev/mapper/vera /mnt echo "this is a test" > /mnt/testing.txt umount /mnt cryptsetup close vera ``` Then i rebooted the system into Windows, and using Veracrypt, i was able to map the volume onto the E: drive using the same password i'd entered with tcplay and "cryptsetup open", and then read "this is a test" out of E:\testing.txt In my test, my password was plain 7-bit clean US-ASCII; i didn't try any fancier passwords. Regards, --dkg
signature.asc
Description: PGP signature
