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 PYaQUnUT5BNQ for ; Mon, 20 May 2013 10:41:57 +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 ; Mon, 20 May 2013 10:41:56 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by zimbra.kress-net.com (Postfix) with ESMTP id 8015F1B6E4B for ; Mon, 20 May 2013 10:41:56 +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 INAEOWfuLsCK for ; Mon, 20 May 2013 10:41: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 84C441B6B06 for ; Mon, 20 May 2013 10:41:54 +0200 (CEST) Date: Mon, 20 May 2013 10:41:54 +0200 (CEST) From: Krzysztof Rutecki Message-ID: <32903421.12967.1369039314290.JavaMail.root@zimbra.kress-net.com> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_12966_28585214.1369039314289" Subject: Re: [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_12966_28585214.1369039314289 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Hi The reason I`m doing it is to have a solution where passphrase never leave host or better, never leave cryptsetup tool. My company is working on NAS solutions with maximum security lever. Imagine you have servers with 24 bays and few root administrators . What is a chance of disk leakage e.g. where drive is being replace for new one under warranty condition? With MooseFS (btw an excellent tool), LUKS, passprase on crypto card/token and cryptsetup supporting pkcs11 you can format disk using token as storage and two-factor authentication device. Am I thinking correctly? For backup you can add second key (the same way or classic, just for backup) and sys admins never see key(s). Using now available methods (gnupgp or pkcs11-data) you can easlly modify scripts to dump passphrase or keyfile. I want to minimize it. Of course I`m not expecting that maintainers of official cryptsetup will integrate it. Maybe some day. Those I was thinking about GitHub. I can make a fork of official cryptsetup, then fork from it to my version. Community can see what cams from and how. Anyway lots of job to be done before code will be ready to place on public repo.It will be, maybe in next 2-3 weeks. If you are interested, good and help full source of smartcards is SmartCardsFocus . Thanks guys for help with ACOS5-64 cards! RSA4096 is finally working well under PKCS#11. Good job. Regards Krzysztof Rutecki ------=_Part_12966_28585214.1369039314289 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

The reason I`m doing it is to have a solution where pa= ssphrase never leave host or better, never leave cryptsetup tool. My company is = working on NAS solutions with maximum
security lever. 

Imagine you have servers = with 24 bays and few root administrators. What is a chance of disk lea= kage e.g. where drive is being replace for new one under warranty
condition? W= ith MooseFS (btw an excellent tool), LUKS, passprase on crypto card/token a= nd cryptsetup supporting pkcs11 you can format disk using token as storage = and two-factor
authentication device. Am I thinking correctly? For backup you = can add second key (the same way or classic, just for backup) and sys admin= s never see key(s). Using now available
methods (gnupgp or pkcs11-data) you ca= n easlly modify scripts to dump passphrase or keyfile. I want to minimize i= t.
=
fork from it to my ve= rsion. Community can see what cams from and how. 

<= font face=3D"times new roman, new york, times, serif">Anyway lots of job to= be done before code will be ready to place on public repo.It will be, mayb= e in next 2-3 weeks. If you are interested, good and help full source of sm= artcards is 
SmartCardsFocus. Thanks guys for help with ACOS5-6= 4 cards! RSA4096 is finally working well under PKCS#11. Good job.

RegardsKrzysztof Rutecki


------=_Part_12966_28585214.1369039314289--