Weird (old ?) volume not supported

[Stepland]

The linux version of TrueCrypt has no problem mounting this volume : smaller_password_1234.tar.gz (mind you it's 4GBs once unzipped) but I can't get it to work with tc-play ...

Here's what the volume properties dialog shows if that helps :

[bwalex]

Hi! Volume format version 1 and 2 aren't supported by tc-play - I assume this is the message you are getting when trying?

https://github.com/bwalex/tc-play/blob/2d8d597a4879b4344bce4763883833f3489515bd/hdr.c#L140

Although maybe it doesn't even get there if the actual key derivation function for those older versions is different from any supported version.

[bwalex]

In fact - yes, you probably won't even get there, considering it's using LRW, which definitely isn't a supported mode.

[Stepland]

Thanks for the quick answer !

In fact - yes, you probably won't even get there

Yeah, iirc it just displays that the password is incorrect without more details. Smells like the code trying to deal with an unexpected failure mode.

Volume format version 1 and 2 aren't supported by tc-play

considering it's using LRW, which definitely isn't a supported mode.

For both of these things : by "unsupported" do you mean that it just so happens not to be supported by the code in its current state, or that tc-play is not meant to support it ever

If it isn't against tc-play's "mission statement" to support these, I might give it a try. I can't promise anything though.

[bwalex]

Fair question - it's not supported by the code, and I wasn't actually expecting to ever add support for them (although I did at some point briefly consider it, as evidenced by this comment: https://github.com/bwalex/tc-play/blob/2d8d597a4879b4344bce4763883833f3489515bd/tcplay.c#L64

That comment about not supporting LRW in dm-crypt and opencrypto was referring to DragonFly, though, not Linux. I think Linux' dm-crypt does support LRW. You'd still need an LRW implementation for use with gcrypt, though.

I'm definitely not against anyone adding support for these older volume types, as long as it doesn't make a big mess of the existing code. I'm sure that latter part can be worked out, though.