From linux-crypto-bounce@nl.linux.org Thu Jul 01 04:05:16 2004 Received: from localhost ([127.0.0.1] helo=humbolt) by humbolt.nl.linux.org with esmtp (Exim 4.22) id 1Bfqv3-00049g-8G; Thu, 01 Jul 2004 04:03:21 +0200 Received: with ECARTIS (v1.0.0; list linux-crypto); Thu, 01 Jul 2004 04:03:12 +0200 (CEST) Received: from imo-d23.mx.aol.com ([205.188.139.137]) by humbolt.nl.linux.org with esmtp (Exim 4.22) id 1Bfqui-00048U-RT for linux-crypto@nl.linux.org; Thu, 01 Jul 2004 04:03:00 +0200 Received: from Jamesmclalin@aol.com by imo-d23.mx.aol.com (mail_out_v37_r2.6.) id o.15.2cbd7680 (3940) for ; Wed, 30 Jun 2004 22:02:43 -0400 (EDT) From: Jamesmclalin@aol.com Message-ID: <15.2cbd7680.2e14cac3@aol.com> Date: Wed, 30 Jun 2004 22:02:43 EDT Subject: (no subject) To: linux-crypto@nl.linux.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="-----------------------------1088647363" X-Mailer: 9.0 for Windows sub 5112 Received-SPF: X-Spam-Status: No, hits=4.3 required=5.0 tests=BAYES_90,HTML_60_70,NO_REAL_NAME,RCVD_IN_ORBS version=2.55 X-Spam-Level: **** X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) X-ecartis-version: Ecartis v1.0.0 Sender: linux-crypto-bounce@nl.linux.org Errors-to: linux-crypto-bounce@nl.linux.org X-original-sender: Jamesmclalin@aol.com Precedence: bulk List-help: List-unsubscribe: List-software: Ecartis version 1.0.0 List-Id: X-List-ID: List-subscribe: List-owner: List-post: List-archive: X-list: linux-crypto -------------------------------1088647363 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit i need my password and the order code for my ebay account -------------------------------1088647363 Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable i need my password and the order code for my ebay account -------------------------------1088647363-- - Linux-crypto: cryptography in and on the Linux system Archive: http://mail.nl.linux.org/linux-crypto/ From linux-crypto-bounce@nl.linux.org Thu Jul 01 06:10:55 2004 Received: from localhost ([127.0.0.1] helo=humbolt) by humbolt.nl.linux.org with esmtp (Exim 4.22) id 1Bfssq-00048O-Lp; Thu, 01 Jul 2004 06:09:12 +0200 Received: with ECARTIS (v1.0.0; list linux-crypto); Thu, 01 Jul 2004 06:09:05 +0200 (CEST) Received: from [211.213.121.237] (helo=adis.co.nz) by humbolt.nl.linux.org with smtp (Exim 4.22) id 1Bfss8-000439-3S; Thu, 01 Jul 2004 06:08:28 +0200 Received: from 3.63.220.133 by smtp.space.gc.ca; Thu, 01 Jul 2004 04:08:29 +0000 Message-ID: <060201c45f21$228433e5$5508eb8a@adis.co.nz> From: "Devon Hudson" To: linux-crypto@nl.linux.org, linux-crypto-request@nl.linux.org, linux-crypto-bounce@nl.linux.org, linux-cluster@nl.linux.org Subject: $12882 Date: Wed, 30 Jun 2004 23:08:28 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit Received-SPF: X-Spam-Status: No, hits=2.8 required=5.0 tests=AWL,BAD_CREDIT,RCVD_IN_ORBS,RCVD_IN_RFCI,SUBJ_DOLLARS version=2.55 X-Spam-Level: ** X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) X-ecartis-version: Ecartis v1.0.0 Sender: linux-crypto-bounce@nl.linux.org Errors-to: linux-crypto-bounce@nl.linux.org X-original-sender: dhudson_cg@space.gc.ca Precedence: bulk List-help: List-unsubscribe: List-software: Ecartis version 1.0.0 List-Id: X-List-ID: List-subscribe: List-owner: List-post: List-archive: X-list: linux-crypto Hello, I sent you an email a few days ago, because you now qualify for a new mortgage. You could get $300,000 for as little as $700 a month! Bad credit is no problem, you can pull cash out or refinance. Please click on this link: http://www.fast-loanz.com/e4/e7.php?weo=71 Best Regards, Steve Morris ---- system information ---- comment inherent colors years based display part [Web working implemented imply runtime current work stroke-radical implementations behaviors name for might mistake absence believes similar-looking - Linux-crypto: cryptography in and on the Linux system Archive: http://mail.nl.linux.org/linux-crypto/ From linux-crypto-bounce@nl.linux.org Thu Jul 01 17:28:25 2004 Received: from localhost ([127.0.0.1] helo=humbolt) by humbolt.nl.linux.org with esmtp (Exim 4.22) id 1Bg3SC-0001Vd-Dj; Thu, 01 Jul 2004 17:26:24 +0200 Received: with ECARTIS (v1.0.0; list linux-crypto); Thu, 01 Jul 2004 17:26:17 +0200 (CEST) Received: from tarjoilu.luukku.com ([194.215.205.232]) by humbolt.nl.linux.org with esmtp (Exim 4.22) id 1Bg3Rk-0001Uj-2s for linux-crypto@nl.linux.org; Thu, 01 Jul 2004 17:25:56 +0200 Received: from localhost (mta1-o.i.luukku.com [10.0.1.112]) by mta1-o.i.luukku.com (Postfix) with ESMTP id 95BA1808A8; Thu, 1 Jul 2004 18:25:53 +0300 (EEST) Received: from users.sourceforge.net (2eeb.yhteys.mtv3.fi [62.236.235.46]) by tarjoilu.luukku.com (Postfix) with ESMTP id 902253AE286; Thu, 1 Jul 2004 18:25:52 +0300 (EEST) Message-ID: <40E42D47.4C3CCDBE@users.sourceforge.net> Date: Thu, 01 Jul 2004 18:27:03 +0300 From: Jari Ruusu X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.4.22aa1r7 i686) X-Accept-Language: en MIME-Version: 1.0 To: Doug Campbell Cc: linux-crypto@nl.linux.org Subject: Re: loop-AES: Boot from CD-ROM + encrypted root partition References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Received-SPF: X-Spam-Status: No, hits=-5.9 required=5.0 tests=AWL,BAYES_10,EMAIL_ATTRIBUTION,QUOTED_EMAIL_TEXT, RCVD_IN_ORBS,REFERENCES,REPLY_WITH_QUOTES, USER_AGENT_MOZILLA_XM version=2.55 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) X-ecartis-version: Ecartis v1.0.0 Sender: linux-crypto-bounce@nl.linux.org Errors-to: linux-crypto-bounce@nl.linux.org X-original-sender: jariruusu@users.sourceforge.net Precedence: bulk List-help: List-unsubscribe: List-software: Ecartis version 1.0.0 List-Id: X-List-ID: List-subscribe: List-owner: List-post: List-archive: X-list: linux-crypto Doug Campbell wrote: > I am using GRUB, do I just do something like the following? > > boot=/dev/loop7 > disk=/dev/loop7 > bios=0x00 > sectors=36 > heads=2 > cylinders=80 > geometric > compact > read-only > prompt > timeout=30 > vga=normal > backup=/dev/null > install=text > map=/mnt/map > title Linux using loop-AES > root (hd0,0) > kernel /vmlinuz ro root=/dev/ram0 init=/linuxrc rootfstype=minix > initrd /initrd.gz No. That is mixture of lilo config and grub config, and will work with neither lilo nor grub. > Question 2: In Step 12 it says: > > 12) Build new /boot/initrd.gz > > ./build-initrd.sh /boot/initrd.conf > > but I noticed that not all of the configuration options that I initially > changed in build-initrd.sh are in the initrd.conf file in Step 10a. Do I > add these to that file or will it use what I have set in the buid-initrd.sh > file as defaults and only change the options that I have specifically set in > initrd.conf? Values set in build-initrd.sh are defaults. Additional configuration file /boot/initrd.conf can override any defaults it wants. Here I suggest that you put all your local changes to /boot/initrd.conf and use unmodified build-initrd.sh from loop-AES tarball. > Question 3: In Step 20 it says: > > 20) Clean up and reboot your computer. The 'dd' command attempts to > overwrite gpg encrypted root partition key file and 'mkswap' command > restores "temporary file system on swap" /dev/hda3 back to swap usage. > > dd if=/dev/zero of=/mnt/rootkey.gpg bs=64k count=1 conv=notrunc > umount /mnt > sync > mkswap /dev/hda3 > sync > reboot > > Am I rebooting the computer with my rescue disk again? > > If so, after doing so, do I need to first mount /dev/hda3 again? The dd > command above seems to be trying to overwrite a file on a filesystem that > isn't mounted. But maybe I am missing something here? > > If not, what am I rebooting the computer with? The boot CD that I just > made? You don't need to do any of above. If your root partition is already encrypted and you want to create CD-ROM that boots to your existing encrypted root partition, then only these steps are needed: - step 7 - copy rootkey.gpg to /boot/iso/rootkey.gpg - steps 10a to 13e (Above step numbers refer to loop-AES-v2.1b README Example 6, and may be different on newer or older loop-AES versions) > Question 4: Do I need the /dev/hda1 or /boot parition after I finish? If > so, I didn't seem to encrypt it yet so can I encrypt it in the same way that > I did for /dev/hda2, the root partition? Separate /boot partition is not needed on CD-ROM boot, but some tools still want to find files from /boot directory. Following "umount /boot" might not succeed because there may already be processes with open files in /boot partition. To find out which processes you need to kill before /boot can be unmounted, use this command: lsof | grep /boot You can copy those files to root partition, like this: umount /boot mkdir /boot-old mount -t ext2 /dev/hda1 /boot-old cp -dpR /boot-old/* /boot umount /boot-old rmdir /boot-old And then remove /dev/hda1 mount line from /etc/fstab file. After that /dev/hda1 is free unused partition. -- Jari Ruusu 1024R/3A220F51 5B 4B F9 BB D3 3F 52 E9 DB 1D EB E3 24 0E A9 DD - Linux-crypto: cryptography in and on the Linux system Archive: http://mail.nl.linux.org/linux-crypto/ From linux-crypto-bounce@nl.linux.org Thu Jul 01 22:12:32 2004 Received: from localhost ([127.0.0.1] helo=humbolt) by humbolt.nl.linux.org with esmtp (Exim 4.22) id 1Bg7tU-0005vH-Jy; Thu, 01 Jul 2004 22:10:52 +0200 Received: with ECARTIS (v1.0.0; list linux-crypto); Thu, 01 Jul 2004 22:10:45 +0200 (CEST) Received: from anchor-post-32.mail.demon.net ([194.217.242.90]) by humbolt.nl.linux.org with esmtp (Exim 4.22) id 1Bg7tC-0005uH-BN for linux-crypto@nl.linux.org; Thu, 01 Jul 2004 22:10:34 +0200 Received: from black-sun.demon.co.uk ([212.228.147.62] helo=nova) by anchor-post-32.mail.demon.net with esmtp (Exim 3.35 #1) id 1Bg7t9-000Iu8-0W; Thu, 01 Jul 2004 21:10:31 +0100 Received: from paul by nova with local id 1BfxEc-0000p6-64 ; Thu, 01 Jul 2004 09:47:58 +0100 Date: Thu, 1 Jul 2004 09:47:48 +0100 From: Paul Walker To: Jamesmclalin@aol.com Cc: linux-crypto@nl.linux.org Subject: Re: (no subject) Message-ID: <20040701084747.GY3415@black-sun.demon.co.uk> References: <15.2cbd7680.2e14cac3@aol.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <15.2cbd7680.2e14cac3@aol.com> User-Agent: Mutt/1.5.5.1+cvs20040105i Received-SPF: X-Spam-Status: No, hits=-9.0 required=5.0 tests=BAYES_01,EMAIL_ATTRIBUTION,IN_REP_TO,RCVD_IN_ORBS, REFERENCES,REPLY_WITH_QUOTES,USER_AGENT_MUTT autolearn=ham version=2.55 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) X-ecartis-version: Ecartis v1.0.0 Sender: linux-crypto-bounce@nl.linux.org Errors-to: linux-crypto-bounce@nl.linux.org X-original-sender: paul@black-sun.demon.co.uk Precedence: bulk List-help: List-unsubscribe: List-software: Ecartis version 1.0.0 List-Id: X-List-ID: List-subscribe: List-owner: List-post: List-archive: X-list: linux-crypto On Wed, Jun 30, 2004 at 10:02:43PM -0400, Jamesmclalin@aol.com wrote: > i need my password and the order code for my ebay account Why are you asking us? This list deals with cryptography for Linux. -- Paul VBScript is designed to be a secure programming environment. It lacks various commands that can be potentially damaging if used in a malicious manner. This added security is critical in enterprise solutions. -- support.microsoft.com - Linux-crypto: cryptography in and on the Linux system Archive: http://mail.nl.linux.org/linux-crypto/ From linux-crypto-bounce@nl.linux.org Sat Jul 03 01:27:34 2004 Received: from localhost ([127.0.0.1] helo=humbolt) by humbolt.nl.linux.org with esmtp (Exim 4.22) id 1BgXPW-00081M-Av; Sat, 03 Jul 2004 01:25:38 +0200 Received: with ECARTIS (v1.0.0; list linux-crypto); Sat, 03 Jul 2004 01:25:31 +0200 (CEST) Received: from lakermmtao05.cox.net ([68.230.240.34]) by humbolt.nl.linux.org with esmtp (Exim 4.22) id 1BgXP1-0007xt-VZ for linux-crypto@nl.linux.org; Sat, 03 Jul 2004 01:25:08 +0200 Received: from [192.168.100.23] (really [68.109.204.226]) by lakermmtao05.cox.net (InterMail vM.6.01.03.02 201-2131-111-104-20040324) with ESMTP id <20040702232453.IMEA5935.lakermmtao05.cox.net@[192.168.100.23]> for ; Fri, 2 Jul 2004 19:24:53 -0400 Mime-Version: 1.0 (Apple Message framework v618) To: linux-crypto@nl.linux.org Message-Id: <0439D1AE-CC7F-11D8-80B0-0003939F4092@case.edu> Content-Type: multipart/alternative; boundary=Apple-Mail-2-981825127 From: John Poirier Subject: Loop-AES Date: Fri, 2 Jul 2004 19:24:51 -0400 X-Mailer: Apple Mail (2.618) Received-SPF: X-Spam-Status: No, hits=-4.6 required=5.0 tests=BAYES_10,RCVD_IN_ORBS,USER_AGENT_APPLEMAIL version=2.55 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) X-ecartis-version: Ecartis v1.0.0 Sender: linux-crypto-bounce@nl.linux.org Errors-to: linux-crypto-bounce@nl.linux.org X-original-sender: jpoirier@case.edu Precedence: bulk List-help: List-unsubscribe: List-software: Ecartis version 1.0.0 List-Id: X-List-ID: List-subscribe: List-owner: List-post: List-archive: X-list: linux-crypto --Apple-Mail-2-981825127 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed I made encrypted a pair of disks using loop-AES on Debian Woody. I recently formatted my system disk to Gentoo. I saved the encryption keys for the other disk. The script I had written called for this: losetup -e aes -k 128 -p 0 /dev/loop0 /dev/hde > /keyfile In other words, create a loopback device based on this hard disk and unencrypt it using the AES cipher and the contents of "keyfile" which is a 128 bit key. So what I did after I installed Gentoo was download the freshest util-linux and aes-loop. I patched util-linux and compiled with no problem and I was able to make and install loop.ko with no problem as well. I compiled my kernel without loopback support as called for by install docs, and loaded loop.ko using modprobe loop modprobe -l verifies that it is loaded. So far so good. The problem is that this version of losetup no longer takes the -k option and I can't remember what version I was using before. I also can't remember if I used patched util-linux or something else. Okay, so i changed "aes" to "aes-128". Now I enter the command: losetup -e aes-128 -p 0 /dev/loop0 /dev/hde > /keyfile I get no errors, but when I try to mount loop0 I get told that it can't find a filesystem on the device. Is this a problem with the "offset"? Why have the parameters of this program changed? I'm not sure what's going on here. In fact, I don't even really know if it is the kernel, the binary or my configuration that is screwing things up for me and don't know how to tell. What I am actually trying to head towards here eventually is accessing these drives using dm-crypt. Are these even compatible? John --Apple-Mail-2-981825127 Content-Transfer-Encoding: 7bit Content-Type: text/enriched; charset=US-ASCII VerdanaI made encrypted a pair of disks using loop-AES on Debian Woody. I recently formatted my system disk to Gentoo. I saved the encryption keys for the other disk. The script I had written called for this: losetup -e aes -k 128 -p 0 /dev/loop0 /dev/hde > /keyfile In other words, create a loopback device based on this hard disk and unencrypt it using the AES cipher and the contents of "keyfile" which is a 128 bit key. So what I did after I installed Gentoo was download the freshest util-linux and aes-loop. I patched util-linux and compiled with no problem and I was able to make and install loop.ko with no problem as well. I compiled my kernel without loopback support as called for by install docs, and loaded loop.ko using modprobe loop modprobe -l verifies that it is loaded. So far so good. The problem is that this version of losetup no longer takes the -k option and I can't remember what version I was using before. I also can't remember if I used patched util-linux or something else. Okay, so i changed "aes" to "aes-128". Now I enter the command: losetup -e aes-128 -p 0 /dev/loop0 /dev/hde > /keyfile I get no errors, but when I try to mount loop0 I get told that it can't find a filesystem on the device. Is this a problem with the "offset"? Why have the parameters of this program changed? I'm not sure what's going on here. In fact, I don't even really know if it is the kernel, the binary or my configuration that is screwing things up for me and don't know how to tell. What I am actually trying to head towards here eventually is accessing these drives using dm-crypt. Are these even compatible? John --Apple-Mail-2-981825127-- - Linux-crypto: cryptography in and on the Linux system Archive: http://mail.nl.linux.org/linux-crypto/ From linux-crypto-bounce@nl.linux.org Sat Jul 03 12:02:24 2004 Received: from localhost ([127.0.0.1] helo=humbolt) by humbolt.nl.linux.org with esmtp (Exim 4.22) id 1BghKG-0003vE-DB; Sat, 03 Jul 2004 12:00:52 +0200 Received: with ECARTIS (v1.0.0; list linux-crypto); Sat, 03 Jul 2004 12:00:45 +0200 (CEST) Received: from lsanca1-ar53-4-46-071-077.lsanca1.dsl-verizon.net ([4.46.71.77] helo=krautzer.at) by humbolt.nl.linux.org with smtp (Exim 4.22) id 1BghJN-0003pl-W8; Sat, 03 Jul 2004 11:59:58 +0200 Received: from 52.101.22.196 by smtp.mandrake.ca; Sat, 03 Jul 2004 09:58:41 +0000 Message-ID: <134001c460e4$f033bcbc$5d24d13f@krautzer.at> From: "Marsha Ewing" To: linux-crypto@nl.linux.org, linux-crypto-request@nl.linux.org, linux-crypto-bounce@nl.linux.org, linux-cluster@nl.linux.org Subject: $22331 Date: Sat, 03 Jul 2004 06:58:27 -0300 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit Received-SPF: X-Spam-Status: No, hits=3.6 required=5.0 tests=BAD_CREDIT,RCVD_IN_NJABL,RCVD_IN_ORBS,RCVD_IN_RFCI, SUBJ_DOLLARS version=2.55 X-Spam-Level: *** X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) X-ecartis-version: Ecartis v1.0.0 Sender: linux-crypto-bounce@nl.linux.org Errors-to: linux-crypto-bounce@nl.linux.org X-original-sender: marsha_ewinghn@mandrake.ca Precedence: bulk List-help: List-unsubscribe: List-software: Ecartis version 1.0.0 List-Id: X-List-ID: List-subscribe: List-owner: List-post: List-archive: X-list: linux-crypto Hi, I sent you an email a few days ago, because you now qualify for a new mortgage. You could get $300,000 for as little as $700 a month! Bad credit is no problem, you can pull cash out or refinance. Please click on this link: http://www.yourloanz.com/s6/jwex.php?bks=71 Best Regards, Steve Morris ---- system information ---- Since form standard distinct sends preferences specifics HTTP mistake perform fallback available Internet inappropriate cannot considered adapted expected impossible non-Java implement C: resources lives - Linux-crypto: cryptography in and on the Linux system Archive: http://mail.nl.linux.org/linux-crypto/ From linux-crypto-bounce@nl.linux.org Sat Jul 03 13:23:16 2004 Received: from localhost ([127.0.0.1] helo=humbolt) by humbolt.nl.linux.org with esmtp (Exim 4.22) id 1BgiaL-0001NC-Og; Sat, 03 Jul 2004 13:21:33 +0200 Received: with ECARTIS (v1.0.0; list linux-crypto); Sat, 03 Jul 2004 13:21:26 +0200 (CEST) Received: from mato.luukku.com ([193.209.83.251]) by humbolt.nl.linux.org with esmtp (Exim 4.22) id 1Bgia1-0001MQ-D7 for linux-crypto@nl.linux.org; Sat, 03 Jul 2004 13:21:13 +0200 Received: from localhost (mta3-o.i.luukku.com [10.0.1.132]) by mta3-o.i.luukku.com (Postfix) with ESMTP id E140CFFBBD; Sat, 3 Jul 2004 14:20:58 +0300 (EEST) Received: from users.sourceforge.net (f711.yhteys.mtv3.fi [62.237.17.247]) by mato.luukku.com (Postfix) with ESMTP id 1525A22EE89; Sat, 3 Jul 2004 14:20:57 +0300 (EEST) Message-ID: <40E696DA.E68E8DCD@users.sourceforge.net> Date: Sat, 03 Jul 2004 14:22:02 +0300 From: Jari Ruusu X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.4.22aa1r7 i686) X-Accept-Language: en MIME-Version: 1.0 To: John Poirier Cc: linux-crypto@nl.linux.org Subject: Re: Loop-AES References: <0439D1AE-CC7F-11D8-80B0-0003939F4092@case.edu> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Received-SPF: X-Spam-Status: No, hits=-5.4 required=5.0 tests=AWL,BAYES_01,EMAIL_ATTRIBUTION,QUOTED_EMAIL_TEXT, RCVD_IN_ORBS,REFERENCES,REPLY_WITH_QUOTES, USER_AGENT_MOZILLA_XM version=2.55 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) X-ecartis-version: Ecartis v1.0.0 Sender: linux-crypto-bounce@nl.linux.org Errors-to: linux-crypto-bounce@nl.linux.org X-original-sender: jariruusu@users.sourceforge.net Precedence: bulk List-help: List-unsubscribe: List-software: Ecartis version 1.0.0 List-Id: X-List-ID: List-subscribe: List-owner: List-post: List-archive: X-list: linux-crypto John Poirier wrote: > I made encrypted a pair of disks using loop-AES on Debian Woody. I=20 > recently formatted my system disk to Gentoo. I saved the encryption=20 > keys for the other disk. The script I had written called for this: >=20 > losetup -e aes -k 128 -p 0 /dev/loop0 /dev/hde > /keyfile >=20 > In other words, create a loopback device based on this hard disk and=20 > unencrypt it using the AES cipher and the contents of "keyfile" which=20 > is a 128 bit key. >=20 > So what I did after I installed Gentoo was download the freshest=20 > util-linux and aes-loop. I patched util-linux and compiled with no=20 > problem and I was able to make and install loop.ko with no problem as=20 > well. I compiled my kernel without loopback support as called for by=20 > install docs, and loaded loop.ko using >=20 > modprobe loop >=20 > modprobe -l verifies that it is loaded. >=20 > So far so good. The problem is that this version of losetup no longer=20 > takes the -k option and I can't remember what version I was using=20 > before. I also can't remember if I used patched util-linux or something= =20 > else. Okay, so i changed "aes" to "aes-128". Now I enter the command: >=20 > losetup -e aes-128 -p 0 /dev/loop0 /dev/hde > /keyfile >=20 > I get no errors, but when I try to mount loop0 I get told that it=20 > can't find a filesystem on the device. Is this a problem with the=20 > "offset"? Why have the parameters of this program changed? I'm not sure= =20 > what's going on here. In fact, I don't even really know if it is the=20 > kernel, the binary or my configuration that is screwing things up for=20 > me and don't know how to tell. losetup -e aes128 -p 0 -H rmd160 /dev/loop0 /dev/hde < /keyfile ^^^^^^^^^ ^ Above syntax uses single-key mode, which has been broken, and as such is not recommended. > What I am actually trying to head towards here eventually is accessing=20 > these drives using dm-crypt. Are these even compatible? dm-crypt is cryptoloop compatible. Current versions=A0of dm-crypt and cryptoloop are both broken and backdoored, and as such useless for securi= fty needs. --=20 Jari Ruusu 1024R/3A220F51 5B 4B F9 BB D3 3F 52 E9 DB 1D EB E3 24 0E A9 = DD - Linux-crypto: cryptography in and on the Linux system Archive: http://mail.nl.linux.org/linux-crypto/ From linux-crypto-bounce@nl.linux.org Mon Jul 05 11:00:43 2004 Received: from localhost ([127.0.0.1] helo=humbolt) by humbolt.nl.linux.org with esmtp (Exim 4.22) id 1BhPJD-0008OP-V8; Mon, 05 Jul 2004 10:58:44 +0200 Received: with ECARTIS (v1.0.0; list linux-crypto); Mon, 05 Jul 2004 10:58:36 +0200 (CEST) Received: from jrac.mailbox.co.uk ([195.82.105.10] helo=tomato.tritontek.com) by humbolt.nl.linux.org with esmtp (Exim 4.22) id 1BhPIy-0008O2-Bd for linux-crypto@nl.linux.org; Mon, 05 Jul 2004 10:58:28 +0200 Received: from freedomrecruit.com by tritontek.com (MDaemon.PRO.v7.1.0.R) with ESMTP id md50000089253.msg for ; Mon, 05 Jul 2004 10:13:23 +0100 Received: from freedomrecruit.com [192.168.1.11] by freedomrecruit.com [192.168.1.11] (with RAW) (MDaemon.PRO.v6.8.4.R) for ; Mon, 05 Jul 2004 10:16:05 +0100 Date: Mon, 05 Jul 2004 10:16:05 +0100 From: Postmaster@freedomrecruit.com Reply-To: Postmaster@freedomrecruit.com Subject: MDaemon Notification -- Attachment Removed To: linux-crypto@nl.linux.org Message-ID: Mime-Version: 1.0 X-Actual-From: Postmaster@freedomrecruit.com Content-Type: text/plain; charset=US-ASCII X-Authenticated-Sender: freedomrecruit@tritontek.com X-Spam-Processed: tritontek.com, Mon, 05 Jul 2004 10:13:23 +0100 (not processed: message from trusted or authenticated source) X-MDRemoteIP: 217.206.196.228 X-Return-Path: X-MDaemon-Deliver-To: linux-crypto@nl.linux.org Received-SPF: X-Spam-Status: No, hits=1.2 required=5.0 tests=NO_REAL_NAME,RCVD_IN_ORBS version=2.55 X-Spam-Level: * X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) X-ecartis-version: Ecartis v1.0.0 Sender: linux-crypto-bounce@nl.linux.org Errors-to: linux-crypto-bounce@nl.linux.org X-original-sender: Postmaster@freedomrecruit.com Precedence: bulk List-help: List-unsubscribe: List-software: Ecartis version 1.0.0 List-Id: X-List-ID: List-subscribe: List-owner: List-post: List-archive: X-list: linux-crypto Your recent message to this server regarding `Document` was not delivered. The attached document is of a file type we do not allow on this server. The message and attachment are automatically deleted. The message contained: >From : linux-crypto@nl.linux.org To : mdaemon@freedomrecruit.com Subject : Document Message-ID: Attachment(s) removed: ----------------------------------------- Notice.zip - Linux-crypto: cryptography in and on the Linux system Archive: http://mail.nl.linux.org/linux-crypto/ From linux-crypto-bounce@nl.linux.org Mon Jul 05 16:57:20 2004 Received: from localhost ([127.0.0.1] helo=humbolt) by humbolt.nl.linux.org with esmtp (Exim 4.22) id 1BhUsJ-0000Mv-Hf; Mon, 05 Jul 2004 16:55:19 +0200 Received: with ECARTIS (v1.0.0; list linux-crypto); Mon, 05 Jul 2004 16:55:12 +0200 (CEST) Received: from smtp2.libero.it ([193.70.192.52]) by humbolt.nl.linux.org with esmtp (Exim 4.22) id 1BhUs0-0000L4-24; Mon, 05 Jul 2004 16:55:00 +0200 Received: from localhost (172.16.1.84) by smtp2.libero.it (7.0.027-DD01) id 40C73476005B8095; Mon, 5 Jul 2004 16:49:25 +0200 Received: from libero.it (172.16.1.111) by smtp0.libero.it (7.0.027-DD01) id 40C733600037794E; Mon, 5 Jul 2004 16:49:11 +0200 Date: Mon, 5 Jul 2004 16:49:10 +0200 Message-Id: Subject: URGENT BUISNESS PROPOSAL MIME-Version: 1.0 X-Sensitivity: 3 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable From: "chrisjonesubn" To: "mkhaira1" X-XaM3-API-Version: 4.1 (B27) X-type: 0 X-SenderIP: 200.61.79.134 X-Virus-Scanned: by amavisd-new at libero.it Received-SPF: X-Spam-Status: No, hits=4.3 required=5.0 tests=BAYES_60,DEAR_SOMETHING,MAILTO_TO_SPAM_ADDR,RCVD_IN_ORBS, SUBJ_ALL_CAPS version=2.55 X-Spam-Level: **** X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) X-ecartis-version: Ecartis v1.0.0 Sender: linux-crypto-bounce@nl.linux.org Errors-to: linux-crypto-bounce@nl.linux.org X-original-sender: chrisjonesubn@libero.it Precedence: bulk List-help: List-unsubscribe: List-software: Ecartis version 1.0.0 List-Id: X-List-ID: List-subscribe: List-owner: List-post: List-archive: X-list: linux-crypto PRIVATE TEL:(234-8037761716) Email: chrisjones532002@yahoo.com.br ATTN= :HONORABLE CONTRACTOR DATE:6/3/2004 Dear Sir, Sequel to the secret= ive arrangement in regards of the shipment of your contract sum, I wish = to inform you that all necessary modalities have been automatically con= cluded and has left Nigeria to London via your Country today by Express = Cargo Flight. Note carefully that the content of the crate is "MONEY" b= ut I did not disclose it to the Courier Services as Money, rather I info= rmed them that the crate contain Vital "DIPLOMATIC DOCUMENTS" belonging=0D = to my client (that?s you). However, On no account should you disclose th= e content of the crate with the Diplomatic Courier Services for fear of= betrayal. So do not allow them to know that the content is money. Furt= her more, kindly get back to me as soon as possible so that i can furnis= h with you every modalities regards to the conclusion of this transactio= n. Meanwhile, I will be coming over to your country immediately the con= signment arrives in your Country for my 20% share. Congrats and remain = blessed. Best Regards, MR CHRITIAN JONES - Linux-crypto: cryptography in and on the Linux system Archive: http://mail.nl.linux.org/linux-crypto/ From linux-crypto-bounce@nl.linux.org Tue Jul 06 21:14:05 2004 Received: from localhost ([127.0.0.1] helo=humbolt) by humbolt.nl.linux.org with esmtp (Exim 4.22) id 1BhvMJ-0002Kn-QH; Tue, 06 Jul 2004 21:12:03 +0200 Received: with ECARTIS (v1.0.0; list linux-crypto); Tue, 06 Jul 2004 21:11:57 +0200 (CEST) Received: from mail.gmx.net ([213.165.64.20]) by humbolt.nl.linux.org with smtp (Exim 4.22) id 1BhvM1-0002It-R3 for linux-crypto@nl.linux.org; Tue, 06 Jul 2004 21:11:45 +0200 Received: (qmail 26875 invoked by uid 0); 6 Jul 2004 19:11:22 -0000 Received: from 217.224.34.9 by www1.gmx.net with HTTP; Tue, 6 Jul 2004 21:11:22 +0200 (MEST) Date: Tue, 6 Jul 2004 21:11:22 +0200 (MEST) From: tROLLI02@gmx.de To: linux-crypto@nl.linux.org MIME-Version: 1.0 Subject: loopAES 2.1a on soft raid Linux 2.6.6 X-Priority: 3 (Normal) X-Authenticated: #691426 Message-ID: <3619.1089141082@www1.gmx.net> X-Mailer: WWW-Mail 1.6 (Global Message Exchange) X-Flags: 0001 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Received-SPF: X-Spam-Status: No, hits=-2.9 required=5.0 tests=BAYES_10,FROM_ENDS_IN_NUMS,NO_REAL_NAME,RCVD_IN_ORBS version=2.55 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) X-ecartis-version: Ecartis v1.0.0 Sender: linux-crypto-bounce@nl.linux.org Errors-to: linux-crypto-bounce@nl.linux.org X-original-sender: tROLLI02@gmx.de Precedence: bulk List-help: List-unsubscribe: List-software: Ecartis version 1.0.0 List-Id: X-List-ID: List-subscribe: List-owner: List-post: List-archive: X-list: linux-crypto Hi All ... I have been playing arround with loopAES for quite some time now and I love it. The ability to boot from a removeable media such as a CD or a USB plus the strength of loopAES GPG protected multi-key is fantastic. I was now trying to get loop AES working on a soft raid, but i don't seam to get very far. ext2 on loopAES on singel disk works fine ext2 on md0 works fine too but ext2 on loopAES on md0 causes a seg fault Before I seriously start looking into why this dosn't work, I'd like to know if there is anyone else out there that got loopAES on soft raid working. thankx ... tR02 ------ my system: 2.6.6 Kernel + loopAES 2.1v debian:~# cat /proc/mdstat Personalities : [linear] [raid0] [raid1] [raid5] md0 : active linear hde2[1] hde1[0] <- split one disk in 2 for testing 156288128 blocks 32k rounding debian:~# losetup -e AES192 -K /boot/rootkey.gpg /dev/loop7 /dev/md0 debian:~# mke2fs /dev/loop7 <- tis working! debian:~# mount -t ext2 /dev/loop7 /mnt/ debian:~# ls -al /mnt <- seg fault! -- +++ Jetzt WLAN-Router für alle DSL-Einsteiger und Wechsler +++ GMX DSL-Powertarife zudem 3 Monate gratis* http://www.gmx.net/dsl - Linux-crypto: cryptography in and on the Linux system Archive: http://mail.nl.linux.org/linux-crypto/ From linux-crypto-bounce@nl.linux.org Wed Jul 07 16:27:53 2004 Received: from localhost ([127.0.0.1] helo=humbolt) by humbolt.nl.linux.org with esmtp (Exim 4.22) id 1BiDN3-0005rJ-Oz; Wed, 07 Jul 2004 16:26:01 +0200 Received: with ECARTIS (v1.0.0; list linux-crypto); Wed, 07 Jul 2004 16:25:54 +0200 (CEST) Received: from mato.luukku.com ([193.209.83.251]) by humbolt.nl.linux.org with esmtp (Exim 4.22) id 1BiDMn-0005q0-Kp for linux-crypto@nl.linux.org; Wed, 07 Jul 2004 16:25:45 +0200 Received: from localhost (mta3-o.i.luukku.com [10.0.1.132]) by mta3-o.i.luukku.com (Postfix) with ESMTP id 17067FF8EC; Wed, 7 Jul 2004 17:25:35 +0300 (EEST) Received: from users.sourceforge.net (faec.yhteys.mtv3.fi [62.236.236.250]) by mato.luukku.com (Postfix) with ESMTP id 5C1BC22EE8A; Wed, 7 Jul 2004 17:25:34 +0300 (EEST) Message-ID: <40EC080E.9C357B8E@users.sourceforge.net> Date: Wed, 07 Jul 2004 17:26:22 +0300 From: Jari Ruusu X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.4.22aa1r7 i686) X-Accept-Language: en MIME-Version: 1.0 To: tROLLI02@gmx.de Cc: linux-crypto@nl.linux.org Subject: Re: loopAES 2.1a on soft raid Linux 2.6.6 References: <3619.1089141082@www1.gmx.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Received-SPF: X-Spam-Status: No, hits=-5.4 required=5.0 tests=AWL,BAYES_10,EMAIL_ATTRIBUTION,MAILTO_TO_SPAM_ADDR, QUOTED_EMAIL_TEXT,RCVD_IN_ORBS,REFERENCES, REPLY_WITH_QUOTES,USER_AGENT_MOZILLA_XM version=2.55 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) X-ecartis-version: Ecartis v1.0.0 Sender: linux-crypto-bounce@nl.linux.org Errors-to: linux-crypto-bounce@nl.linux.org X-original-sender: jariruusu@users.sourceforge.net Precedence: bulk List-help: List-unsubscribe: List-software: Ecartis version 1.0.0 List-Id: X-List-ID: List-subscribe: List-owner: List-post: List-archive: X-list: linux-crypto tROLLI02@gmx.de wrote: > I was now trying to get loop AES working on a soft raid, but i don't > seam to get very far. > > ext2 on loopAES on singel disk works fine > ext2 on md0 works fine too > > but ext2 on loopAES on md0 causes a seg fault > > Before I seriously start looking into why this dosn't work, > I'd like to know if there is anyone else out there > that got loopAES on soft raid working. On subject line you said that you were using loop-AES-v2.1a, but loop-AES-v2.1b was released on May 27 2004, and it included a fix for this bug: "Fixed bio vec merge bug that only affected loop on top of md-raid0 or md-linear (2.6 kernels only)." http://mail.nl.linux.org/linux-crypto/2004-05/msg00032.html -- Jari Ruusu 1024R/3A220F51 5B 4B F9 BB D3 3F 52 E9 DB 1D EB E3 24 0E A9 DD - Linux-crypto: cryptography in and on the Linux system Archive: http://mail.nl.linux.org/linux-crypto/ From linux-crypto-bounce@nl.linux.org Thu Jul 08 14:27:51 2004 Received: from localhost ([127.0.0.1] helo=humbolt) by humbolt.nl.linux.org with esmtp (Exim 4.22) id 1BiXyI-0003eG-St; Thu, 08 Jul 2004 14:25:50 +0200 Received: with ECARTIS (v1.0.0; list linux-crypto); Thu, 08 Jul 2004 14:25:43 +0200 (CEST) Received: from [217.207.221.147] (helo=philex.com) by humbolt.nl.linux.org with esmtp (Exim 4.22) id 1BiXxz-0003cw-FW for linux-crypto@nl.linux.org; Thu, 08 Jul 2004 14:25:31 +0200 Received: from philex.com [127.0.0.1] by philex.com [127.0.0.1] (with RAW) (MDaemon.PRO.v7.1.0.R) for ; Thu, 08 Jul 2004 13:24:47 +0100 Date: Thu, 08 Jul 2004 13:24:47 +0100 From: Postmaster@philex.com Reply-To: Postmaster@philex.com Subject: MDaemon Notification -- Attachment Removed To: linux-crypto@nl.linux.org X-MDaemon-Deliver-To: linux-crypto@nl.linux.org Message-ID: Mime-Version: 1.0 X-Actual-From: Postmaster@philex.com X-MDSend-Notifications-To: [trash] Content-Type: text/plain; charset=US-ASCII Received-SPF: X-Spam-Status: No, hits=1.2 required=5.0 tests=AWL,NO_REAL_NAME,RCVD_IN_ORBS version=2.55 X-Spam-Level: * X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) X-ecartis-version: Ecartis v1.0.0 Sender: linux-crypto-bounce@nl.linux.org Errors-to: linux-crypto-bounce@nl.linux.org X-original-sender: Postmaster@philex.com Precedence: bulk List-help: List-unsubscribe: List-software: Ecartis version 1.0.0 List-Id: X-List-ID: List-subscribe: List-owner: List-post: List-archive: X-list: linux-crypto The following message contained restricted attachment(s) which have been removed: >From : linux-crypto@nl.linux.org To : bonnie@philex.com Subject : Spam Message-ID: Attachment(s) removed: ----------------------------------------- websitelist01_bonnie.zip - Linux-crypto: cryptography in and on the Linux system Archive: http://mail.nl.linux.org/linux-crypto/ From linux-crypto-bounce@nl.linux.org Thu Jul 08 14:27:53 2004 Received: from localhost ([127.0.0.1] helo=humbolt) by humbolt.nl.linux.org with esmtp (Exim 4.22) id 1BiXyI-0003eC-Cx; Thu, 08 Jul 2004 14:25:50 +0200 Received: with ECARTIS (v1.0.0; list linux-crypto); Thu, 08 Jul 2004 14:25:42 +0200 (CEST) Received: from [217.207.221.147] (helo=philex.com) by humbolt.nl.linux.org with esmtp (Exim 4.22) id 1BiXxx-0003cy-FT for linux-crypto@nl.linux.org; Thu, 08 Jul 2004 14:25:29 +0200 Received: from philex.com [127.0.0.1] by philex.com [127.0.0.1] (with RAW) (MDaemon.PRO.v7.1.0.R) for ; Thu, 08 Jul 2004 13:24:51 +0100 Date: Thu, 08 Jul 2004 13:24:51 +0100 From: Postmaster@philex.com Reply-To: Postmaster@philex.com Subject: MDaemon Notification -- Attachment Removed To: linux-crypto@nl.linux.org X-MDaemon-Deliver-To: linux-crypto@nl.linux.org Message-ID: Mime-Version: 1.0 X-Actual-From: Postmaster@philex.com X-MDSend-Notifications-To: [trash] Content-Type: text/plain; charset=US-ASCII Received-SPF: X-Spam-Status: No, hits=1.2 required=5.0 tests=NO_REAL_NAME,RCVD_IN_ORBS version=2.55 X-Spam-Level: * X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) X-ecartis-version: Ecartis v1.0.0 Sender: linux-crypto-bounce@nl.linux.org Errors-to: linux-crypto-bounce@nl.linux.org X-original-sender: Postmaster@philex.com Precedence: bulk List-help: List-unsubscribe: List-software: Ecartis version 1.0.0 List-Id: X-List-ID: List-subscribe: List-owner: List-post: List-archive: X-list: linux-crypto The following message contained restricted attachment(s) which have been removed: >From : linux-crypto@nl.linux.org To : archive@philex.com Subject : (Archive Copy) Spam Message-ID: Attachment(s) removed: ----------------------------------------- websitelist01_bonnie.zip - Linux-crypto: cryptography in and on the Linux system Archive: http://mail.nl.linux.org/linux-crypto/ From linux-crypto-bounce@nl.linux.org Fri Jul 09 15:37:40 2004 Received: from localhost ([127.0.0.1] helo=humbolt) by humbolt.nl.linux.org with esmtp (Exim 4.22) id 1BivXO-0002au-7U; Fri, 09 Jul 2004 15:35:38 +0200 Received: with ECARTIS (v1.0.0; list linux-crypto); Fri, 09 Jul 2004 15:35:31 +0200 (CEST) Received: from [62.77.36.165] (helo=hoppy.wappi.com) by humbolt.nl.linux.org with smtp (Exim 4.22) id 1BivWr-0002Y0-M1 for linux-crypto@nl.linux.org; Fri, 09 Jul 2004 15:35:05 +0200 Received: (qmail 31311 invoked by uid 99); 9 Jul 2004 12:08:51 -0000 Message-ID: <20040709120851.31301.qmail@hoppy.wappi.com> To: Subject: TRUSTEE Reply-To: david From: david Date: Fri, 09 Jul 2004 12:08:51 +0000 Organization: www.wappi.com by Movenda S.p.A. X-Mailer: PHP/3.0.18 X-Scripts-by: sergio@ascia.net X-Remote_Host: X-Remote_Addr: 80.88.132.12 X-User_Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1) X-Forwarded_For: X-Via: Content-Transfer-Encoding: binary MIME-Version: 1.0 Content-Type: text/plain Received-SPF: X-Spam-Status: No, hits=0.1 required=5.0 tests=RCVD_IN_ORBS version=2.55 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) X-ecartis-version: Ecartis v1.0.0 Sender: linux-crypto-bounce@nl.linux.org Errors-to: linux-crypto-bounce@nl.linux.org X-original-sender: davidmamman7@wappi.com Precedence: bulk List-help: List-unsubscribe: List-software: Ecartis version 1.0.0 List-Id: X-List-ID: List-subscribe: List-owner: List-post: List-archive: X-list: linux-crypto Dear Friend. As you read this, I don't want you to feel sorry for me, because, I believe everyone will die someday. My name is David Mamman, a merchant in Dubai, in the U.A.E.I have been diagnosed with Esophageal Cancer which was discovered very late, due to my laxity in caring for my health. It has defiled all forms of medicine, and right now I have only about a few months to live, according to medical experts. I have not particularly lived my life so well, as I never really cared for anyone not even myself but my business. Though I am very rich, I was never generous, I was always hostile to people and only focus on my business as that was the only thing I cared for. But now I regret all this as I now know that there is more to life than just wanting to have or make all the money in the world. I believe when God gives me a second chance to come to this world I would live my life a different way from how I have lived it. Now that God ! has called me, I have willed and given most of my properties and assets to my immediate and extended family members and as well as a few close friends. I want God to be merciful to me and accept my soul and so, I have decided to give arms to charity organizations and give succour and confort to the less priviledged in our societies, as I want this to be one of the last good deeds I do on earth. So far, I have distributed money to some charity organizations in the U.A.E, Algeria and Malaysia. Now that my health has deteriorated so badly, I cannot do this my self anymore. I once asked members of my family to close one of my accounts and distribute the money which I have there to charity organization and to the less priviledged in Bulgaria and Pakistan, they refused and kept the money to themselves. Hence, I do not trust them anymore, as they seem not to be contended with what I have left for them. The last of my money which no one knows of is the huge cash deposit of twenty four million dollars(24MUSD) that I have with a Security Company in Europe for safe keeping. I will want you to help me collect this deposit and disburse it to some charity organizations and to the less priviledged. Please send me a mail to indicate if you will assist me in this disbursement. I have set aside 10% for you for your time and patience. You can e-mail me at:davidmamman7@indiatimes.com While I await to hear from you, may God be with you and your entire family. Remain blessed. David Mamman --- Mail inviata con il servizio WebMail di Wappi Connetti ad internet il tuo telefonino: http://www.wappi.com/ Wappi e' un servizio di Movenda S.p.A. http://www.movenda.com/ - Linux-crypto: cryptography in and on the Linux system Archive: http://mail.nl.linux.org/linux-crypto/ From linux-crypto-bounce@nl.linux.org Fri Jul 09 22:31:29 2004 Received: from localhost ([127.0.0.1] helo=humbolt) by humbolt.nl.linux.org with esmtp (Exim 4.22) id 1Bj202-0003Ge-EE; Fri, 09 Jul 2004 22:29:38 +0200 Received: with ECARTIS (v1.0.0; list linux-crypto); Fri, 09 Jul 2004 22:29:31 +0200 (CEST) Received: from web40511.mail.yahoo.com ([66.218.78.128]) by humbolt.nl.linux.org with smtp (Exim 4.22) id 1Bj1zo-0003CW-7K for linux-crypto@nl.linux.org; Fri, 09 Jul 2004 22:29:24 +0200 Message-ID: <20040709202750.92439.qmail@web40511.mail.yahoo.com> Received: from [217.255.134.159] by web40511.mail.yahoo.com via HTTP; Fri, 09 Jul 2004 13:27:50 PDT Date: Fri, 9 Jul 2004 13:27:50 -0700 (PDT) From: Thomas "Müller" Subject: Re: loopAES 2.1a on soft raid Linux 2.6.6 To: linux-crypto@nl.linux.org In-Reply-To: <3619.1089141082@www1.gmx.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Received-SPF: X-Spam-Status: No, hits=-0.1 required=5.0 tests=EMAIL_ATTRIBUTION,IN_REP_TO,MAILTO_TO_SPAM_ADDR, RCVD_IN_ORBS version=2.55 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) X-ecartis-version: Ecartis v1.0.0 Sender: linux-crypto-bounce@nl.linux.org Errors-to: linux-crypto-bounce@nl.linux.org X-original-sender: etwcn@yahoo.com Precedence: bulk List-help: List-unsubscribe: List-software: Ecartis version 1.0.0 List-Id: X-List-ID: List-subscribe: List-owner: List-post: List-archive: X-list: linux-crypto --- tROLLI02@gmx.de wrote: > Before I seriously start looking into why this > dosn't work, > I'd like to know if there is anyone else out there > that got loopAES on soft raid working. I am using loopAES on a software-raid5 with 5 disks for more than half a year now. I never had any problems. I have kernel 2.4.25. Thomas __________________________________ Do you Yahoo!? Yahoo! Mail - 50x more storage than other providers! http://promotions.yahoo.com/new_mail - Linux-crypto: cryptography in and on the Linux system Archive: http://mail.nl.linux.org/linux-crypto/ From linux-crypto-bounce@nl.linux.org Sat Jul 10 03:25:28 2004 Received: from localhost ([127.0.0.1] helo=humbolt) by humbolt.nl.linux.org with esmtp (Exim 4.22) id 1Bj6ad-0004Gj-QF; Sat, 10 Jul 2004 03:23:43 +0200 Received: with ECARTIS (v1.0.0; list linux-crypto); Sat, 10 Jul 2004 03:23:37 +0200 (CEST) Received: from [202.74.166.250] (helo=amristar.com.au) by humbolt.nl.linux.org with smtp (Exim 4.22) id 1Bj6aN-0004Fm-SE for linux-crypto@nl.linux.org; Sat, 10 Jul 2004 03:23:28 +0200 Received: (qmail 7911 invoked from network); 10 Jul 2004 01:23:02 -0000 Received: from unknown (HELO elvandar) (127.0.0.1) by 0 with SMTP; 10 Jul 2004 01:23:02 -0000 Received: from localhost ([127.0.0.1]) by elvandar with esmtp (Exim 3.35 #1 (Debian)) id 1Bj6L7-0001Pf-00 for ; Sat, 10 Jul 2004 09:07:41 +0800 Subject: Re: loopAES 2.1a on soft raid Linux 2.6.6 From: Daniel Harvey To: linux-crypto@nl.linux.org In-Reply-To: <20040709202750.92439.qmail@web40511.mail.yahoo.com> References: <20040709202750.92439.qmail@web40511.mail.yahoo.com> Content-Type: text/plain Message-Id: <1089421661.2092.3.camel@elvandar> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Sat, 10 Jul 2004 09:07:41 +0800 Content-Transfer-Encoding: 7bit X-Sent-Items-Stored: elvandar Received-SPF: X-Spam-Status: No, hits=-4.8 required=5.0 tests=AWL,BAYES_20,IN_REP_TO,MAILTO_TO_SPAM_ADDR,RCVD_IN_ORBS, REFERENCES,USER_AGENT_XIMIAN autolearn=ham version=2.55 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) X-ecartis-version: Ecartis v1.0.0 Sender: linux-crypto-bounce@nl.linux.org Errors-to: linux-crypto-bounce@nl.linux.org X-original-sender: daniel@amristar.com.au Precedence: bulk List-help: List-unsubscribe: List-software: Ecartis version 1.0.0 List-Id: X-List-ID: List-subscribe: List-owner: List-post: List-archive: X-list: linux-crypto I've been using loop-aes with Linux 2.4.x through 2.6.x for a number of years with no problems. > --- tROLLI02@gmx.de wrote: > > Before I seriously start looking into why this > > dosn't work, > > I'd like to know if there is anyone else out there > > that got loopAES on soft raid working. > Regards -- Daniel Harvey Phone/Fax +61 8 9481 1566/77 Director, Amristar Solutions; www.amristar.com.au Mobile +61 41 444 8136 - Linux-crypto: cryptography in and on the Linux system Archive: http://mail.nl.linux.org/linux-crypto/ From linux-crypto-bounce@nl.linux.org Sat Jul 10 04:01:14 2004 Received: from localhost ([127.0.0.1] helo=humbolt) by humbolt.nl.linux.org with esmtp (Exim 4.22) id 1Bj79M-0005x6-B6; Sat, 10 Jul 2004 03:59:36 +0200 Received: with ECARTIS (v1.0.0; list linux-crypto); Sat, 10 Jul 2004 03:59:28 +0200 (CEST) Received: from [202.164.170.194] (helo=PHMNLAPP02.ph.kworld.kpmg.com) by humbolt.nl.linux.org with smtp (Exim 4.22) id 1Bj795-0005vj-9N for linux-crypto@nl.linux.org; Sat, 10 Jul 2004 03:59:19 +0200 Received: from SMTP agent by mail gateway Sat, 10 Jul 2004 09:48:26 --800 From: mailsweeper@kpmg.com.ph To: linux-crypto@nl.linux.org Date: Sat, 10 Jul 2004 09:59:07 +0800 (CCT) Subject: ATTENTION: A message you sent was found to contain a Virus and has been deleted. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Message-Id: Received-SPF: X-Spam-Status: No, hits=1.9 required=5.0 tests=EXCUSE_1,NO_REAL_NAME,RCVD_IN_ORBS version=2.55 X-Spam-Level: * X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) X-ecartis-version: Ecartis v1.0.0 Sender: linux-crypto-bounce@nl.linux.org Errors-to: linux-crypto-bounce@nl.linux.org X-original-sender: mailsweeper@kpmg.com.ph Precedence: bulk List-help: List-unsubscribe: List-software: Ecartis version 1.0.0 List-Id: X-List-ID: List-subscribe: List-owner: List-post: List-archive: X-list: linux-crypto The message you sent to "mailsweeper@kpmg.com.ph " with subject "Mail Delivery (failure mailsweeper@kpmg.com.ph)" on "Sat, 10 Jul 2004 03:58:45 +0200" Was found to contain a Virus and has been deleted. The intended recipient h= as been notified of this action. It is your responsibility to clean the inf= ected attachment before resending. Virus Type: "Scenarios/Incoming/Sophos Anti-Virus: A virus has been detecte= d: 'W32/Netsky-P'. Scenarios/Incoming/Attachments - Hostile: A filename matching the file mask= was detected: 'message.scr'. Scenarios/Incoming/Data Type Manager: 'ItemLength.GE.0'. " You might have received this warning even though you did not send a virus-i= nfected email to KPMG. This is due to the fact that many viruses use false = email addresses (=E2=80=9Cspoofing=E2=80=9D) and unfortunately this virus h= as used yours. If you have received this email because of address spoofing= , we apologize for the inconvenience and suggest you delete this mail. - Linux-crypto: cryptography in and on the Linux system Archive: http://mail.nl.linux.org/linux-crypto/ From linux-crypto-bounce@nl.linux.org Sun Jul 11 18:12:00 2004 Received: from localhost ([127.0.0.1] helo=humbolt) by humbolt.nl.linux.org with esmtp (Exim 4.22) id 1Bjgty-0004eU-Kj; Sun, 11 Jul 2004 18:10:06 +0200 Received: with ECARTIS (v1.0.0; list linux-crypto); Sun, 11 Jul 2004 18:09:58 +0200 (CEST) Received: from pop.gmx.net ([213.165.64.20] helo=mail.gmx.net) by humbolt.nl.linux.org with smtp (Exim 4.22) id 1Bjgte-0004dY-SP for linux-crypto@nl.linux.org; Sun, 11 Jul 2004 18:09:46 +0200 Received: (qmail 31549 invoked by uid 0); 11 Jul 2004 16:09:36 -0000 Received: from 80.171.34.184 by www69.gmx.net with HTTP; Sun, 11 Jul 2004 18:09:36 +0200 (MEST) Date: Sun, 11 Jul 2004 18:09:36 +0200 (MEST) From: a.engels@gmx.net To: linux-crypto@nl.linux.org MIME-Version: 1.0 Subject: Loop-AES, security concerns, stability of file backed loop-aes X-Priority: 3 (Normal) X-Authenticated: #2329190 Message-ID: <19923.1089562176@www69.gmx.net> X-Mailer: WWW-Mail 1.6 (Global Message Exchange) X-Flags: 0001 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Received-SPF: X-Spam-Status: No, hits=-1.4 required=5.0 tests=BAYES_20,NO_REAL_NAME,RCVD_IN_ORBS version=2.55 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) X-ecartis-version: Ecartis v1.0.0 Sender: linux-crypto-bounce@nl.linux.org Errors-to: linux-crypto-bounce@nl.linux.org X-original-sender: a.engels@gmx.net Precedence: bulk List-help: List-unsubscribe: List-software: Ecartis version 1.0.0 List-Id: X-List-ID: List-subscribe: List-owner: List-post: List-archive: X-list: linux-crypto Dear mailing list readers, I have spent the last days to evaluate whole disk encryption possibilities under Linux. As far as I know there are 3 ways: cryptoloop, dm-crypt and loop-aes. My task is to backup gigabytes of medical and financial data stored on a couple of smb file servers to a remote machine, whose security is unknown. Lets assume the worst case that the crypto container on this backup machines is world readable. I will use rsync, so only changes of the crypto container are transferred on a daily basis. It appears to me that loop-aes is the only one choice under linux with real secure implementation of strong encryption. However, I am no crypto analyst and would love to read some professional comments about loop-aes. So, my first question is, if somebody knows a link to a document which deals with this? Also, I have questions related to file backed loop-aes encryption. If I use ext3 on top of a file backed loop device, I understand that the consistency is in danger because writes are reordered of the underlying fs. What I dont understand is the claim, that ext3 (top) <-> loop-aes <-> ext3 (underlying with data=ordered or data=journal) should work. Why is the assumption correct that the underlying ext3 preserves the same write order of the ext3 on top? I found some other notes about deadlocks while using file backed loop-aes. On Linux Kernel mailing list it is claimed that GFP_NOFS is cause of deadlocks. Ext3 uses this call, ext2 not. The author of loop-aes just used the phrase "it should maybe work" if ext2 is fs on top. So, does somebody of you know the stability of this scenario (file backed loop-aes with ext2 on top) on production servers? The reason I dont want to use device backed loop-aes is the dependency from the block device. If I use file backed loop-aes and one server crashes, I can just copy the crypto container as file to to an arbitrary fs created on a i.e. a ide, scsi-blockdevice or even software raid of a new server. I think I wouldnt have this functionality if I backup the (ide-,scsi- or software raid-) block device with "dd" (maybe I am wrong?). Kind regards, A.Engels - Linux-crypto: cryptography in and on the Linux system Archive: http://mail.nl.linux.org/linux-crypto/ From linux-crypto-bounce@nl.linux.org Sun Jul 11 20:29:50 2004 Received: from localhost ([127.0.0.1] helo=humbolt) by humbolt.nl.linux.org with esmtp (Exim 4.22) id 1Bjj3g-0006py-61; Sun, 11 Jul 2004 20:28:16 +0200 Received: with ECARTIS (v1.0.0; list linux-crypto); Sun, 11 Jul 2004 20:28:09 +0200 (CEST) Received: from server133-han.de-nserver.de ([81.3.17.173]) by humbolt.nl.linux.org with esmtp (Exim 4.22) id 1Bjj3I-0006om-Cr for linux-crypto@nl.linux.org; Sun, 11 Jul 2004 20:27:52 +0200 Received: (qmail 3806 invoked from network); 11 Jul 2004 18:27:26 -0000 Received: from unknown (HELO organic.homeip.net) (test@bitfalle.org@217.82.199.2) by server133-han.de-nserver.de with SMTP; 11 Jul 2004 18:27:26 -0000 Received: from localhost (localhost [127.0.0.1]) by organic.homeip.net (Postfix) with ESMTP id 2609716B6D for ; Sun, 11 Jul 2004 20:27:37 +0200 (CEST) Received: from organic.homeip.net ([127.0.0.1]) by localhost (organic.homeip.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 25904-02 for ; Sun, 11 Jul 2004 20:27:35 +0200 (CEST) Received: from tatooine.organic.net (tatooine.organic.net [192.168.0.26]) by organic.homeip.net (Postfix) with ESMTP id C389F15C60 for ; Sun, 11 Jul 2004 20:27:35 +0200 (CEST) Received: by tatooine.organic.net (Postfix, from userid 500) id 107B8168095; Sun, 11 Jul 2004 20:27:58 +0200 (CEST) Date: Sun, 11 Jul 2004 20:27:57 +0200 From: markus reichelt To: linux-crypto@nl.linux.org Subject: Re: Loop-AES, security concerns, stability of file backed loop-aes Message-ID: <20040711182757.GA4517@lists.notified.de> Mail-Followup-To: linux-crypto@nl.linux.org References: <19923.1089562176@www69.gmx.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; x-action=pgp-signed Content-Disposition: inline In-Reply-To: <19923.1089562176@www69.gmx.net> Organization: still stuck in reorganization mode X-Request-PGP: http://lists.notified.de/pubkey.mr.lists.asc User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new at organic.homeip.net Received-SPF: X-Spam-Status: No, hits=-10.5 required=5.0 tests=AWL,BAYES_10,EMAIL_ATTRIBUTION,IN_REP_TO,PGP_SIGNATURE, QUOTED_EMAIL_TEXT,RCVD_IN_ORBS,REFERENCES, REPLY_WITH_QUOTES,USER_AGENT_MUTT autolearn=ham version=2.55 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) X-ecartis-version: Ecartis v1.0.0 Sender: linux-crypto-bounce@nl.linux.org Errors-to: linux-crypto-bounce@nl.linux.org X-original-sender: mr@lists.notified.de Precedence: bulk List-help: List-unsubscribe: List-software: Ecartis version 1.0.0 List-Id: X-List-ID: List-subscribe: List-owner: List-post: List-archive: X-list: linux-crypto -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 a.engels@gmx.net wrote: > It appears to me that loop-aes is the only one choice under linux with real > secure implementation of strong encryption. However, I am no crypto analyst > and would love to read some professional comments about loop-aes. So, my > first question is, if somebody knows a link to a document which deals with > this? Scientifically? Unfortunately not. Loop-AES is only secure if it has been set up in multi-key mode with encrypted swap. Loop-AEs in single-key mode is vulnerable to a watermark attack and cryptoloop/dm-crypt are vulnerable to watermark/optimized dictionary attacks. Optimized dictionary attack: http://marc.theaimsgroup.com/?l=linux-kernel&m=107419912024246&w=2 Watermark attack: http://marc.theaimsgroup.com/?l=linux-kernel&m=107719798631935&w=2 > Also, I have questions related to file backed loop-aes encryption. I would avoid file backed loop-aes completely. Too much uncertainty lies in what could be the cause of lockups. > The reason I dont want to use device backed loop-aes is the dependency from > the block device. If I use file backed loop-aes and one server crashes, I > can just copy the crypto container as file to to an arbitrary fs created on > a i.e. a ide, scsi-blockdevice or even software raid of a new server. I > think I wouldnt have this functionality if I backup the (ide-,scsi- or > software raid-) block device with "dd" (maybe I am wrong?). In theory this should work. A partition image can be mounted, so it should work with loop-AES as well. This should be sufficient to access your data in case of an emergency, but be sure to mount the image read-only. Because of the filesystem's last access time (atime) record a simple 'ls -al' causes a write. Of course you could use noatime as mount option but I would play it safe. I would go along with this. OTOH, don't know about your setup... a different approach could be to split up your large data collection in smaller chunks (directorywise, f.e.) tar/bzip2 'em up and use gpg to encrypt the *.tar.bz2. Additionally you could use rar to create archives with recovery information, this comes in handy if network traffic somehow caused corrupted files. The big disadvantage with gpg is that even slightly corrupted encrypted files can't be decrypted. Therefore I use the 'protective layer' of rar archives. :) Then you could use rsync (over ssh) for backup. This method is quite messy (setup, maintenance, ressources), but works. - -- Bastard Administrator in $hell -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQFA8YatLMyTO8Kj/uQRAsWIAJ9qTnO0bUS94NV/vF3mbLmLAt7gKwCcD0Lp EVdTHH8OTiSx62llfryWYOQ= =y3VY -----END PGP SIGNATURE----- - Linux-crypto: cryptography in and on the Linux system Archive: http://mail.nl.linux.org/linux-crypto/ From linux-crypto-bounce@nl.linux.org Sun Jul 11 22:08:56 2004 Received: from localhost ([127.0.0.1] helo=humbolt) by humbolt.nl.linux.org with esmtp (Exim 4.22) id 1BjkbG-0004o8-SQ; Sun, 11 Jul 2004 22:07:02 +0200 Received: with ECARTIS (v1.0.0; list linux-crypto); Sun, 11 Jul 2004 22:06:56 +0200 (CEST) Received: from av6-1-sn3.vrr.skanova.net ([81.228.9.179]) by humbolt.nl.linux.org with esmtp (Exim 4.22) id 1Bjkaw-0004n4-Ka for linux-crypto@nl.linux.org; Sun, 11 Jul 2004 22:06:42 +0200 Received: by av6-1-sn3.vrr.skanova.net (Postfix, from userid 502) id 87CE137E80; Sun, 11 Jul 2004 22:06:29 +0200 (CEST) Received: from smtp3-2-sn3.vrr.skanova.net (smtp3-2-sn3.vrr.skanova.net [81.228.9.102]) by av6-1-sn3.vrr.skanova.net (Postfix) with ESMTP id 786E337E44 for ; Sun, 11 Jul 2004 22:06:29 +0200 (CEST) Received: from balrog (h173n2fls33o284.telia.com [213.64.142.173]) by smtp3-2-sn3.vrr.skanova.net (Postfix) with ESMTP id E15C737E47 for ; Sun, 11 Jul 2004 22:06:28 +0200 (CEST) Received: from amavis by balrog with scanned-ok (Exim 3.36 #1 (Debian)) id 1Bjkai-000014-00 for ; Sun, 11 Jul 2004 22:06:28 +0200 Received: from balrog ([127.0.0.1]) by localhost (balrog [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 10897-09 for ; Sun, 11 Jul 2004 22:06:26 +0200 (CEST) Received: from thomas by balrog with local (Exim 3.36 #1 (Debian)) id 1Bjkaf-00009m-00 for ; Sun, 11 Jul 2004 22:06:25 +0200 Date: Sun, 11 Jul 2004 22:06:25 +0200 From: Thomas =?iso-8859-1?Q?Sj=F6gren?= To: linux-crypto@nl.linux.org Subject: Re: Loop-AES, security concerns, stability of file backed loop-aes Message-ID: <20040711200625.GB31065@northernsecurity.net> Reply-To: thomas@northernsecurity.net References: <19923.1089562176@www69.gmx.net> <20040711182757.GA4517@lists.notified.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="xXmbgvnjoT4axfJE" Content-Disposition: inline In-Reply-To: <20040711182757.GA4517@lists.notified.de> X-PGP-Request: http://www.northernsecurity.net/contact/114aa85c.asc X-PGP-Fingerprint: 3367 0D84 444B D5B6 980E 7D5D 1209 639D 114A A85C User-Agent: Mutt/1.5.6+20040523i X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) Received-SPF: X-Spam-Status: No, hits=-11.2 required=5.0 tests=AWL,BAYES_01,IN_REP_TO,PGP_SIGNATURE_2,QUOTED_EMAIL_TEXT, RCVD_IN_ORBS,REFERENCES,REPLY_WITH_QUOTES,USER_AGENT_MUTT autolearn=ham version=2.55 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) X-ecartis-version: Ecartis v1.0.0 Sender: linux-crypto-bounce@nl.linux.org Errors-to: linux-crypto-bounce@nl.linux.org X-original-sender: thomas@northernsecurity.net Precedence: bulk List-help: List-unsubscribe: List-software: Ecartis version 1.0.0 List-Id: X-List-ID: List-subscribe: List-owner: List-post: List-archive: X-list: linux-crypto --xXmbgvnjoT4axfJE Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Jul 11, 2004 at 08:27:57PM +0200, markus reichelt wrote: [...] > Then you could use rsync (over ssh) for backup. This method is quite > messy (setup, maintenance, ressources), but works. Since it's one(?) server and backup with pretty private info on it why not = spend some time and set a proper VPN between the two? /Thomas --=20 =3D=3D thomas@northernsecurity.net | thomas@se.linux.org =3D=3D Encrypted e-mails preferred | GPG KeyID: 114AA85C -- --xXmbgvnjoT4axfJE Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iQEVAwUBQPGdwdXAsD67qPj1AQJZUAf/V30cYHRIF2t1Xt05nL1LCSVLwaUFCWVT KYEjJZcHw7Uc3K0Q9+siwjz7kJP1jK9E2mrgSSTAqgcdYj4SVHGyXdy2ic4i1fQ0 Q9ypGBl/e2PlSY3k3m812PixQcxr8XyCBLXyVGKS3uQ4ZJmrT/JR5+1/cIDTd5CM fbCxhVVFgn3DhFOQzBD2EL5a7vREVAzTTvpJ3jivDrgvh4jzdgtYnOzF5zQi0EZV /fsy+Fr1H3kMPVJhdTcHy48izZF/CttpeLnv5QTkFYRnW6BJggkdde1xmuy2BasK hpp5D7ShT1bpRoxpL4trtIXOATlTXKdbSBm+Qq2sI38pYdjZudY9nQ== =KV7o -----END PGP SIGNATURE----- --xXmbgvnjoT4axfJE-- - Linux-crypto: cryptography in and on the Linux system Archive: http://mail.nl.linux.org/linux-crypto/ From linux-crypto-bounce@nl.linux.org Sun Jul 11 22:44:04 2004 Received: from localhost ([127.0.0.1] helo=humbolt) by humbolt.nl.linux.org with esmtp (Exim 4.22) id 1Bjl9c-0006Y8-4R; Sun, 11 Jul 2004 22:42:32 +0200 Received: with ECARTIS (v1.0.0; list linux-crypto); Sun, 11 Jul 2004 22:42:25 +0200 (CEST) Received: from server133-han.de-nserver.de ([81.3.17.173]) by humbolt.nl.linux.org with esmtp (Exim 4.22) id 1Bjl9I-0006XI-U8 for linux-crypto@nl.linux.org; Sun, 11 Jul 2004 22:42:12 +0200 Received: (qmail 4943 invoked from network); 11 Jul 2004 20:41:47 -0000 Received: from unknown (HELO organic.homeip.net) (test@bitfalle.org@217.82.199.2) by server133-han.de-nserver.de with SMTP; 11 Jul 2004 20:41:47 -0000 Received: from localhost (localhost [127.0.0.1]) by organic.homeip.net (Postfix) with ESMTP id 64D92173A5 for ; Sun, 11 Jul 2004 22:41:58 +0200 (CEST) Received: from organic.homeip.net ([127.0.0.1]) by localhost (organic.homeip.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 03920-08 for ; Sun, 11 Jul 2004 22:41:57 +0200 (CEST) Received: from tatooine.organic.net (tatooine.organic.net [192.168.0.26]) by organic.homeip.net (Postfix) with ESMTP id D23E2173A3 for ; Sun, 11 Jul 2004 22:41:57 +0200 (CEST) Received: by tatooine.organic.net (Postfix, from userid 500) id 4DD42168095; Sun, 11 Jul 2004 22:42:22 +0200 (CEST) Date: Sun, 11 Jul 2004 22:42:22 +0200 From: markus reichelt To: linux-crypto@nl.linux.org Subject: Re: Loop-AES, security concerns, stability of file backed loop-aes Message-ID: <20040711204222.GA5075@lists.notified.de> Mail-Followup-To: linux-crypto@nl.linux.org References: <19923.1089562176@www69.gmx.net> <20040711182757.GA4517@lists.notified.de> <20040711200625.GB31065@northernsecurity.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; x-action=pgp-signed Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20040711200625.GB31065@northernsecurity.net> Organization: still stuck in reorganization mode X-Request-PGP: http://lists.notified.de/pubkey.mr.lists.asc User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new at organic.homeip.net Received-SPF: X-Spam-Status: No, hits=-11.0 required=5.0 tests=AWL,BAYES_01,EMAIL_ATTRIBUTION,IN_REP_TO,PGP_SIGNATURE, QUOTED_EMAIL_TEXT,RCVD_IN_ORBS,REFERENCES, REPLY_WITH_QUOTES,USER_AGENT_MUTT autolearn=ham version=2.55 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) X-ecartis-version: Ecartis v1.0.0 Sender: linux-crypto-bounce@nl.linux.org Errors-to: linux-crypto-bounce@nl.linux.org X-original-sender: mr@lists.notified.de Precedence: bulk List-help: List-unsubscribe: List-software: Ecartis version 1.0.0 List-Id: X-List-ID: List-subscribe: List-owner: List-post: List-archive: X-list: linux-crypto -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Thomas Sjögren wrote: > On Sun, Jul 11, 2004 at 08:27:57PM +0200, markus reichelt wrote: > [...] > > Then you could use rsync (over ssh) for backup. This method is quite > > messy (setup, maintenance, ressources), but works. > > Since it's one(?) server and backup with pretty private info on it why not spend > some time and set a proper VPN between the two? Sure, if VPN suits his needs. Might be a bit oversized for plain backup imho. However, this could also be of interest: http://www.pizzashack.org/rssh/ "rssh is a restricted shell for use with OpenSSH, allowing only scp and/or sftp. For example, if you have a server which you only want to allow users to copy files off of via scp, without providing shell access, you can use rssh to do that." - -- Bastard Administrator in $hell -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQFA8aYuLMyTO8Kj/uQRAqvAAKCSVDGUQHDzgM+bCaky7pGPWT/dagCeJnqP UvLeLww7NP6izV7EDaiTntU= =93dw -----END PGP SIGNATURE----- - Linux-crypto: cryptography in and on the Linux system Archive: http://mail.nl.linux.org/linux-crypto/ From linux-crypto-bounce@nl.linux.org Mon Jul 12 00:41:02 2004 Received: from localhost ([127.0.0.1] helo=humbolt) by humbolt.nl.linux.org with esmtp (Exim 4.22) id 1Bjmyh-0005Th-4C; Mon, 12 Jul 2004 00:39:23 +0200 Received: with ECARTIS (v1.0.0; list linux-crypto); Mon, 12 Jul 2004 00:39:16 +0200 (CEST) Received: from imap.gmx.net ([213.165.64.20] helo=mail.gmx.net) by humbolt.nl.linux.org with smtp (Exim 4.22) id 1BjmyS-0005Ss-D0 for linux-crypto@nl.linux.org; Mon, 12 Jul 2004 00:39:08 +0200 Received: (qmail 4357 invoked by uid 0); 11 Jul 2004 22:38:55 -0000 Received: from 80.171.34.184 by www54.gmx.net with HTTP; Mon, 12 Jul 2004 00:38:56 +0200 (MEST) Date: Mon, 12 Jul 2004 00:38:56 +0200 (MEST) From: a.engels@gmx.net To: "linux crypto" MIME-Version: 1.0 Subject: Re: Loop-AES, security concerns, stability of file backed loop-aes X-Priority: 3 (Normal) X-Authenticated: #2329190 Message-ID: <15418.1089585536@www54.gmx.net> X-Mailer: WWW-Mail 1.6 (Global Message Exchange) X-Flags: 0001 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Received-SPF: X-Spam-Status: No, hits=-2.6 required=5.0 tests=AWL,BAYES_10,NO_REAL_NAME,QUOTED_EMAIL_TEXT,RCVD_IN_ORBS version=2.55 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) X-ecartis-version: Ecartis v1.0.0 Sender: linux-crypto-bounce@nl.linux.org Errors-to: linux-crypto-bounce@nl.linux.org X-original-sender: a.engels@gmx.net Precedence: bulk List-help: List-unsubscribe: List-software: Ecartis version 1.0.0 List-Id: X-List-ID: List-subscribe: List-owner: List-post: List-archive: X-list: linux-crypto > On Sun, Jul 11, 2004 at 08:27:57PM +0200, markus reichelt wrote: > [...] > > Then you could use rsync (over ssh) for backup. This method is quite > > messy (setup, maintenance, ressources), but works. > > Since it's one(?) server and backup with pretty private info on it why not > spend > some time and set a proper VPN between the two? I am not worried about the file transfer to the backup machines. I dont fully (actually not at all) trust the backup machines. I cant restrict physical access to these machines and I am not the only one who has root on them. Theoretically, a secure whole disk encryption should deliver enought security even if the image is world readable, right? - Linux-crypto: cryptography in and on the Linux system Archive: http://mail.nl.linux.org/linux-crypto/ From linux-crypto-bounce@nl.linux.org Mon Jul 12 00:41:32 2004 Received: from localhost ([127.0.0.1] helo=humbolt) by humbolt.nl.linux.org with esmtp (Exim 4.22) id 1Bjmzd-0005aG-Jk; Mon, 12 Jul 2004 00:40:21 +0200 Received: with ECARTIS (v1.0.0; list linux-crypto); Mon, 12 Jul 2004 00:40:11 +0200 (CEST) Received: from imap.gmx.net ([213.165.64.20] helo=mail.gmx.net) by humbolt.nl.linux.org with smtp (Exim 4.22) id 1BjmzF-0005Vi-3W for linux-crypto@nl.linux.org; Mon, 12 Jul 2004 00:39:57 +0200 Received: (qmail 28159 invoked by uid 0); 11 Jul 2004 22:39:46 -0000 Received: from 80.171.34.184 by www54.gmx.net with HTTP; Mon, 12 Jul 2004 00:39:47 +0200 (MEST) Date: Mon, 12 Jul 2004 00:39:47 +0200 (MEST) From: a.engels@gmx.net To: "linux crypto" MIME-Version: 1.0 Subject: Re: Loop-AES, security concerns, stability of file backed loop-aes X-Priority: 3 (Normal) X-Authenticated: #2329190 Message-ID: <16277.1089585587@www54.gmx.net> X-Mailer: WWW-Mail 1.6 (Global Message Exchange) X-Flags: 0001 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Received-SPF: X-Spam-Status: No, hits=-3.3 required=5.0 tests=AWL,BAYES_10,NO_REAL_NAME,QUOTED_EMAIL_TEXT,RCVD_IN_ORBS version=2.55 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) X-ecartis-version: Ecartis v1.0.0 Sender: linux-crypto-bounce@nl.linux.org Errors-to: linux-crypto-bounce@nl.linux.org X-original-sender: a.engels@gmx.net Precedence: bulk List-help: List-unsubscribe: List-software: Ecartis version 1.0.0 List-Id: X-List-ID: List-subscribe: List-owner: List-post: List-archive: X-list: linux-crypto Thanks for the fast replies :) > Scientifically? Unfortunately not. Loop-AES is only secure if it has > been set up in multi-key mode with encrypted swap. Yes, I already read this from the docs. If all these options are activated, there is no attack possible (at least not yet known)? I need the highest possible security, because the backup servers are not trustworthy. I also read some pages about a (very theoretical) attack of AES. Does somebody have benchmarks for AES128, AES256 and other ciphers like twofish etc? Are the performance differences between these ciphers even noticeable on a P4 3 GHz running database services and Samba? > OTOH, don't know about your setup... a different approach could be to > split up your large data collection in smaller chunks (directorywise, > f.e.) tar/bzip2 'em up and use gpg to encrypt the *.tar.bz2. > > Additionally you could use rar to create archives with recovery > information, this comes in handy if network traffic somehow caused > corrupted files. The big disadvantage with gpg is that even slightly > corrupted encrypted files can't be decrypted. Therefore I use the > 'protective layer' of rar archives. :) > > Then you could use rsync (over ssh) for backup. This method is quite > messy (setup, maintenance, ressources), but works. I thought about such a solution, too, but it simply doesnt work in my case. See, my servers hold hunderts of gigabyte of data. If just 1 bit is changed, gpg would create a different encryption stream from this on => the gpg file is not rsyncable, so that each day my entire data would have to be transferred. Creating a gpg archive for each directory or even for each file would still be too inefficient, because I have very large database files with a size of multiple gbs. They are really good rsyncable when not encrypted. The aim would be to add real strong encryption and to keep the efficiency of rsync. Another question: how does loop-aes react on bad blocks? - Linux-crypto: cryptography in and on the Linux system Archive: http://mail.nl.linux.org/linux-crypto/ From linux-crypto-bounce@nl.linux.org Mon Jul 12 10:59:44 2004 Received: from localhost ([127.0.0.1] helo=humbolt) by humbolt.nl.linux.org with esmtp (Exim 4.22) id 1BjwdK-0004Yh-6h; Mon, 12 Jul 2004 10:57:58 +0200 Received: with ECARTIS (v1.0.0; list linux-crypto); Mon, 12 Jul 2004 10:57:52 +0200 (CEST) Received: from nelson.cdata.hu ([195.70.56.230]) by humbolt.nl.linux.org with esmtp (Exim 4.22) id 1Bjwd5-0004Y5-8h for linux-crypto@nl.linux.org; Mon, 12 Jul 2004 10:57:43 +0200 Received: from localhost (localhost [127.0.0.1]) by nelson.cdata.hu (Postfix) with ESMTP id 5ED3617DB0 for ; Mon, 12 Jul 2004 10:57:36 +0200 (CEST) Received: from nelson.cdata.hu ([127.0.0.1]) by localhost (nelson [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 26988-08 for ; Mon, 12 Jul 2004 10:57:34 +0200 (CEST) Received: by nelson.cdata.hu (Postfix, from userid 1019) id C52A317D7D; Mon, 12 Jul 2004 10:57:34 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by nelson.cdata.hu (Postfix) with ESMTP id B746F73187 for ; Mon, 12 Jul 2004 10:57:34 +0200 (CEST) Date: Mon, 12 Jul 2004 10:57:34 +0200 (CEST) From: "Gabor Kiss [Bitman]" Reply-To: kissg@cdata.hu Cc: linux crypto Subject: Re: Loop-AES, security concerns, stability of file backed loop-aes In-Reply-To: <16277.1089585587@www54.gmx.net> Message-ID: References: <16277.1089585587@www54.gmx.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by amavisd-new-20030616-p9 (Debian) at cdata.hu Received-SPF: X-Spam-Status: No, hits=-6.1 required=5.0 tests=BAYES_01,IN_REP_TO,QUOTED_EMAIL_TEXT,RCVD_IN_ORBS, REFERENCES,REPLY_WITH_QUOTES,USER_AGENT_PINE version=2.55 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) X-ecartis-version: Ecartis v1.0.0 Sender: linux-crypto-bounce@nl.linux.org Errors-to: linux-crypto-bounce@nl.linux.org X-original-sender: kissg@cdata.hu Precedence: bulk List-help: List-unsubscribe: List-software: Ecartis version 1.0.0 List-Id: X-List-ID: List-subscribe: List-owner: List-post: List-archive: X-list: linux-crypto > I thought about such a solution, too, but it simply doesnt work in my case. > See, my servers hold hunderts of gigabyte of data. If just 1 bit is changed, > gpg would create a different encryption stream from this on => the gpg file > is not rsyncable, so that each day my entire data would have to be > transferred. Creating a gpg archive for each directory or even for each file > would still be too inefficient, because I have very large database files > with a size of multiple gbs. They are really good rsyncable when not > encrypted. The aim would be to add real strong encryption and to keep the > efficiency of rsync. AFAIK loop-aes is fully transparent on block level I/O. It is not a stream cipher. Each disk block is encrypted independently on others. Am I wrong? Gabor - Linux-crypto: cryptography in and on the Linux system Archive: http://mail.nl.linux.org/linux-crypto/ From linux-crypto-bounce@nl.linux.org Mon Jul 12 17:26:30 2004 Received: from localhost ([127.0.0.1] helo=humbolt) by humbolt.nl.linux.org with esmtp (Exim 4.22) id 1Bk2fh-0006BY-Kh; Mon, 12 Jul 2004 17:24:49 +0200 Received: with ECARTIS (v1.0.0; list linux-crypto); Mon, 12 Jul 2004 17:24:42 +0200 (CEST) Received: from server133-han.de-nserver.de ([81.3.17.173]) by humbolt.nl.linux.org with esmtp (Exim 4.22) id 1Bk2fI-0006AJ-8g for linux-crypto@nl.linux.org; Mon, 12 Jul 2004 17:24:24 +0200 Received: (qmail 3198 invoked from network); 12 Jul 2004 15:23:59 -0000 Received: from unknown (HELO organic.homeip.net) (test@bitfalle.org@217.82.199.2) by server133-han.de-nserver.de with SMTP; 12 Jul 2004 15:23:59 -0000 Received: from localhost (localhost [127.0.0.1]) by organic.homeip.net (Postfix) with ESMTP id 27B2017556 for ; Mon, 12 Jul 2004 17:24:02 +0200 (CEST) Received: from organic.homeip.net ([127.0.0.1]) by localhost (organic.homeip.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 30058-10 for ; Mon, 12 Jul 2004 17:24:01 +0200 (CEST) Received: from tatooine.organic.net (tatooine.organic.net [192.168.0.26]) by organic.homeip.net (Postfix) with ESMTP id AAEDE1239E for ; Mon, 12 Jul 2004 17:24:01 +0200 (CEST) Received: by tatooine.organic.net (Postfix, from userid 500) id B8469168095; Mon, 12 Jul 2004 17:24:20 +0200 (CEST) Date: Mon, 12 Jul 2004 17:24:20 +0200 From: markus reichelt To: linux crypto Subject: Re: Loop-AES, security concerns, stability of file backed loop-aes Message-ID: <20040712152420.GB6155@lists.notified.de> Mail-Followup-To: linux crypto References: <16277.1089585587@www54.gmx.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; x-action=pgp-signed Content-Disposition: inline In-Reply-To: <16277.1089585587@www54.gmx.net> Organization: still stuck in reorganization mode X-Request-PGP: http://lists.notified.de/pubkey.mr.lists.asc User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new at organic.homeip.net Received-SPF: X-Spam-Status: No, hits=-11.2 required=5.0 tests=AWL,BAYES_01,EMAIL_ATTRIBUTION,IN_REP_TO,PGP_SIGNATURE, QUOTED_EMAIL_TEXT,RCVD_IN_ORBS,REFERENCES, REPLY_WITH_QUOTES,USER_AGENT_MUTT autolearn=ham version=2.55 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) X-ecartis-version: Ecartis v1.0.0 Sender: linux-crypto-bounce@nl.linux.org Errors-to: linux-crypto-bounce@nl.linux.org X-original-sender: mr@lists.notified.de Precedence: bulk List-help: List-unsubscribe: List-software: Ecartis version 1.0.0 List-Id: X-List-ID: List-subscribe: List-owner: List-post: List-archive: X-list: linux-crypto -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 a.engels@gmx.net wrote: > I need the highest possible security, because the backup servers are not > trustworthy. Then use loop-AES :) > I also read some pages about a (very theoretical) attack of AES. Does > somebody have benchmarks for AES128, AES256 and other ciphers like twofish > etc? Are the performance differences between these ciphers even noticeable > on a P4 3 GHz running database services and Samba? I don't have a link for benchmarks but would be interested in one though. By rule of thumb, you won't notice loop-AES on such a large machine if the server load is low/medium. AES is implemented in optimized assembler code. AES was picked because of its strength and speed. Serpent made 2nd place (it's considered slightly stronger than AES but slower - IIRC). > Another question: how does loop-aes react on bad blocks? Like bad physical sectors on hard disks? Nothing any soft can do about it. The data stored in those areas most likely can't be read/restored completely. That's bad enough, but with file system encryption each damaged sector is a total loss (IF I understand the working concept of loop-AES right). Jari will know for sure :) I consider myself lucky... haven't had to endure such a mess. A while ago I asked about worst case scenarios but aside from a hint to search the archives (doing so turned up negative), there was no reply. I take that as a good sign :-) - -- Bastard Administrator in $hell -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQFA8q0kLMyTO8Kj/uQRAuqLAJ9JqREpxoVgnXWKXTYXZVlu8h5fNgCfcJ8C PbF9IY03XaBPZkGz0mTtrgM= =lQJ8 -----END PGP SIGNATURE----- - Linux-crypto: cryptography in and on the Linux system Archive: http://mail.nl.linux.org/linux-crypto/ From linux-crypto-bounce@nl.linux.org Mon Jul 12 18:22:15 2004 Received: from localhost ([127.0.0.1] helo=humbolt) by humbolt.nl.linux.org with esmtp (Exim 4.22) id 1Bk3XV-0001mX-9c; Mon, 12 Jul 2004 18:20:25 +0200 Received: with ECARTIS (v1.0.0; list linux-crypto); Mon, 12 Jul 2004 18:20:18 +0200 (CEST) Received: from julius.godisch.de ([217.69.161.76] helo=mx.godisch.de) by humbolt.nl.linux.org with esmtp (Exim 4.22) id 1Bk3XB-0001ih-KK for linux-crypto@nl.linux.org; Mon, 12 Jul 2004 18:20:05 +0200 Received: from p508d0b43.dip0.t-ipconnect.de ([80.141.11.67] helo=carlos.godisch.de) by mx.godisch.de with asmtp (TLSv1:RC4-SHA:128) id 1Bk3WC-00017w-D6 for linux-crypto@nl.linux.org; Mon, 12 Jul 2004 18:19:04 +0200 Received: from godisch by carlos.godisch.de with local id 1Bk3WB-0001Kp-E6 for ; Mon, 12 Jul 2004 18:19:03 +0200 Date: Mon, 12 Jul 2004 18:19:03 +0200 From: Martin Godisch To: linux crypto Subject: Re: Loop-AES, security concerns, stability of file backed loop-aes Message-ID: <20040712161903.GA29583@carlos.godisch.de> Mail-Followup-To: linux crypto References: <15418.1089585536@www54.gmx.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <15418.1089585536@www54.gmx.net> X-GPG-ID: 0x68DCD606 X-GPG-Fingerprint: 2AB1 9CDD 4BA9 D7FB 6927 5A9E 9A91 821D 68DC D606 X-No-Archive: yes X-Debbugs-No-Ack: yes User-Agent: Mutt/1.5.6+20040523i Received-SPF: X-Spam-Status: No, hits=-8.6 required=5.0 tests=BAYES_01,EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT, RCVD_IN_NJABL,RCVD_IN_ORBS,REFERENCES,REPLY_WITH_QUOTES, USER_AGENT_MUTT autolearn=ham version=2.55 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) X-ecartis-version: Ecartis v1.0.0 Sender: linux-crypto-bounce@nl.linux.org Errors-to: linux-crypto-bounce@nl.linux.org X-original-sender: martin@godisch.de Precedence: bulk List-help: List-unsubscribe: List-software: Ecartis version 1.0.0 List-Id: X-List-ID: List-subscribe: List-owner: List-post: List-archive: X-list: linux-crypto On Mon, Jul 12, 2004 at 00:38:56 +0200, a.engels@gmx.net wrote: > I am not worried about the file transfer to the backup machines. I dont > fully (actually not at all) trust the backup machines. I cant restrict > physical access to these machines and I am not the only one who has root on > them. Theoretically, a secure whole disk encryption should deliver enought > security even if the image is world readable, right? What gains you an encrypted partition when there is another (evil) root on that machine while the partition is mounted? Encrypt your backup at home and put the tar.gz.gpg or something on the backup machine. Kind regards, Martin - Linux-crypto: cryptography in and on the Linux system Archive: http://mail.nl.linux.org/linux-crypto/ From linux-crypto-bounce@nl.linux.org Mon Jul 12 20:23:00 2004 Received: from localhost ([127.0.0.1] helo=humbolt) by humbolt.nl.linux.org with esmtp (Exim 4.22) id 1Bk5R9-00027K-Kh; Mon, 12 Jul 2004 20:21:59 +0200 Received: with ECARTIS (v1.0.0; list linux-crypto); Mon, 12 Jul 2004 20:21:52 +0200 (CEST) Received: from tarjoilu.luukku.com ([194.215.205.232]) by humbolt.nl.linux.org with esmtp (Exim 4.22) id 1Bk5Qn-000263-Tz for linux-crypto@nl.linux.org; Mon, 12 Jul 2004 20:21:37 +0200 Received: from localhost (mta1-o.i.luukku.com [10.0.1.112]) by mta1-o.i.luukku.com (Postfix) with ESMTP id 89B3581526; Mon, 12 Jul 2004 21:07:42 +0300 (EEST) Received: from users.sourceforge.net (3c13.yhteys.mtv3.fi [62.237.19.60]) by tarjoilu.luukku.com (Postfix) with ESMTP id B90F63AE288; Mon, 12 Jul 2004 21:07:41 +0300 (EEST) Message-ID: <40F2D38A.9582623F@users.sourceforge.net> Date: Mon, 12 Jul 2004 21:08:10 +0300 From: Jari Ruusu X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.4.22aa1r7 i686) X-Accept-Language: en MIME-Version: 1.0 To: a.engels@gmx.net Cc: linux-crypto@nl.linux.org Subject: Re: Loop-AES, security concerns, stability of file backed loop-aes References: <19923.1089562176@www69.gmx.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Received-SPF: X-Spam-Status: No, hits=-5.5 required=5.0 tests=AWL,BAYES_01,EMAIL_ATTRIBUTION,QUOTED_EMAIL_TEXT, RCVD_IN_ORBS,REFERENCES,REPLY_WITH_QUOTES, USER_AGENT_MOZILLA_XM version=2.55 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) X-ecartis-version: Ecartis v1.0.0 Sender: linux-crypto-bounce@nl.linux.org Errors-to: linux-crypto-bounce@nl.linux.org X-original-sender: jariruusu@users.sourceforge.net Precedence: bulk List-help: List-unsubscribe: List-software: Ecartis version 1.0.0 List-Id: X-List-ID: List-subscribe: List-owner: List-post: List-archive: X-list: linux-crypto a.engels@gmx.net wrote: > If I use ext3 on top of a file backed loop device, I understand that the > consistency is in danger because writes are reordered of the underlying fs. > What I dont understand is the claim, that ext3 (top) <-> loop-aes <-> ext3 > (underlying with data=ordered or data=journal) should work. Why is the > assumption correct that the underlying ext3 preserves the same write order > of the ext3 on top? Some older loop-AES README files said that ext3 -> loop -> file-on-ext3 (data=ordered or data=journal) should work. Newer versions of README advise to not use file backed loops at all. File backed loops may work under certain circumstances, but it is better to avoid using them. > I am not worried about the file transfer to the backup machines. I dont > fully (actually not at all) trust the backup machines. I cant restrict > physical access to these machines and I am not the only one who has root on > them. Theoretically, a secure whole disk encryption should deliver enought > security even if the image is world readable, right? loop-AES is still vulnerable to attacks that involve trojaning utilities used to mount and use encrypted file systems (losetup, mount, gpg, kernel+modules, init scripts, and other suid root programs). loop-AES is also vulnerable to attacker modifying ciphertext; ciphertext is not authenticated and attacker tampered ciphertext will decrypt without detection. It is possible for attacker to revert whole file system ciphertext to some earlier version (if attacker had access and saved old ciphertext). Also each individual 512 byte sector can be reverted to old state. It is possible to copy ciphertext of known plaintext to other sector, and only first 16 bytes of copied ciphertext will decrypt incorrectly. My point is: secure software crypto in rooted or otherwise insecure box is impossible to achieve. > Another question: how does loop-aes react on bad blocks? I/O errors of underlying device are reported to file system on top of loop device. It is up to file system to report I/O errors to applications. Errors resulting from damaged ciphertext (no I/O error detected by underlying device) stay in same 512 byte block where damaged ciphertext is and errors will not propagate to other sectors. -- Jari Ruusu 1024R/3A220F51 5B 4B F9 BB D3 3F 52 E9 DB 1D EB E3 24 0E A9 DD - Linux-crypto: cryptography in and on the Linux system Archive: http://mail.nl.linux.org/linux-crypto/ From linux-crypto-bounce@nl.linux.org Mon Jul 12 20:27:40 2004 Received: from localhost ([127.0.0.1] helo=humbolt) by humbolt.nl.linux.org with esmtp (Exim 4.22) id 1Bk5Vs-0002gQ-EO; Mon, 12 Jul 2004 20:26:52 +0200 Received: with ECARTIS (v1.0.0; list linux-crypto); Mon, 12 Jul 2004 20:26:45 +0200 (CEST) Received: from sasami.anime.net ([207.109.251.120]) by humbolt.nl.linux.org with esmtp (Exim 4.22) id 1Bk5Ve-0002fV-6A for linux-crypto@nl.linux.org; Mon, 12 Jul 2004 20:26:38 +0200 Received: from localhost (goemon@localhost) by sasami.anime.net (8.11.6/8.11.6) with ESMTP id i6CIQUS28694 for ; Mon, 12 Jul 2004 11:26:30 -0700 X-Antispam-Origin-Id: c4dc35da7d5d290438c6d6bdb17308d1 Date: Mon, 12 Jul 2004 11:26:30 -0700 (PDT) From: Dan Hollis To: linux-crypto@nl.linux.org Subject: loop-aes and amd64 In-Reply-To: <40F2D38A.9582623F@users.sourceforge.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Greylist: Message not sent from an IPv4 address, not delayed by milter-greylist-1.3.8 (sasami.anime.net [0.0.0.0]); Mon, 12 Jul 2004 11:26:30 -0700 (PDT) Received-SPF: X-Spam-Status: No, hits=-5.6 required=5.0 tests=AWL,BAYES_01,IN_REP_TO,RCVD_IN_ORBS,USER_AGENT_PINE version=2.55 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) X-ecartis-version: Ecartis v1.0.0 Sender: linux-crypto-bounce@nl.linux.org Errors-to: linux-crypto-bounce@nl.linux.org X-original-sender: goemon@anime.net Precedence: bulk List-help: List-unsubscribe: List-software: Ecartis version 1.0.0 List-Id: X-List-ID: List-subscribe: List-owner: List-post: List-archive: X-list: linux-crypto Are there plans for amd64 optimized loop-aes? -Dan - Linux-crypto: cryptography in and on the Linux system Archive: http://mail.nl.linux.org/linux-crypto/ From linux-crypto-bounce@nl.linux.org Mon Jul 12 20:49:54 2004 Received: from localhost ([127.0.0.1] helo=humbolt) by humbolt.nl.linux.org with esmtp (Exim 4.22) id 1Bk5rD-00049x-2d; Mon, 12 Jul 2004 20:48:55 +0200 Received: with ECARTIS (v1.0.0; list linux-crypto); Mon, 12 Jul 2004 20:48:48 +0200 (CEST) Received: from mato.luukku.com ([193.209.83.251]) by humbolt.nl.linux.org with esmtp (Exim 4.22) id 1Bk5qw-00049R-3W for linux-crypto@nl.linux.org; Mon, 12 Jul 2004 20:48:38 +0200 Received: from localhost (mta3-o.i.luukku.com [10.0.1.132]) by mta3-o.i.luukku.com (Postfix) with ESMTP id 85D72100360; Mon, 12 Jul 2004 21:41:26 +0300 (EEST) Received: from users.sourceforge.net (3c13.yhteys.mtv3.fi [62.237.19.60]) by mato.luukku.com (Postfix) with ESMTP id D8A6522EE89; Mon, 12 Jul 2004 21:41:25 +0300 (EEST) Message-ID: <40F2DB72.A6A25F4D@users.sourceforge.net> Date: Mon, 12 Jul 2004 21:41:54 +0300 From: Jari Ruusu X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.4.22aa1r7 i686) X-Accept-Language: en MIME-Version: 1.0 To: Dan Hollis Cc: linux-crypto@nl.linux.org Subject: Re: loop-aes and amd64 References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Received-SPF: X-Spam-Status: No, hits=-5.4 required=5.0 tests=AWL,BAYES_01,EMAIL_ATTRIBUTION,RCVD_IN_ORBS,REFERENCES, USER_AGENT_MOZILLA_XM version=2.55 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) X-ecartis-version: Ecartis v1.0.0 Sender: linux-crypto-bounce@nl.linux.org Errors-to: linux-crypto-bounce@nl.linux.org X-original-sender: jariruusu@users.sourceforge.net Precedence: bulk List-help: List-unsubscribe: List-software: Ecartis version 1.0.0 List-Id: X-List-ID: List-subscribe: List-owner: List-post: List-archive: X-list: linux-crypto Dan Hollis wrote: > Are there plans for amd64 optimized loop-aes? I have already implemented that. I'm waiting for Marcelo to release 2.4.27 kernel, and I then will release loop-AES-v2.1c that includes AMD64 optimized assembler implementations of AES and MD5. It is all tested and ready for release. AMD Opteron 1593.7 MHz, gcc-3.2.2 AES C implementation: key length 128 bits, encrypt speed 690.0 Mbits/s key length 128 bits, decrypt speed 711.8 Mbits/s key length 192 bits, encrypt speed 588.3 Mbits/s key length 192 bits, decrypt speed 607.4 Mbits/s key length 256 bits, encrypt speed 507.7 Mbits/s key length 256 bits, decrypt speed 527.0 Mbits/s AES assembler implementation: key length 128 bits, encrypt speed 1106.6 Mbits/s key length 128 bits, decrypt speed 1107.0 Mbits/s key length 192 bits, encrypt speed 932.3 Mbits/s key length 192 bits, decrypt speed 933.3 Mbits/s key length 256 bits, encrypt speed 807.8 Mbits/s key length 256 bits, decrypt speed 813.7 Mbits/s MD5 C implementation: md5 IV speed 1381.8 Mbits/sec MD5 assembler implementation: md5 IV speed 2367.1 Mbits/sec -- Jari Ruusu 1024R/3A220F51 5B 4B F9 BB D3 3F 52 E9 DB 1D EB E3 24 0E A9 DD - Linux-crypto: cryptography in and on the Linux system Archive: http://mail.nl.linux.org/linux-crypto/ From linux-crypto-bounce@nl.linux.org Tue Jul 13 00:24:06 2004 Received: from localhost ([127.0.0.1] helo=humbolt) by humbolt.nl.linux.org with esmtp (Exim 4.22) id 1Bk9CX-0004Jw-Jf; Tue, 13 Jul 2004 00:23:09 +0200 Received: with ECARTIS (v1.0.0; list linux-crypto); Tue, 13 Jul 2004 00:23:02 +0200 (CEST) Received: from mail.gmx.de ([213.165.64.20] helo=mail.gmx.net) by humbolt.nl.linux.org with smtp (Exim 4.22) id 1Bk9CH-0004D0-Dq for linux-crypto@nl.linux.org; Tue, 13 Jul 2004 00:22:53 +0200 Received: (qmail 777 invoked by uid 0); 12 Jul 2004 22:22:41 -0000 Received: from 213.39.198.36 by www43.gmx.net with HTTP; Tue, 13 Jul 2004 00:22:41 +0200 (MEST) Date: Tue, 13 Jul 2004 00:22:41 +0200 (MEST) From: a.engels@gmx.net To: linux-crypto@nl.linux.org MIME-Version: 1.0 References: <20040712161903.GA29583@carlos.godisch.de> Subject: Re: Loop-AES, security concerns, stability of file backed loop-aes X-Priority: 3 (Normal) X-Authenticated: #2329190 Message-ID: <6104.1089670961@www43.gmx.net> X-Mailer: WWW-Mail 1.6 (Global Message Exchange) X-Flags: 0001 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Received-SPF: X-Spam-Status: No, hits=-1.8 required=5.0 tests=BAYES_20,NO_REAL_NAME,QUOTED_EMAIL_TEXT,RCVD_IN_ORBS, REFERENCES version=2.55 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) X-ecartis-version: Ecartis v1.0.0 Sender: linux-crypto-bounce@nl.linux.org Errors-to: linux-crypto-bounce@nl.linux.org X-original-sender: a.engels@gmx.net Precedence: bulk List-help: List-unsubscribe: List-software: Ecartis version 1.0.0 List-Id: X-List-ID: List-subscribe: List-owner: List-post: List-archive: X-list: linux-crypto > > I am not worried about the file transfer to the backup machines. I dont > > fully (actually not at all) trust the backup machines. I cant restrict > > physical access to these machines and I am not the only one who has root > on > > them. Theoretically, a secure whole disk encryption should deliver > enought > > security even if the image is world readable, right? > > What gains you an encrypted partition when there is another (evil) root > on that machine while the partition is mounted? Encrypt your backup at > home and put the tar.gz.gpg or something on the backup machine. I never said that these images are mounted on the backup server. Images are just stored there. - Linux-crypto: cryptography in and on the Linux system Archive: http://mail.nl.linux.org/linux-crypto/ From linux-crypto-bounce@nl.linux.org Tue Jul 13 00:36:52 2004 Received: from localhost ([127.0.0.1] helo=humbolt) by humbolt.nl.linux.org with esmtp (Exim 4.22) id 1Bk9Oz-0005L0-Cp; Tue, 13 Jul 2004 00:36:01 +0200 Received: with ECARTIS (v1.0.0; list linux-crypto); Tue, 13 Jul 2004 00:35:35 +0200 (CEST) Received: from mail.gmx.net ([213.165.64.20]) by humbolt.nl.linux.org with smtp (Exim 4.22) id 1Bk9OQ-0005KB-5D for linux-crypto@nl.linux.org; Tue, 13 Jul 2004 00:35:26 +0200 Received: (qmail 945 invoked by uid 0); 12 Jul 2004 22:35:15 -0000 Received: from 213.39.198.36 by www56.gmx.net with HTTP; Tue, 13 Jul 2004 00:35:15 +0200 (MEST) Date: Tue, 13 Jul 2004 00:35:15 +0200 (MEST) From: a.engels@gmx.net To: "linux crypto" MIME-Version: 1.0 Subject: Re: Loop-AES, security concerns, stability of file backed loop-aes X-Priority: 3 (Normal) X-Authenticated: #2329190 Message-ID: <13689.1089671715@www56.gmx.net> X-Mailer: WWW-Mail 1.6 (Global Message Exchange) X-Flags: 0001 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Received-SPF: X-Spam-Status: No, hits=-2.8 required=5.0 tests=AWL,BAYES_10,NO_REAL_NAME,QUOTED_EMAIL_TEXT,RCVD_IN_ORBS version=2.55 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) X-ecartis-version: Ecartis v1.0.0 Sender: linux-crypto-bounce@nl.linux.org Errors-to: linux-crypto-bounce@nl.linux.org X-original-sender: a.engels@gmx.net Precedence: bulk List-help: List-unsubscribe: List-software: Ecartis version 1.0.0 List-Id: X-List-ID: List-subscribe: List-owner: List-post: List-archive: X-list: linux-crypto > > I also read some pages about a (very theoretical) attack of AES. Does > > somebody have benchmarks for AES128, AES256 and other ciphers like > twofish > > etc? Are the performance differences between these ciphers even > noticeable > > on a P4 3 GHz running database services and Samba? > > I don't have a link for benchmarks but would be interested in one > though. By rule of thumb, you won't notice loop-AES on such a large > machine if the server load is low/medium. AES is implemented in > optimized assembler code. > > AES was picked because of its strength and speed. Serpent made 2nd > place (it's considered slightly stronger than AES but slower - IIRC). Yes, but if I read the source code correctly, only AES128 is asm pentium optimized, not AES256. For security of AES and Serpent have a look at: http://www.cryptosystem.net/aes/ If speed isnt really a problem with modern hardware, it would be nice to know the opinion of crypto analysts which one the safest cipher is according to current knowledge. - Linux-crypto: cryptography in and on the Linux system Archive: http://mail.nl.linux.org/linux-crypto/ From linux-crypto-bounce@nl.linux.org Tue Jul 13 01:01:31 2004 Received: from localhost ([127.0.0.1] helo=humbolt) by humbolt.nl.linux.org with esmtp (Exim 4.22) id 1Bk9mn-0006u7-Bh; Tue, 13 Jul 2004 01:00:37 +0200 Received: with ECARTIS (v1.0.0; list linux-crypto); Tue, 13 Jul 2004 01:00:29 +0200 (CEST) Received: from mail.gmx.de ([213.165.64.20] helo=mail.gmx.net) by humbolt.nl.linux.org with smtp (Exim 4.22) id 1Bk9mT-0006tD-3W for linux-crypto@nl.linux.org; Tue, 13 Jul 2004 01:00:17 +0200 Received: (qmail 22415 invoked by uid 0); 12 Jul 2004 23:00:06 -0000 Received: from 213.39.198.36 by www56.gmx.net with HTTP; Tue, 13 Jul 2004 01:00:07 +0200 (MEST) Date: Tue, 13 Jul 2004 01:00:07 +0200 (MEST) From: a.engels@gmx.net To: "linux crypto" MIME-Version: 1.0 Subject: Re: Loop-AES, security concerns, stability of file backed loop-aes X-Priority: 3 (Normal) X-Authenticated: #2329190 Message-ID: <11527.1089673207@www56.gmx.net> X-Mailer: WWW-Mail 1.6 (Global Message Exchange) X-Flags: 0001 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Received-SPF: X-Spam-Status: No, hits=-3.4 required=5.0 tests=AWL,BAYES_10,NO_REAL_NAME,QUOTED_EMAIL_TEXT,RCVD_IN_ORBS version=2.55 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) X-ecartis-version: Ecartis v1.0.0 Sender: linux-crypto-bounce@nl.linux.org Errors-to: linux-crypto-bounce@nl.linux.org X-original-sender: a.engels@gmx.net Precedence: bulk List-help: List-unsubscribe: List-software: Ecartis version 1.0.0 List-Id: X-List-ID: List-subscribe: List-owner: List-post: List-archive: X-list: linux-crypto Hi Jari! > Some older loop-AES README files said that ext3 -> loop -> file-on-ext3 > (data=ordered or data=journal) should work. Newer versions of README > advise > to not use file backed loops at all. File backed loops may work under > certain circumstances, but it is better to avoid using them. I just had another idea which would fit my needs: ext3 -> loop-aes -> software raid1 -> hda1,hdb1 + loop (without encryption) -> file on ext3 Each time I want to backup my data, I do a raidhotadd of the loop device. I wait until it is rebuild using the data from the partions hda1, hdb1. If the rebuild is finished, I create a consistent state of the file system by terminating samba and data base engines. I do a raidhotremove of the loop device and have a perfect snapshot. In case of restore, I would use the loop device to rebuild the partitions. Would this scenario work? > > > I am not worried about the file transfer to the backup machines. I dont > > fully (actually not at all) trust the backup machines. I cant restrict > > physical access to these machines and I am not the only one who has root > on > > them. Theoretically, a secure whole disk encryption should deliver > enought > > security even if the image is world readable, right? > > loop-AES is still vulnerable to attacks that involve trojaning utilities > used to mount and use encrypted file systems (losetup, mount, gpg, > kernel+modules, init scripts, and other suid root programs). Right, I just forgot to point out, that the images are of course not mounted on the backup servers. > loop-AES is also vulnerable to attacker modifying ciphertext; ciphertext > is > not authenticated and attacker tampered ciphertext will decrypt without > detection. It is possible for attacker to revert whole file system > ciphertext to some earlier version (if attacker had access and saved old > ciphertext). Also each individual 512 byte sector can be reverted to old > state. It is possible to copy ciphertext of known plaintext to other > sector, > and only first 16 bytes of copied ciphertext will decrypt incorrectly. Nice, I havent thought of this possibility. Maybe one could store a md5 checksum of the crypto container inside the crypto container itself and check consistency when the fs is mounted. However, this would mean to read the entire crypto container at each mount. Adding checksums to each block (checksum also includes position of block) would be another way. - Linux-crypto: cryptography in and on the Linux system Archive: http://mail.nl.linux.org/linux-crypto/ From linux-crypto-bounce@nl.linux.org Tue Jul 13 01:08:13 2004 Received: from localhost ([127.0.0.1] helo=humbolt) by humbolt.nl.linux.org with esmtp (Exim 4.22) id 1Bk9tR-0008E6-5P; Tue, 13 Jul 2004 01:07:29 +0200 Received: with ECARTIS (v1.0.0; list linux-crypto); Tue, 13 Jul 2004 01:07:22 +0200 (CEST) Received: from pop.gmx.de ([213.165.64.20] helo=mail.gmx.net) by humbolt.nl.linux.org with smtp (Exim 4.22) id 1Bk9tD-0008Ce-4E for linux-crypto@nl.linux.org; Tue, 13 Jul 2004 01:07:15 +0200 Received: (qmail 28081 invoked by uid 0); 12 Jul 2004 23:07:02 -0000 Received: from 213.39.198.36 by www42.gmx.net with HTTP; Tue, 13 Jul 2004 01:07:02 +0200 (MEST) Date: Tue, 13 Jul 2004 01:07:02 +0200 (MEST) From: a.engels@gmx.net To: "linux crypto" MIME-Version: 1.0 Subject: Re: Loop-AES, security concerns, stability of file backed loop-aes X-Priority: 3 (Normal) X-Authenticated: #2329190 Message-ID: <12708.1089673622@www42.gmx.net> X-Mailer: WWW-Mail 1.6 (Global Message Exchange) X-Flags: 0001 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Received-SPF: X-Spam-Status: No, hits=-3.5 required=5.0 tests=AWL,BAYES_10,NO_REAL_NAME,QUOTED_EMAIL_TEXT,RCVD_IN_ORBS version=2.55 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) X-ecartis-version: Ecartis v1.0.0 Sender: linux-crypto-bounce@nl.linux.org Errors-to: linux-crypto-bounce@nl.linux.org X-original-sender: a.engels@gmx.net Precedence: bulk List-help: List-unsubscribe: List-software: Ecartis version 1.0.0 List-Id: X-List-ID: List-subscribe: List-owner: List-post: List-archive: X-list: linux-crypto > Nice, I havent thought of this possibility. Maybe one could store a md5 > checksum of the crypto container inside the crypto container itself and > check consistency when the fs is mounted. However, this would mean to read > the entire crypto container at each mount. Adding checksums to each block > (checksum also includes position of block) would be another way. I need to correct myself: if the last method is used, its not possible to move blocks inside the crypto container, however an elder version of this block could be used to overwrite the new one without notice. - Linux-crypto: cryptography in and on the Linux system Archive: http://mail.nl.linux.org/linux-crypto/ From linux-crypto-bounce@nl.linux.org Tue Jul 13 01:50:35 2004 Received: from localhost ([127.0.0.1] helo=humbolt) by humbolt.nl.linux.org with esmtp (Exim 4.22) id 1BkAY9-0001Vu-Ix; Tue, 13 Jul 2004 01:49:33 +0200 Received: with ECARTIS (v1.0.0; list linux-crypto); Tue, 13 Jul 2004 01:49:26 +0200 (CEST) Received: from mailfarm.berkeley.edu ([128.32.61.106] helo=calmail-fe1.berkeley.edu) by humbolt.nl.linux.org with esmtp (Exim 4.22) id 1BkAXr-0001V0-B0 for linux-crypto@nl.linux.org; Tue, 13 Jul 2004 01:49:15 +0200 Received: from [64.2.57.148] (account pavpen@calmail.berkeley.edu HELO smash) by calmail-fe1.berkeley.edu (CommuniGate Pro SMTP 4.1.8) with ESMTP-TLS id 3187337 for linux-crypto@nl.linux.org; Mon, 12 Jul 2004 16:49:01 -0700 Received: from r by smash with local (Exim 4.34) id 1BkAXb-0005ka-HB for linux-crypto@nl.linux.org; Mon, 12 Jul 2004 16:48:59 -0700 Date: Mon, 12 Jul 2004 16:48:59 -0700 From: Pavel Minev Penev To: linux crypto Subject: Re: Loop-AES, security concerns, stability of file backed loop-aes Message-ID: <20040712234859.GA22035@smash> Reply-To: linux-crypto@nl.linux.org Mail-Followup-To: linux crypto References: <12708.1089673622@www42.gmx.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <12708.1089673622@www42.gmx.net> User-Agent: Mutt/1.5.6+20040523i X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: pavpen@berkeley.edu X-SA-Exim-Scanned: No (on smash); SAEximRunCond expanded to false Received-SPF: X-Spam-Status: No, hits=-9.9 required=5.0 tests=BAYES_01,EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT, RCVD_IN_ORBS,REFERENCES,REPLY_WITH_QUOTES, SIGNATURE_LONG_SPARSE,USER_AGENT_MUTT autolearn=ham version=2.55 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) X-ecartis-version: Ecartis v1.0.0 Sender: linux-crypto-bounce@nl.linux.org Errors-to: linux-crypto-bounce@nl.linux.org X-original-sender: pavpen@berkeley.edu Precedence: bulk List-help: List-unsubscribe: List-software: Ecartis version 1.0.0 List-Id: X-List-ID: List-subscribe: List-owner: List-post: List-archive: X-list: linux-crypto On Tue, Jul 13, 2004 at 01:07:02AM +0200, a.engels@gmx.net wrote: > > Nice, I havent thought of this possibility. Maybe one could store a md5 > > checksum of the crypto container inside the crypto container itself and > > check consistency when the fs is mounted. However, this would mean to read > > the entire crypto container at each mount. Adding checksums to each block > > (checksum also includes position of block) would be another way. > > I need to correct myself: if the last method is used, its not possible to > move blocks inside the crypto container, however an elder version of this > block could be used to overwrite the new one without notice. A combination of the two methods might be of some use though. You can checksum each block, and then checksum the checksums (will speed up checksum verification of the whole filesystem by some [large] factor). You may not notice a modified block at mount if an attacker preserves its checksum, but if you verify each block's checksum before reading and maybe writing (caching, of course) you should not be tricked into using a modified block. Thougt, -- Pav http://www.againsttcpa.com/ ,., My type: Dvorak. http://swpat.ffii.org/ ,``:'', {o ! o} Gain your human right of ] -+- [ My GPG/PGP key is now available at privacy: use cryptography! \ ! / x-hkp://search.keyserver.net:11371. `-' `shell$ gpg --keyserver x-hkp://search.keyserver.net:11371 --recv-key 164C028F` - Linux-crypto: cryptography in and on the Linux system Archive: http://mail.nl.linux.org/linux-crypto/ From linux-crypto-bounce@nl.linux.org Tue Jul 13 08:51:26 2004 Received: from localhost ([127.0.0.1] helo=humbolt) by humbolt.nl.linux.org with esmtp (Exim 4.22) id 1BkH6e-0005cK-G4; Tue, 13 Jul 2004 08:49:36 +0200 Received: with ECARTIS (v1.0.0; list linux-crypto); Tue, 13 Jul 2004 08:49:29 +0200 (CEST) Received: from david.siemens.gr ([212.251.43.203]) by humbolt.nl.linux.org with esmtp (Exim 4.22) id 1BkH6Q-0005bW-Lr for linux-crypto@nl.linux.org; Tue, 13 Jul 2004 08:49:22 +0200 Received: from mail.siemens.gr (mail.siemens.gr [141.29.40.244]) by david.siemens.gr (8.12.6/8.12.6) with ESMTP id i6D6nBoq021595 for ; Tue, 13 Jul 2004 08:49:11 +0200 Received: from poseidon.siemens.gr (poseidon.siemens.gr [141.29.40.250]) by mail.siemens.gr (8.12.6/8.12.6) with ESMTP id i6D6n5fo022437 for ; Tue, 13 Jul 2004 08:49:11 +0200 Received: by Poseidon with Internet Mail Service (5.5.2657.72) id <3Z8S6XTX>; Tue, 13 Jul 2004 09:44:15 +0300 Message-ID: <87ABB70ACC0FD6119F280800062B398E83E859@Poseidon> From: Nanopoulou Stella To: linux-crypto@nl.linux.org Subject: =?iso-8859-7?Q?=C1=F5=F4=FC=EC=E1=F4=E7_=C1=F0=DC=ED=F4=E7=F3=E7?= =?iso-8859-7?Q?=3A_Hello?= Date: Tue, 13 Jul 2004 09:44:14 +0300 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain; charset="windows-1253" Received-SPF: X-Spam-Status: No, hits=0.1 required=5.0 tests=RCVD_IN_ORBS version=2.55 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) X-ecartis-version: Ecartis v1.0.0 Sender: linux-crypto-bounce@nl.linux.org Errors-to: linux-crypto-bounce@nl.linux.org X-original-sender: stella.nanopoulou@siemens.com Precedence: bulk List-help: List-unsubscribe: List-software: Ecartis version 1.0.0 List-Id: X-List-ID: List-subscribe: List-owner: List-post: List-archive: X-list: linux-crypto Dear all, I will be out of office from 12th of July until the 26th of July. Thank you, Stella Nanopoulou - Linux-crypto: cryptography in and on the Linux system Archive: http://mail.nl.linux.org/linux-crypto/ From linux-crypto-bounce@nl.linux.org Tue Jul 13 09:25:39 2004 Received: from localhost ([127.0.0.1] helo=humbolt) by humbolt.nl.linux.org with esmtp (Exim 4.22) id 1BkHe8-0000TA-Es; Tue, 13 Jul 2004 09:24:12 +0200 Received: with ECARTIS (v1.0.0; list linux-crypto); Tue, 13 Jul 2004 09:24:02 +0200 (CEST) Received: from server133-han.de-nserver.de ([81.3.17.173]) by humbolt.nl.linux.org with esmtp (Exim 4.22) id 1BkHdc-0000QQ-QX for linux-crypto@nl.linux.org; Tue, 13 Jul 2004 09:23:40 +0200 Received: (qmail 8101 invoked from network); 13 Jul 2004 07:23:21 -0000 Received: from unknown (HELO organic.homeip.net) (test@bitfalle.org@217.82.206.159) by server133-han.de-nserver.de with SMTP; 13 Jul 2004 07:23:21 -0000 Received: from localhost (localhost [127.0.0.1]) by organic.homeip.net (Postfix) with ESMTP id F0247142B0 for ; Tue, 13 Jul 2004 09:23:21 +0200 (CEST) Received: from organic.homeip.net ([127.0.0.1]) by localhost (organic.homeip.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 28778-09 for ; Tue, 13 Jul 2004 09:23:21 +0200 (CEST) Received: from tatooine.organic.net (tatooine.organic.net [192.168.0.26]) by organic.homeip.net (Postfix) with ESMTP id 4046F142AE for ; Tue, 13 Jul 2004 09:23:21 +0200 (CEST) Received: by tatooine.organic.net (Postfix, from userid 500) id 6AABF168095; Tue, 13 Jul 2004 09:23:48 +0200 (CEST) Date: Tue, 13 Jul 2004 09:23:48 +0200 From: markus reichelt To: linux crypto Subject: Re: Loop-AES, security concerns, stability of file backed loop-aes Message-ID: <20040713072348.GA2111@lists.notified.de> Mail-Followup-To: linux crypto References: <13689.1089671715@www56.gmx.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; x-action=pgp-signed Content-Disposition: inline In-Reply-To: <13689.1089671715@www56.gmx.net> Organization: still stuck in reorganization mode X-Request-PGP: http://lists.notified.de/pubkey.mr.lists.asc User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new at organic.homeip.net Received-SPF: X-Spam-Status: No, hits=-11.0 required=5.0 tests=AWL,BAYES_10,EMAIL_ATTRIBUTION,IN_REP_TO,PGP_SIGNATURE, QUOTED_EMAIL_TEXT,RCVD_IN_ORBS,REFERENCES, REPLY_WITH_QUOTES,USER_AGENT_MUTT autolearn=ham version=2.55 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) X-ecartis-version: Ecartis v1.0.0 Sender: linux-crypto-bounce@nl.linux.org Errors-to: linux-crypto-bounce@nl.linux.org X-original-sender: mr@lists.notified.de Precedence: bulk List-help: List-unsubscribe: List-software: Ecartis version 1.0.0 List-Id: X-List-ID: List-subscribe: List-owner: List-post: List-archive: X-list: linux-crypto -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 a.engels@gmx.net wrote: > For security of AES and Serpent have a look at: > http://www.cryptosystem.net/aes/ Bookmark set. I didn't know about aes4 conference, sadly, it took place right next door. Next time :) > If speed isnt really a problem with modern hardware, it would be nice to > know the opinion of crypto analysts which one the safest cipher is according > to current knowledge. I agree... but maybe we won't get an answer here. So, have you considered directly writing some cryptanalysts about it? - -- Bastard Administrator in $hell -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQFA844ELMyTO8Kj/uQRAorfAJ0SLIEx/p0Rt0crhoFkE8/SSIXFSACgg/e6 Gzi0W0rD5CK6e1DGXr8yeVU= =VW9N -----END PGP SIGNATURE----- - Linux-crypto: cryptography in and on the Linux system Archive: http://mail.nl.linux.org/linux-crypto/ From linux-crypto-bounce@nl.linux.org Tue Jul 13 12:49:21 2004 Received: from localhost ([127.0.0.1] helo=humbolt) by humbolt.nl.linux.org with esmtp (Exim 4.22) id 1BkKpU-00083R-1g; Tue, 13 Jul 2004 12:48:08 +0200 Received: with ECARTIS (v1.0.0; list linux-crypto); Tue, 13 Jul 2004 12:48:01 +0200 (CEST) Received: from imap.gmx.net ([213.165.64.20] helo=mail.gmx.net) by humbolt.nl.linux.org with smtp (Exim 4.22) id 1BkKpG-000809-Pc for linux-crypto@nl.linux.org; Tue, 13 Jul 2004 12:47:54 +0200 Received: (qmail 32566 invoked by uid 0); 13 Jul 2004 10:47:44 -0000 Received: from 213.39.148.107 by www50.gmx.net with HTTP; Tue, 13 Jul 2004 12:47:44 +0200 (MEST) Date: Tue, 13 Jul 2004 12:47:44 +0200 (MEST) From: a.engels@gmx.net To: "linux crypto" MIME-Version: 1.0 Subject: Re: Loop-AES, security concerns, stability of file backed loop-aes X-Priority: 3 (Normal) X-Authenticated: #2329190 Message-ID: <15656.1089715664@www50.gmx.net> X-Mailer: WWW-Mail 1.6 (Global Message Exchange) X-Flags: 0001 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Received-SPF: X-Spam-Status: No, hits=-2.6 required=5.0 tests=AWL,BAYES_20,NO_REAL_NAME,QUOTED_EMAIL_TEXT,RCVD_IN_ORBS version=2.55 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) X-ecartis-version: Ecartis v1.0.0 Sender: linux-crypto-bounce@nl.linux.org Errors-to: linux-crypto-bounce@nl.linux.org X-original-sender: a.engels@gmx.net Precedence: bulk List-help: List-unsubscribe: