From: Chris Drake <Tech@CryptoPhoto.com>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] TrueCrypt support ended -- "Not secure"
Date: Thu, 29 May 2014 11:07:10 +1000 [thread overview]
Message-ID: <1055768232.20140529110710@CryptoPhoto.com> (raw)
In-Reply-To: <lm5p4u$mpl$1@ger.gmane.org>
Hi Robert,
That's a hoax - their domain got hijacked.
Kind Regards,
Chris Drake
Thursday, May 29, 2014, 8:49:01 AM, you wrote:
RN> Sourceforge page warns against continued use, and the latest release does not
RN> permit creation of new volumes.
RN> http://arstechnica.com/security/2014/05/truecrypt-is-not-secure-official-sourceforge-page-abruptly-warns/
RN> http://truecrypt.sourceforge.net/
next prev parent reply other threads:[~2014-05-29 1:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-28 22:49 [dm-crypt] TrueCrypt support ended -- "Not secure" Robert Nichols
2014-05-29 1:07 ` Chris Drake [this message]
2014-05-29 2:46 ` Robert Nichols
2014-05-29 3:38 ` Chris Drake
2014-05-29 14:35 ` Arno Wagner
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=1055768232.20140529110710@CryptoPhoto.com \
--to=tech@cryptophoto.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.