From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 81EAF198005 for ; Wed, 20 Mar 2013 04:40:56 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id F0B8AE05B4; Wed, 20 Mar 2013 04:40:39 +0000 (UTC) Received: from smtpq2.gn.mail.iss.as9143.net (smtpq2.gn.mail.iss.as9143.net [212.54.34.165]) by pigeon.gentoo.org (Postfix) with ESMTP id A5471E039A for ; Wed, 20 Mar 2013 04:40:38 +0000 (UTC) Received: from [212.54.34.134] (helo=smtp3.gn.mail.iss.as9143.net) by smtpq2.gn.mail.iss.as9143.net with esmtp (Exim 4.71) (envelope-from ) id 1UIApK-0004Hs-0X for gentoo-user@lists.gentoo.org; Wed, 20 Mar 2013 05:40:38 +0100 Received: from 54698b76.cm-12-2c.dynamic.ziggo.nl ([84.105.139.118] helo=data.antarean.org) by smtp3.gn.mail.iss.as9143.net with esmtp (Exim 4.71) (envelope-from ) id 1UIApJ-0006xp-Jm for gentoo-user@lists.gentoo.org; Wed, 20 Mar 2013 05:40:38 +0100 Received: from [10.20.13.102] (unknown [10.20.13.102]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by data.antarean.org (Postfix) with ESMTPSA id 55A1B1C for ; Wed, 20 Mar 2013 05:40:15 +0100 (CET) User-Agent: K-9 Mail for Android In-Reply-To: <514939A9.3030204@orlitzky.com> References: <514925C3.8020900@gmail.com> <51492A76.4010202@iinet.net.au> <51492CE9.4030508@gmail.com> <514939A9.3030204@orlitzky.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Subject: Re: [gentoo-user] [OT] Time-lock USB stick From: "J. Roeleveld" Date: Wed, 20 Mar 2013 05:40:34 +0100 To: gentoo-user@lists.gentoo.org Message-ID: <8e117e44-3289-4339-89e8-6404b4cda277@email.android.com> Content-Transfer-Encoding: quoted-printable X-Ziggo-spambar: ---- X-Ziggo-spamscore: -4.9 X-Ziggo-spamreport: ALL_TRUSTED=-1,BAYES_00=-1.9,PROLO_TRUST_RDNS=-3,RDNS_DYNAMIC=0.982 X-Ziggo-Spam-Status: No X-Spam-Status: No X-Spam-Flag: No X-Archives-Salt: 35d5b683-dd44-470c-8207-8cc5c1952d38 X-Archives-Hash: 15bae970383170e0f722052220575599 Michael Orlitzky wrote: >-----BEGIN PGP SIGNED MESSAGE----- >Hash: SHA1 > >On 03/19/2013 11:28 PM, Michael Mol wrote: >>=20 >> Not so much. The idea would be that you could power cycle the >> device to get access to it again. The device would be read for the >> keys at system bootup, but then would shut itself off after a few >> minutes to prevent the keys from being read from disk. (There's >> still the risk of them being read from the memory of the process >> using them, but that's slightly more difficult, and security is all >> about raising the bar.) >>=20 > >Eject the USB drive after five minutes? This raises the bar >significantly, to "has tried to send the 'close CD tray' command to a >USB stick before." > >-----BEGIN PGP SIGNATURE----- >Version: GnuPG v2.0.19 (GNU/Linux) > >iQIcBAEBAgAGBQJRSTmpAAoJEBxJck0inpOiKusP/1sVI0A5hbT1pE8yRu+Ydn5W >j+O6o9j+r2Tqzkay0/tXPWs8HJlM7c8yQcaRvQoCiau2mQzitSk+nLxCPh/GLpis >2d49ihFKmVFk7qrIzMkrHoV4XRc2jVfgiEq+n8W5dYpODPCX9N4MQidgiYePnZ52 >YEtxijEkfPk73j5jPoJh6SNWtzrdLUC6DH4mmghqgmZcn4glkhWpqIU6U/tj4hJT >iN67F5g0g8YSIQNTBsTO/TLrQmrHdb/iT2v9hTxeL+Ly+xjHKJmSikP+f0rOOrQn >vXbJHGk2IAgajDHcdG3jDJvoQDgA0vl+uJ/i4tj++rwMNNXxX7MmFq9qGqGGjBp4 >nwFVJn9QGMHq2boDXISXlz+zNcjLWcaxNrXQiqSB5sqnbvjg27/NCDaQG8+ZgWzX >a/JGLqu3l7LoribH54E51PGdpKiiooDgYjgQkB9ZrSM6/X14JftqWavEALrLQXfM >ud32XTgMGiBVqyjtGQ4VDS2KtQnZAWhORMQJvOx3nwApUiXOlyX8xoyazYetnTaC >pZFgYRgmNYQodweJNrpz28EekEhwr1A/HHYhe5ANqUSO44xZBhsfEhtz0ycVd0ok >2JnCC4WwmQtqifD4S3hEsn4BN1XvxCH8YhXV6S+ApD9bo22ybZFw7f54tMSV0L/d >brkafk2u3Bhnh2yFr+6k >=3DpX91 >-----END PGP SIGNATURE----- I don't think it is possible to un-eject a usb-drive without powercycling= it. And why wait 5 minutes to eject it? Simply do that as soon as the keys ar= e read? Extra option: Stick the usbdisk driver as a module in a ramdisk and then rmmod it. Remove the module from disk And use module signing. From what I understand. The keys for that are gen= erated at compile time? And you can delete them from the kernel sources a= fter compiling. -- Joost --=20 Sent from my Android phone with K-9 Mail. Please excuse my brevity.