Kevin Kofler wrote:
> try tcplay, a BSD-licensed interoperable implementation that is
> already packaged in Fedora.
tcplay hasn't been maintained in a while. Upstream hasn't pushed any commits
since 2014.
https://github.com/bwalex/tc-play
And the history of builds for new releases of Fedora
Andrew Toskin wrote:
> Oh, sorry, I hadn't thought to try searching for previous threads about
> VeraCrypt in particular.
>
> And, looking at it again, the dual license here is tricky, because it
> looks like the old TrueCrypt files are still TrueCrypt-licensed, while the
> new files are
Oh, sorry, I hadn't thought to try searching for previous threads about
VeraCrypt in particular.
And, looking at it again, the dual license here is tricky, because it looks
like the old TrueCrypt files are still TrueCrypt-licensed, while the new files
are Apache-licensed. I wondered briefly
> "AT" == Andrew Toskin writes:
AT> I'm looking specifically into VeraCrypt, the open-source fork from
AT> TrueCrypt.
Has the situation which has kept VeraCrypt out of Fedora previously been
changed?
See this, for example:
Sorry if this has already been discussed, but I couldn't find a thread dealing
with this exact situation... I'm considering a new package that is
dual-licensed under a free and a nonfree license.
The Fedora Licensing Guidelines say:
> If code is multiple licensed, and at least one of the
