Unit 193

Yes it does, confirmed with i386 and armhf both. Thanks.

G'day! While building the new version for 32bit arches (armhf, i386) I hit a failure to build in PCSCException.cpp, snippet below. It seems at least for the i386 CentOS builds you hit no such problem, though. ../Common/PCSCException.cpp: In member function ‘virtual void VeraCrypt::PCSCException::Deserialize(std::shared_ptr<VeraCrypt::Stream>)’: ../Common/PCSCException.cpp:143:31: error: no matching function for call to ‘VeraCrypt::Serializer::Deserialize(const char [10], LONG&)’ 143 | sr.Deserialize("ErrorCode",...

I use Debian unstable on my desktop and have VeraCrypt installed, it works fine for both VC volumes and TC volumes. What errors are you getting? Any output on the terminal if launched from there? Note I'm not using the package built from upstream, but it should still be nearly the same anyway.

Howdy, You can check out the general overview at repology, and there's some unofficial, contributed resources such as an Ubuntu PPA and I'm testing out an OBS repo for Debian (based) users. You'll find it's lacking from the repositories of many Linux distributions due to the license the TrueCrypt authors chose. ~Unit 193 Unit193 @ freenode Unit193 @ OFTC

Ah! Thank you, that makes sense. I see my error, I scolled too far down on https://sourceforge.net/projects/veracrypt/files/VeraCrypt%201.24-Update5/ it seems. Thanks for the quick reply. ~Unit 193

Howdy, So it seems the last two updates didn't have release tarballs (and associated detacted signatures) on either here or launchpad.net. Is this the plan moving forward or were they (hopefully) mistakenly missed? Currently I watch for [Vv]era[Cc]rypt_([\d\w\._-]+)_[Ss]ource\.tar\.(?:gz|bz2|xz) but I could repack a zipfile, it just wouldn't be as easily verifiable by the detached signature. ~Unit 193

Howdy, I've updated that PPA so you should be able to upgrade to '1.24-Update2' now. ~Unit 193

Howdy, My apologies. The error message following the check to see if any VeraCrypt volumes are mounted erroneously echos to STDOUT, whereas it should send it to STDERR to include it in graphical updaters. This should be fixed next release. ~Unit 193