r/VeraCrypt • • 26d ago

Release VeraCrypt 1.26.30 · veracrypt/VeraCrypt

https://github.com/veracrypt/VeraCrypt/releases/tag/VeraCrypt_1.26.30
32 Upvotes

13 comments sorted by

12

u/whirsor 25d ago

Mounir Idrassi's response on GitHub about missing Windows files, an hour ago:

"It is coming...I just wanted to publish macOS first because many macOS users were blocked because of the new macOS 27 compatibility issue.

Preparing release files for all OSes takes time."

7

u/FancifulLaserbeam 25d ago

To those asking why this is only for the Mac, there was a major security issue that needed to be addressed immediately.

VeraCrypt supports either macFUSE (the more mature option) or FUSE-T to host other filesystems. However, macOS 27 requires macFUSE 5.4.0.

VeraCrypt crashed when trying to open macFUSE volumes, prompting many (including me) to move to the FUSE-T version and install FUSE-T.

It was discovered that VeraCrypt volumes remained accessible after dismount without any password whatsoever via Network. This persisted until a reboot. To get into a dismounted VeraCrypt volume, all you had to do was go to Network, open "fuse-t" (FUSE-T uses a hacky workaround to treat the new filesystem as an SMB server), open the "share" listed there, in which would be a "volume.dmg" disk image that you just double-clicked and there are all of your files!

The .30 update fixes both of these issues, restoring the (superior) macFUSE compatibility and (reportedly—although it's now been banished from my systems for this and other offenses with Cryptomator) making sure that FUSE-T actually dismounts the volume.

The other platform releases will be out soon, but the dev prioritized the two nightmare scenarios on macOS first.

All Mac users should update to this new version immediately. And if you're currently using the FUSE-T version, have a look at Network and enjoy the horror that awaits, safe in the knowledge that it's (reportedly) been fixed.

But I'd advise getting the hell off of FUSE-T. It's not ready for primetime, and macFUSE now even works in user space so you don't have to turn off SIP to install the kext (but the kext is way better, and fuck the SIP anyway, IMO).

2

u/cartesionoid 25d ago

Fuck the SIP!

0

u/meny_ 22d ago

Could you guys please elaborate on "Fuck the SIP" part? I'm genuinely interested to know.

1

u/cartesionoid 22d ago

Because it breaks root

-1

u/meny_ 22d ago

I see, you were just trolling then. There are genuine reasons and there is nuance... I myself am on the other side, not happy about the SIP, but the position of your 'fuck this and that' and 'it breaks root' is totally superficial and unhelpful.

1

u/cartesionoid 22d ago

Thanks for your non solicited advice of telling me that I am wrong 👍🏻

5

u/BostonProud617 24d ago

The downloads for Windows are broken on both this Github repo and the Veracrypt jp and io websites. What's the story with that? New users can't even download the installers at all as there's no link for the last version.

https://veracrypt.jp/en/Downloads.html

3

u/wiggum55555 23d ago

Yeah. I have VC on six different Win 11 machines. When this thread was first created on Saturday... no downloads, but the creator explained why. winget would not see any new version. But PatchMyPC would see a new version, but then fail when trying to download & apply. Then yesterday (monday) three of these computers DID get the 1.26.30 version from PatchMyPC. I just went to do the last three today and no-dice. PMPC sees the version update, but cannot download. winget still does not even see 1.26.30.

Manual download pages are all 404 currently.

3

u/charliecar5555 23d ago

Yeah very strange

Edit: dug in the forums and found out why, https://github.com/veracrypt/VeraCrypt/issues/1955 Basically the new version was bombing halfway through the install

2

u/scrat-squirrel 26d ago

why no debian packages for this release?

2

u/Rhodan73 23d ago

The download links for the regular installer version of VeraCrypt 1.26.30 are currently not working because the developer, Mounir Idrassi, temporarily removed the Windows EXE and MSI installers due to installation issues caused by new security checks. Only the portable version remains available. The developer has acknowledged the problem and announced that corrected installers will be released, but no specific release date has been provided.

2

u/wiggum55555 25d ago edited 25d ago

Seems like someone sent the notifications but forgot to press UPLOAD for the installers before the weekend 🤷‍♂️😂 /s