All of lore.kernel.org
 help / color / mirror / Atom feed
From: "U.Mutlu" <for-gmane@mutluit.com>
To: dm-crypt@saout.de
Subject: [dm-crypt] truecrypt - what's the real story behind it?
Date: Sun, 08 Feb 2015 10:45:52 +0100	[thread overview]
Message-ID: <mb7b8h$2m5$1@ger.gmane.org> (raw)

Hi,
the cryptsetup tool supports besides plain and luks, also loopaes and truecrypt.
I now compiled truecrypt-7.1a, and it looks not bad.
I wonder why some people say truecrypt is no more secure.
Which part or method of truecrypt is allegedly broken? Can't be fixed?
And: is full truecrypt functionality integrated in cryptsetup tool? I mean the 
create-options below.

Here's a manually done "create"-session with the available options:

# truecrypt -c

Volume type:
  1) Normal
  2) Hidden
Select [1]: 1
Enter file or device path for new volume: /home/testuser/truecrypt-tests/enc.tcf
Enter volume size (sizeK/size[M]/sizeG): : 250M

Encryption algorithm:
  1) AES
  2) Serpent
  3) Twofish
  4) AES-Twofish
  5) AES-Twofish-Serpent
  6) Serpent-AES
  7) Serpent-Twofish-AES
  8) Twofish-Serpent
Select [1]: 3

Hash algorithm:
  1) RIPEMD-160
  2) SHA-512
  3) Whirlpool
Select [1]: 1

Filesystem:
  1) None
  2) FAT
  3) Linux Ext2
  4) Linux Ext3
  5) Linux Ext4
Select [2]: 3

-- 
cu
Uenal

             reply	other threads:[~2015-02-08  9:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-08  9:45 U.Mutlu [this message]
2015-02-08 10:03 ` [dm-crypt] truecrypt - what's the real story behind it? Milan Broz
2015-02-08 11:53   ` U.Mutlu
2015-02-08 12:02     ` Heinz Diehl
2015-02-08 12:09       ` Alex Elsayed
2015-02-08 12:10         ` Alex Elsayed
2015-02-09 16:16         ` Sven Eschenberg
2015-02-08 12:40       ` U.Mutlu
2015-02-09 16:12   ` Sven Eschenberg

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='mb7b8h$2m5$1@ger.gmane.org' \
    --to=for-gmane@mutluit.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.