All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] two factor authentication with zuluCrypt
Date: Mon, 17 Oct 2011 18:47:34 +0200	[thread overview]
Message-ID: <20111017164734.GA8827@tansi.org> (raw)
In-Reply-To: <4E9C4E13.50702@redhat.com>

On Mon, Oct 17, 2011 at 05:47:31PM +0200, Milan Broz wrote:
> On 10/17/2011 04:39 PM, .. ink .. wrote:
> > Why doesnt cryptsetup support two factor authentication?
> 
> I like the Unix approach - one simple program, one function.

The thing is that you cannot do 2-factor authentication 
generically. You typically have password/passphrase as
one factor, and that can be done generically and is implemented
in cryptsetup. However the second factor is usually a token
or biometrics and there is no way to do these generically. 
They always have to be customized to the concrete solution.
While there are generic smarcard indterfaces, they are
still problematic for this use.

I think the present approach is prefectly fine. It is also easy 
to script in a concrete token or biometrics, just use a longer
passphrase and split it, as originally suggested. Or use
the library, although that does not provide a conceptyal
security increase as compared to scripting.

> cryptsetup is nothing more than low-level configuration
> for dmcrypt and on-disk metadata (key management) wrapper.
> And provides library covering that.
> 
> You can build various plugins (see e.g. how pam_mount
> or systemd uses libcryptsetup) but I would like to cryptsetup
> remains simple utility just for this exact task.
> 
> (But maybe we should add various wrappers to code tree later.)

I can see that happening, e.g. as soon as there is a stable token 
standard with working multi-vendor support. Or if, for example, 
there is a widely-adopted standard for a smartphone to prove its
presence (misusing a phone as a token).

Arno
-- 
Arno Wagner, Dr. sc. techn., Dipl. Inform., CISSP -- Email: arno@wagner.name 
GnuPG:  ID: 1E25338F  FP: 0C30 5782 9D93 F785 E79C  0296 797F 6B50 1E25 338F
----
Cuddly UI's are the manifestation of wishful thinking. -- Dylan Evans

If it's in the news, don't worry about it.  The very definition of 
"news" is "something that hardly ever happens." -- Bruce Schneier 

  reply	other threads:[~2011-10-17 16:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-17  3:44 [dm-crypt] two factor authentication with zuluCrypt .. ink ..
2011-10-17  4:36 ` Arno Wagner
2011-10-17  7:50 ` Milan Broz
2011-10-17 14:39   ` .. ink ..
2011-10-17 15:47     ` Milan Broz
2011-10-17 16:47       ` Arno Wagner [this message]
2011-10-17 16:54         ` .. ink ..
2011-10-17 17:14       ` .. ink ..

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=20111017164734.GA8827@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.