From: Michael Hampicke <mh@hadt.biz>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Demise of Truecrypt - surprised I haven't seen t his discussed here yet?
Date: Mon, 02 Jun 2014 10:53:51 +0200 [thread overview]
Message-ID: <538C3B9F.10808@hadt.biz> (raw)
In-Reply-To: <538C344E.6050809@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1111 bytes --]
Am 02.06.2014 10:22, schrieb Dale:
> Volker Armin Hemmann wrote:
>> Am 01.06.2014 14:31, schrieb Tanstaafl:
>>> Wow, I've been mostly offline for a few days, and this morning when
>>> playing catch up on the news, learned that Truecrypt, one of my all
>>> time favorite apps, is no more.
>>>
>>> Some links of interest:
>>>
>>> https://www.schneier.com/blog/archives/2014/05/truecrypt_wtf.html
>>>
>>> https://news.ycombinator.com/item?id=7812133
>>>
>>> http://community.spiceworks.com/topic/505372-truecrypt-is-dead?page=1
>>>
>>>
>> well, if true: good riddance. But I suspect some hacker-y or power
>> struggle.
>>
>>
>
> I'm considering encrypting my home partition one of these days. Given
> the things that have come out in recent months, back doors and such,
> what is a good program/software/tool to use that is well . . . secure?
> Is there such a thing now?
>
Depends on your needs, for encrypting complete devices/partitions try
the kernels dm-crypt/luks module. If you just want to encrypt a
directory try encfs, and for file encryption there's openssl and gpg
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2014-06-02 8:54 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-01 12:31 [gentoo-user] Demise of Truecrypt - surprised I haven't seen t his discussed here yet? Tanstaafl
2014-06-01 17:45 ` Volker Armin Hemmann
2014-06-02 8:22 ` Dale
2014-06-02 8:53 ` Michael Hampicke [this message]
2014-06-02 9:20 ` Neil Bothwick
2014-06-02 10:24 ` Michael Hampicke
2014-06-02 11:34 ` Mark David Dumlao
2014-06-02 12:27 ` Neil Bothwick
2014-06-02 9:24 ` Volker Armin Hemmann
2014-06-02 9:34 ` Neil Bothwick
2014-06-02 9:48 ` Dale
2014-06-02 10:06 ` Alan McKinnon
2014-06-02 10:27 ` Dale
2014-06-02 10:56 ` Neil Bothwick
2014-06-02 11:04 ` Dale
2014-06-02 11:10 ` Neil Bothwick
2014-06-02 11:33 ` Dale
2014-06-02 13:23 ` J. Roeleveld
2014-06-02 11:28 ` Rich Freeman
2014-06-02 12:06 ` Dale
2014-06-02 12:28 ` Michael Hampicke
2014-06-02 12:30 ` Matti Nykyri
2014-06-02 13:27 ` Rich Freeman
2014-06-02 13:40 ` J. Roeleveld
2014-06-02 12:23 ` Matti Nykyri
2014-06-02 12:36 ` godzil
2014-06-02 12:58 ` Matti Nykyri
2014-06-02 13:29 ` godzil
2014-06-02 14:52 ` J. Roeleveld
2014-06-02 13:23 ` Matti Nykyri
2014-06-02 15:29 ` J. Roeleveld
2014-06-03 18:53 ` Matti Nykyri
2014-06-03 21:05 ` J. Roeleveld
2014-06-03 19:53 ` Matti Nykyri
2014-06-03 21:27 ` Matti Nykyri
2014-06-02 18:14 ` Volker Armin Hemmann
2014-06-02 17:14 ` Volker Armin Hemmann
2014-06-02 19:26 ` J. Roeleveld
2014-06-02 13:22 ` J. Roeleveld
2014-06-02 16:54 ` Volker Armin Hemmann
2014-06-02 10:43 ` Rich Freeman
2014-06-02 10:54 ` Neil Bothwick
2014-06-04 19:59 ` Frank Steinmetzger
2014-06-04 23:24 ` Neil Bothwick
2014-06-05 16:52 ` Frank Steinmetzger
2014-06-05 16:57 ` Rich Freeman
2014-06-02 10:22 ` Tanstaafl
2014-06-02 10:57 ` Volker Armin Hemmann
2014-06-03 7:17 ` Marc Stürmer
2014-06-03 10:00 ` Tanstaafl
2014-06-03 12:02 ` Mick
2014-06-03 19:59 ` Marc Stürmer
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=538C3B9F.10808@hadt.biz \
--to=mh@hadt.biz \
--cc=gentoo-user@lists.gentoo.org \
/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