All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Nichols <rnicholsNOSPAM@comcast.net>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] TrueCrypt support ended -- "Not secure"
Date: Wed, 28 May 2014 21:46:19 -0500	[thread overview]
Message-ID: <lm671s$tfp$1@ger.gmane.org> (raw)
In-Reply-To: <1055768232.20140529110710@CryptoPhoto.com>

On 05/28/2014 08:07 PM, Chris Drake wrote:
> 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/
>
>
>
>
> _______________________________________________
> dm-crypt mailing list
> dm-crypt@saout.de
> http://www.saout.de/mailman/listinfo/dm-crypt
>

It has been reported that the "hacked" release was certified with the
official TruCrypt signing key, and compromise of that key would be
even more damning.  Would someone who had gained access to that key
squander that power on a prank?

-- 
Bob Nichols     "NOSPAM" is really part of my email address.
                 Do NOT delete it.

  reply	other threads:[~2014-05-29  2:46 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
2014-05-29  2:46   ` Robert Nichols [this message]
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='lm671s$tfp$1@ger.gmane.org' \
    --to=rnicholsnospam@comcast.net \
    --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.