From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] TrueCrypt support ended -- "Not secure"
Date: Thu, 29 May 2014 16:35:10 +0200 [thread overview]
Message-ID: <20140529143510.GA6037@tansi.org> (raw)
In-Reply-To: <lm5p4u$mpl$1@ger.gmane.org>
Give it at least a few days before jumping to conclusions.
There is a number of possibilities for what happened and
what is said on the page actually being true is just one
of them.
Also note that the claims about valid signatures on the
current, crippled binaries are shaky as the keys were
apparently changed recently.
Arno
On Thu, May 29, 2014 at 00:49:01 CEST, Robert Nichols wrote:
> Sourceforge page warns against continued use, and the latest release
> does not permit creation of new volumes.
>
> http://arstechnica.com/security/2014/05/truecrypt-is-not-secure-official-sourceforge-page-abruptly-warns/
>
> http://truecrypt.sourceforge.net/
>
> --
> Bob Nichols "NOSPAM" is really part of my email address.
> Do NOT delete it.
>
> _______________________________________________
> dm-crypt mailing list
> dm-crypt@saout.de
> http://www.saout.de/mailman/listinfo/dm-crypt
--
Arno Wagner, Dr. sc. techn., Dipl. Inform., Email: arno@wagner.name
GnuPG: ID: CB5D9718 FP: 12D6 C03B 1B30 33BB 13CF B774 E35C 5FA1 CB5D 9718
----
A good decision is based on knowledge and not on numbers. - Plato
prev parent reply other threads:[~2014-05-29 14:35 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
2014-05-29 3:38 ` Chris Drake
2014-05-29 14:35 ` Arno Wagner [this message]
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=20140529143510.GA6037@tansi.org \
--to=arno@wagner.name \
--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.