Update Cryptsetup to v1.6+

New features which should be implemented in Porteus; suggestions are welcome. All questions or problems with testing releases (alpha, beta, or rc) should go in their relevant thread here, rather than the Bug Reports section.
Post Reply
go2null
White ninja
White ninja
Posts: 25
Joined: 19 Aug 2014, 18:28
Distribution: LXDE-v3.0.1-i486.iso
Location: Canada

Update Cryptsetup to v1.6+

Post#1 by go2null » 22 Aug 2014, 00:53

The main use cases for updating to v1.6+ is support for TrueCrypt containers. This allows secure file sharing with Windows, instead on leaving plain files on the FAT32 USB drive.

Also, the current cryptsetup in initrd does not support aes-xts-plain save.dat files. (Or, at least, it complained and skipped such a save.dat. Had to use my cell phone to take a video to see what happened :-))

Also, the cryptsetup on the desktop is at v1.4.3, the latest release is v1.6.6 (released a few days ago, 2014-08-16), and v1.6.0 was released over a year and half ago (2013-01-14).

User avatar
fanthom
Site Admin
Site Admin
Posts: 5497
Joined: 28 Dec 2010, 02:42
Distribution: Porteus Kiosk
Location: Poland
Contact:

Re: Update Cryptsetup to v1.6+

Post#2 by fanthom » 22 Aug 2014, 06:04

will do for next release.

thanks
Please add [Solved] to your thread title if the solution was found.

go2null
White ninja
White ninja
Posts: 25
Joined: 19 Aug 2014, 18:28
Distribution: LXDE-v3.0.1-i486.iso
Location: Canada

Re: Update Cryptsetup to v1.6+

Post#3 by go2null » 20 May 2015, 14:33

cryptsetup is still at v1.4.3 in Porteus-LXQt-v3.1-i486.

User avatar
fanthom
Site Admin
Site Admin
Posts: 5497
Joined: 28 Dec 2010, 02:42
Distribution: Porteus Kiosk
Location: Poland
Contact:

Re: Update Cryptsetup to v1.6+

Post#4 by fanthom » 20 May 2015, 18:00

latest version must never compile against uClibc.
added back to my TODO list.
Please add [Solved] to your thread title if the solution was found.

KnallKopf
Samurai
Samurai
Posts: 134
Joined: 18 Sep 2012, 20:56
Distribution: Porteus 64bit KDE4
Location: Absurdistan

Re: Update Cryptsetup to v1.6+

Post#5 by KnallKopf » 12 Jun 2015, 19:06

i have done month before
see here

go2null
White ninja
White ninja
Posts: 25
Joined: 19 Aug 2014, 18:28
Distribution: LXDE-v3.0.1-i486.iso
Location: Canada

Re: Update Cryptsetup to v1.6+

Post#6 by go2null » 21 Oct 2015, 10:59

cryptsetup is now at v1.6.7 and adds support for VeraCrypt containers[1].
Note that VeraCrypt has patched some flaws[2] in TrueCypt, and so is now the defacto replacement for TrueCrypt.

[1] veracrypt support: https://gitlab.com/cryptsetup/cryptsetup/issues/245
[2] VeraCrypt Release Notes: https://veracrypt.codeplex.com/wikipage ... se%20Notes

KnallKopf
Samurai
Samurai
Posts: 134
Joined: 18 Sep 2012, 20:56
Distribution: Porteus 64bit KDE4
Location: Absurdistan

Re: Update Cryptsetup to v1.6+

Post#7 by KnallKopf » 08 Nov 2015, 02:53

Thanks i have update and move to here

sos
White ninja
White ninja
Posts: 4
Joined: 07 Jul 2022, 19:37
Distribution: x86_64 XFCE

Update Cryptsetup to v1.6+

Post#8 by sos » 11 Jul 2022, 21:02

go2null wrote:
20 May 2015, 14:33
cryptsetup is still at v1.4.3 in Porteus-LXQt-v3.1-i486.
Well, now cryptsetup is STILL at v1.4.3 in x86_64 Xfce Porteus version 5.0! Updating it was first discussed in 2014.
I added current cryptsetup v2.4.3 in 5.0rc3 and it worked fine for my purposes. Is there some reason it was never updated?

User avatar
ncmprhnsbl
DEV Team
DEV Team
Posts: 3510
Joined: 20 Mar 2012, 03:42
Distribution: 5.0-current-64bit
Location: australia
Contact:

Update Cryptsetup to v1.6+

Post#9 by ncmprhnsbl » 11 Jul 2022, 23:36

sos wrote:
11 Jul 2022, 21:02
Is there some reason it was never updated?
:) probably lots of reasons, none of them good ;p
our crypsetup lives in 003-kernel for some early initrd trickery and is statically built for this purpose (adding your own for your own purposes will have no effect on this part)
i have been aware of this, and been thinking about doing something about it, thanks for reminding me..
now putting it on my TODO list (right at top)

Post Reply