DM-Crypt Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sophie Hunt <sophie.hunt@ctechemail.com>
To: dm-crypt@saout.de
Subject: [dm-crypt] TrueCrypt is discontinued - here are the alternatives
Date: Thu, 22 Dec 2016 10:13:19 +0000	[thread overview]
Message-ID: <5320291.or_mail@ctechemail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 880 bytes --]

Hi,

I noticed you've shared TrueCrypt on this page https://unstable.nl/cgi-bin/man/man2html?8+cryptsetup, as you may be aware, development of TrueCrypt was discontinued back in 2014 and has subsequently not been maintained. A number of security flaws have been uncovered and as a result we are reaching out to people to highlight a list of alternatives.

Here's the list (along with further details about TrueCrypt no longer being maintained) - https://www.comparitech.com/blog/information-security/truecrypt-is-discoutinued-try-these-free-alternatives/, when you update your page it could be a useful resource to point your visitors to.

Please let me know if you have any questions.

-Sophie
Don't want emails from us anymore? Reply to this email with the word "UNSUBSCRIBE" in the subject line.
Comparitech, Kings Lodge, London Road, Sevenoaks Kent, TM15 6AR, United Kingdom


[-- Attachment #2: Type: text/html, Size: 971 bytes --]

             reply	other threads:[~2016-12-22 10:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-22 10:13 Sophie Hunt [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-12-28 11:49 [dm-crypt] TrueCrypt is discontinued - here are the alternatives Sophie Hunt
2016-12-28 16:20 ` Arno Wagner
2016-12-28 16:41   ` Sven Eschenberg
2016-12-28 19:55     ` Arno Wagner
2017-01-03 20:49       ` Laurence Darby
2017-01-04  7:08         ` Milan Broz
2017-01-04 15:31         ` Sven Eschenberg
2017-01-05 21:53           ` Laurence Darby
2017-01-03 11:20 Sophie Hunt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5320291.or_mail@ctechemail.com \
    --to=sophie.hunt@ctechemail.com \
    --cc=dm-crypt@saout.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox