Bug#979617: tcplay: VeraCrypt support
Hi László-- Thanks for sorting out the 3.3-1 upload for tcplay, multiarch-ifying library along the way, and updating the packaging history in Salsa, too! With much appreciation, --dkg signature.asc Description: PGP signature
Bug#979617: tcplay: VeraCrypt support
On Mon, Apr 22, 2024 at 8:33 PM Daniel Kahn Gillmor wrote: > On Sun 2024-04-21 15:44:12 +0200, László Böszörményi (GCS) wrote: > > I prefer communication first. :) Currently I'm travelling so I can > > only check it on Tuesday. > > That's why i uploaded to DELAYED/15 :) thanks for offering to take a > look at it later this week, László! I meant to reach a consensus first and then do the upload. There's no point in an upload that needs to be cancelled. Best, Laszlo/GCS
Bug#979617: tcplay: VeraCrypt support
On Sun 2024-04-21 15:44:12 +0200, László Böszörményi (GCS) wrote: > I prefer communication first. :) Currently I'm travelling so I can > only check it on Tuesday. That's why i uploaded to DELAYED/15 :) thanks for offering to take a look at it later this week, László! > There were some license problems in the past at least, which > prevented packaging. I will check the current situation. That's good to know! in the version i uploaded, it looked like a simple 2-clause BSD, but i'm sure you have more detailed historical knowledge. All the best, --dkg signature.asc Description: PGP signature
Bug#979617: tcplay: VeraCrypt support
Hi, On Sun, Apr 21, 2024 at 9:06 AM Daniel Kahn Gillmor wrote: > 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. [...] > 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 prefer communication first. :) Currently I'm travelling so I can only check it on Tuesday. > 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). There were some license problems in the past at least, which prevented packaging. I will check the current situation. Regards, Laszlo/GCS
Bug#979617: tcplay: VeraCrypt support
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
Bug#979617: tcplay: VeraCrypt support
Retitle: 979617 tcplay: new upstream version 3.3 (includes VeraCrypt support) On Thu 2023-02-16 15:07:10 +0100, Johannes Truschnigg wrote: > tc-play 3.3 seems to build fairly cleanly on bullseye from its tag/release > tarball [0]. It'd be *really* nice to have in Debian to be able to handle > VeraCrypt volumes. It would be great to have this updated version of tcplay in debian. If there's some reason to not update tcplay in debian, it would be good to know. The package hasn't seen any updates in debian since oldoldstable. --dkg signature.asc Description: PGP signature
Bug#979617: tcplay: VeraCrypt support
Dear maintainer, tc-play 3.3 seems to build fairly cleanly on bullseye from its tag/release tarball [0]. It'd be *really* nice to have in Debian to be able to handle VeraCrypt volumes. [0]: https://github.com/bwalex/tc-play/archive/v3.3.tar.gz -- with best regards: - Johannes Truschnigg ( johan...@truschnigg.info ) www: https://johannes.truschnigg.info/ phone: +43650217 xmpp: johan...@truschnigg.info signature.asc Description: PGP signature
Bug#979617: tcplay: VeraCrypt support
Package: tcplay Version: 1.1-6 Severity: normal Dear Maintainer, It seems that VeraCrypt is supported in 3.0 in the upstream of tcplay. https://github.com/bwalex/tc-play/blob/master/CHANGELOG#L15 I hope it will be updated so that VeraCrypt can be used. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf, arm64 Kernel: Linux 5.10.0-1-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_CRAP, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages tcplay depends on: ii libc6 2.31-9 ii libdevmapper1.02.1 2:1.02.173-1 ii libgcrypt20 1.8.7-2 ii libgpg-error0 1.38-2 ii libuuid12.36.1-4 tcplay recommends no packages. tcplay suggests no packages. -- no debconf information
