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] Proposal for support of PKCS#11 devices (SmartCards and Tokens)
Date: Thu, 2 Apr 2015 17:48:01 +0200	[thread overview]
Message-ID: <20150402154801.GA22576@tansi.org> (raw)
In-Reply-To: <F4BEB970-290A-46AB-9E79-D02DFA03F3D2@gmail.com>




On Thu, Apr 02, 2015 at 14:38:28 CEST, Nick Econopouly wrote:
> "2-factor authentication is a large field with many dysfunctional
> solutions (biometrics, for example, or numerous insecure hardware 
> tokens), and no final good solutions are in sight. Hence it is not 
> something that has a place in cryptsetup proper, beyond what is 
> already there. You can also always treat the passphrase as the secret 
> and protect that with your chosen 2-factor authentication scheme."
> 
> I've been interested in the hardware tokens you mentioned; are the yubikey
> and the upcoming nitrokey insecure?
>
> (For 2fa, I assume the gnupg features are more secure because they at
> least require a pin)
> 
> -nick

The think is that in the past most chipcards were broken, some
in ridiculously simple fashions. At the same time, people do not
realize this. I have even heard some security people call a 
smartcard a "mini-HSM". The problem is that makeing a secure token
is hard and expensive. For example, it needs always-on sensors
that can wipe it in case of attacks on the hardware. 

Sure, a hardware token of any kind usually gives you a significant 
security boost as most people chose insecure passwords, but
that is basically it. If a user uses secure passwords, 2-factor
will just annoy.

Gr"usse,
Arno


-- 
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

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

  parent reply	other threads:[~2015-04-02 15:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-02  6:18 [dm-crypt] Proposal for support of PKCS#11 devices (SmartCards and Tokens) Bill Mair
2015-04-02 10:20 ` Arno Wagner
     [not found]   ` <551D1CF9.9020502@billmairsolutions.ltd.uk>
2015-04-02 12:08     ` Arno Wagner
2015-04-02 12:38       ` Nick Econopouly
2015-04-02 12:50         ` Bill Mair
2015-04-02 15:48         ` Arno Wagner [this message]
2015-04-02 13:10       ` Bill Mair
2015-04-02 16:08         ` Arno Wagner
2015-04-02 18:11           ` Bill Mair

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=20150402154801.GA22576@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.