Return-Path: Received: from mail.saout.de ([127.0.0.1]) by localhost (mail.saout.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GNXulAqtxnbS for ; Sun, 19 May 2013 21:10:45 +0200 (CEST) Received: from zimbra.kress-net.com (88-199-169-71.tktelekom.pl [88.199.169.71]) by mail.saout.de (Postfix) with ESMTP for ; Sun, 19 May 2013 21:10:45 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by zimbra.kress-net.com (Postfix) with ESMTP id EDA551B6D21 for ; Sun, 19 May 2013 21:02:55 +0200 (CEST) Received: from zimbra.kress-net.com ([127.0.0.1]) by localhost (zimbra.kress-net.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qQ-iLmaAVHXq for ; Sun, 19 May 2013 21:02:54 +0200 (CEST) Received: from zimbra.kress-net.com (zimbra.kress-net.com [88.199.169.71]) by zimbra.kress-net.com (Postfix) with ESMTP id 68FFF1B6D0C for ; Sun, 19 May 2013 21:02:54 +0200 (CEST) Date: Sun, 19 May 2013 21:02:53 +0200 (CEST) From: Krzysztof Rutecki Message-ID: <28381984.12246.1368990173659.JavaMail.root@zimbra.kress-net.com> In-Reply-To: <13728200.12238.1368989649950.JavaMail.root@zimbra.kress-net.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_12245_21052318.1368990173658" Subject: [dm-crypt] cryptsetup with native PKCS#11 support List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: dm-crypt@saout.de ------=_Part_12245_21052318.1368990173658 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Hi guys I`m new here. The purpose of this email is PKCS#11 support in cryptsetup I`m working on. In short: I need to encrypt disk with LUKS and store key on PKCS#11 compatible device. I now there is a lot of example how to do this using gnupgp or openssl. The goal is to have key only on token, retrieve upon 'luksOpen' operation based on PIN only. What is working now is: - key generation (as pass-phrase ) using smartcard/token hardware RNG - encrypt a backup of the key using certificate from token upon 'luksFormat' - decrypt key from file using privatekey from token upon 'luksOpen' - all above extansions are build in into cryptsetup command (few new switches) - dependencies are minimal - only pkcs11 library file for token is required (no libp11 or pkcs11-helper) Later I will add storage of keyfile on token as data object. As this job is for private use only, the code is a little messy and unclean. So I want to open a discussion : is a native PKCS#11 support in cryptsetup needed? If yes, please give me any possible hint can help. Or suggestion what or how to implement to make it secure. Regards Krzysztof Rutecki ------=_Part_12245_21052318.1368990173658 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable <= div style=3D'font-family: times new roman,new york,times,serif; font-size: = 12pt; color: #000000'>Hi guys

I`m new here. The purpose of this email is PKCS#11 sup= port in cryptsetup I`m working on.

In short: I need to encrypt disk with LUKS and = store key on PKCS#11 compatible device. I now
there is a lot of example how = to do this using gnupgp or openssl.  The goal is to have key only on t= oken,
retrieve upon 'luksOpen' operation based on PIN only.
<= font face=3D"times new roman, new york, times, serif">
What is working now= is:
- = encrypt a backup of the key using certificate from token upon 'luksFormat'<= /font>
- d= ecrypt key from file using privatekey from token upon 'luksOpen'
- all above e= xtansions are build in into cryptsetup command (few new switches)
- depen= dencies are minimal - only pkcs11 library file for token is required (no li= bp11 or pkcs11-helper)

Later I will add storage of keyfile on token as data = object.

As this job is for private use only, the code is a little messy=  and unclean. 

So I want to open a discussion: is a native PK= CS#11 support in cryptsetup needed? If yes, please give me any
=
possible hint c= an help. Or suggestion what or how to implement to make it secure.

RegardsKrzysztof Rutecki
------=_Part_12245_21052318.1368990173658--