AES256

tuxman · 2005-11-16 00:14:36

hi,
does Arch include the AES256 loop and , if it doesn't, is there a way to install it?
I use AES256 to create a small encrypted file on a USB pendrive on Debian and would like to do the same using Arch.

Thanks

tuxman · 2005-11-21 00:48:06

I know this is very basic but hey, here we go.
I tried to install loop-AES on arch, downloaded the tar.bz2 package and the suggested library

aespipe-latest.tar.bz2
loop-AES-latest.tar.bz2

then I went through the usual procedure

#tar -xjf aespipe-latest.tar.bz2
#cd aespipe-v2.3b
#./configure
#make
#make install

so far so good, then

#tar -xjf loop-AES-latest.tar.bz2
#cd loop-AES-v3.1b

now there is no configure file in the direcotry so i cant go on
with the install.
what would be the correct procedure to install loop-AES?

thanks

Snowman · 2005-11-21 03:58:18

tuxman wrote:

now there is no configure file in the direcotry so i cant go on
with the install.
what would be the correct procedure to install loop-AES?

Is there a Makefile in the directory?

tuxman · 2005-11-21 04:51:21

yes, should I skip ./configure?

Snowman · 2005-11-21 05:13:41

Yes. Just run:
# make
# make install

If that doesn't work, post the error message.

tuxman · 2005-11-21 05:20:24

tahnks,
I tried make and then make install and then got this error emssage:

make[2]: *** [loop.ko] Error 134
make[1]: *** [modules] Error 2
make[1]: Leaving directory `/usr/src/linux-2.6.13-ARCH'
make: *** [all] Error 2
[root@tuxman loop-AES-v3.1b]# make install
make: *** No rule to make target `install'. Stop.
[root@tuxman loop-AES-v3.1b]#

tuxman · 2005-11-21 05:26:05

by the way, loop-AES is such a great and versatile tool for Linux I think it should be among the arch packages.
I have seen it's in AUR, unfortunatedly I dont know how to use it.
LOL

soloport · 2005-11-21 05:35:01

Have installed loop-AES on a few Arch boxes. Not sure how far you want to go with it, though.

For example, have installed loop-AES for several mortgage brokers and banks so they could keep personal information (SSN, and other ID) on their central file servers and not worry about theft.

Have a set of scripts I run after an Arch install that automates the setup (if you're interested).

Snowman · 2005-11-21 07:10:27

tuxman wrote:

tahnks,
I tried make and then make install and then got this error emssage:
make[2]: *** [loop.ko] Error 134
make[1]: *** [modules] Error 2
make[1]: Leaving directory `/usr/src/linux-2.6.13-ARCH'
make: *** [all] Error 2

This is not really the error message. Look at the output before what you posted. There's probably a better description of the error in it.

tuxman · 2005-11-21 18:32:51

hi,
as you say, the first part might not be an error, I posted it just to make sure.
where I get a problem is when I try the make install command

[root@tuxman loop-AES-v3.1b]# make install
make: *** No rule to make target `install'. Stop.
[root@tuxman loop-AES-v3.1b]#

I dont know what "No rule to make target install" means of if I am missing something.

Regarding my use for loop-AES, I basically use it to read an encrypted file I use as backup on a USB drive, Knoppix style.
As Im migrating to Arch, Im trying to get the same functionality.

Snowman · 2005-11-21 19:22:18

You first need to fix the errors that you get when you run
# make
Run make, check the output and post the error messages.

We'll worry about make install afterwards.

tuxman · 2005-11-21 21:50:09

Thanks Snowman.

here goes what happens when I try the make command

[root@tuxman loop-AES-v3.1b]# make
cd /usr/src/linux-2.6.13-ARCH && make SUBDIRS=/root/loop-AES-v3.1b modules Q='@cd /root/loop-AES-v3.1b && if [ "$@" = "modules" ]; then make modules; fi; # '
make[1]: Entering directory `/usr/src/linux-2.6.13-ARCH'
Building modules, stage 2.
rm -f *.o *.ko *.orig *.rej *.mod.c patched-loop.[ch] test-file[1234]
rm -f -r test-dir1 tmp-d-kbuild
rm -f patched-loop.[ch]
cp loop.c-2.6.patched patched-loop.c
cd /usr/src/linux-2.6.13-ARCH && gcc -m32 -nostdinc -isystem /usr/lib/gcc/i686-pc-linux-gnu/4.0.3/include -D__KERNEL__ -Iinclude -Wall -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -ffreestanding -O2 -fomit-frame-pointer -pipe -msoft-float -mpreferred-stack-boundary=2 -fno-unit-at-a-time -march=i686 -Iinclude/asm-i386/mach-default -Wdeclaration-after-statement -Wno-pointer-sign -DMODULE -DOLD_REQUEST_MODULE_INTERFACE -DX86_ASM -DKBUILD_BASENAME=patched_loop -DKBUILD_MODNAME=loop -DEXPORT_SYMTAB -c /root/loop-AES-v3.1b/patched-loop.c -o /root/loop-AES-v3.1b/patched-loop.o
cd /usr/src/linux-2.6.13-ARCH && gcc -m32 -nostdinc -isystem /usr/lib/gcc/i686-pc-linux-gnu/4.0.3/include -D__KERNEL__ -Iinclude -Wall -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -ffreestanding -O2 -fomit-frame-pointer -pipe -msoft-float -mpreferred-stack-boundary=2 -fno-unit-at-a-time -march=i686 -Iinclude/asm-i386/mach-default -Wdeclaration-after-statement -Wno-pointer-sign -DMODULE -DOLD_REQUEST_MODULE_INTERFACE -DX86_ASM -DKBUILD_BASENAME=glue -DKBUILD_MODNAME=loop -c /root/loop-AES-v3.1b/glue.c -o /root/loop-AES-v3.1b/glue.o
cd /usr/src/linux-2.6.13-ARCH && gcc -m32 -D__ASSEMBLY__ -Iinclude/asm-i386/mach-default -c /root/loop-AES-v3.1b/aes-x86.S -o /root/loop-AES-v3.1b/aes-x86.o
cd /usr/src/linux-2.6.13-ARCH && gcc -m32 -D__ASSEMBLY__ -Iinclude/asm-i386/mach-default -c /root/loop-AES-v3.1b/md5-x86.S -o /root/loop-AES-v3.1b/md5-x86.o
ld -m elf_i386 -m elf_i386 -r patched-loop.o glue.o aes-x86.o md5-x86.o -o loop.o
cd /usr/src/linux-2.6.13-ARCH && ./scripts/mod/modpost vmlinux /root/loop-AES-v3.1b/loop.o >/dev/null 2>&1
/bin/sh: line 1: 5411 Aborted ./scripts/mod/modpost vmlinux /root/loop-AES-v3.1b/loop.o >/dev/null 2>&1
make[2]: *** [loop.ko] Error 134
make[1]: *** [modules] Error 2
make[1]: Leaving directory `/usr/src/linux-2.6.13-ARCH'
make: *** [all] Error 2
[root@tuxman loop-AES-v3.1b]#

tuxman · 2005-11-22 01:29:13

this is the output of the make on another archlinux box.

[root@myhost loop-AES-v3.1b]# make
cd /usr/src/linux-2.6.10-ARCH && make SUBDIRS=/root/loop-AES-v3.1b modules Q='@c d /root/loop-AES-v3.1b && if [ "$@" = "modules" ]; then make modules; fi; # '
make[1]: Entering directory `/usr/src/linux-2.6.10-ARCH'
Building modules, stage 2.
rm -f *.o *.ko *.orig *.rej *.mod.c patched-loop.[ch] test-file[1234]
rm -f -r test-dir1 tmp-d-kbuild
rm -f patched-loop.[ch]
cp loop.c-2.6.patched patched-loop.c
cd /usr/src/linux-2.6.10-ARCH && gcc -nostdinc -iwithprefix include -D__KERNEL__ -Iinclude -Wall -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-c ommon -O2 -fomit-frame-pointer -pipe -msoft-float -mpreferred-stack-boundary =2 -fno-unit-at-a-time -march=i686 -Iinclude/asm-i386/mach-default -Wdeclaration -after-statement -DMODULE -DOLD_REQUEST_MODULE_INTERFACE -DX86_ASM -DKBUILD_BA SENAME=patched_loop -DKBUILD_MODNAME=loop -DEXPORT_SYMTAB -c /root/loop-AES-v3.1 b/patched-loop.c -o /root/loop-AES-v3.1b/patched-loop.o
/root/loop-AES-v3.1b/patched-loop.c:211: warning: pointer targets in initializat ion differ in signedness
cd /usr/src/linux-2.6.10-ARCH && gcc -nostdinc -iwithprefix include -D__KERNEL__ -Iinclude -Wall -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-c ommon -O2 -fomit-frame-pointer -pipe -msoft-float -mpreferred-stack-boundary =2 -fno-unit-at-a-time -march=i686 -Iinclude/asm-i386/mach-default -Wdeclaration -after-statement -DMODULE -DOLD_REQUEST_MODULE_INTERFACE -DX86_ASM -DKBUILD_BA SENAME=glue -DKBUILD_MODNAME=loop -c /root/loop-AES-v3.1b/glue.c -o /root/loop-A ES-v3.1b/glue.o
/root/loop-AES-v3.1b/glue.c: In function 'transfer_aes':
/root/loop-AES-v3.1b/glue.c:486: warning: pointer targets in passing argument 2 of 'aes_decrypt' differ in signedness
/root/loop-AES-v3.1b/glue.c:486: warning: pointer targets in passing argument 3 of 'aes_decrypt' differ in signedness
/root/loop-AES-v3.1b/glue.c:501: warning: pointer targets in passing argument 2 of 'aes_decrypt' differ in signedness
/root/loop-AES-v3.1b/glue.c:501: warning: pointer targets in passing argument 3 of 'aes_decrypt' differ in signedness
/root/loop-AES-v3.1b/glue.c:555: warning: pointer targets in passing argument 3 of 'aes_encrypt' differ in signedness
/root/loop-AES-v3.1b/glue.c:565: warning: pointer targets in passing argument 3 of 'aes_encrypt' differ in signedness
/root/loop-AES-v3.1b/glue.c:581: warning: pointer targets in passing argument 3 of 'aes_encrypt' differ in signedness
/root/loop-AES-v3.1b/glue.c:589: warning: pointer targets in passing argument 3 of 'aes_encrypt' differ in signedness
cd /usr/src/linux-2.6.10-ARCH && gcc -D__ASSEMBLY__ -Iinclude/asm-i386/mach-defa ult -c /root/loop-AES-v3.1b/aes-x86.S -o /root/loop-AES-v3.1b/aes-x86.o
cd /usr/src/linux-2.6.10-ARCH && gcc -D__ASSEMBLY__ -Iinclude/asm-i386/mach-defa ult -c /root/loop-AES-v3.1b/md5-x86.S -o /root/loop-AES-v3.1b/md5-x86.o
ld -m elf_i386 -r patched-loop.o glue.o aes-x86.o md5-x86.o -o loop.o
cd /usr/src/linux-2.6.10-ARCH && ./scripts/mod/modpost -m vmlinux /root/loop-AES -v3.1b/loop.o >/dev/null 2>&1
/bin/sh: line 1: 4733 Aborted ./scripts/mod/modpost -m vmlinux /root/loop-AES-v3.1b/loop.o >/dev/null 2>&1
make[2]: *** [loop.ko] Error 134
make[1]: *** [modules] Error 2
make[1]: Leaving directory `/usr/src/linux-2.6.10-ARCH'
make: *** [all] Error 2
[root@myhost loop-AES-v3.1b]#

tuxman · 2005-11-23 19:00:25

Soloport,
did you have any trouble installing loop-AES in the terms I described above?
and yes I'd like to try your scripts albeit the install in one box shouldnt be such a big thing as it seems to be in my case, LOL

soloport · 2005-11-24 16:00:06

tuxman wrote:

Soloport,
did you have any trouble installing loop-AES in the terms I described above?
and yes I'd like to try your scripts albeit the install in one box shouldnt be such a big thing as it seems to be in my case, LOL

Let me look over the scripts and compare them with what you're doing, above. It might be something simple -- usually is, for me. When I have an extra minute, I'll post the scripts. They contain other items I would need to strip out, etc., to be generally useful as a stand-alone loop-AES installation script. Perhaps a WiKI entry is in order?

tuxman · 2005-11-24 20:44:02

thank you Soloport,
just my two cents, loop-AES is one of the coolest features of the linux system and should be included in the Arch base system or at least available as a package.

soloport · 2005-12-02 05:12:25

tuxman wrote:

just my two cents, loop-AES is one of the coolest features of the linux system and should be included in the Arch base system or at least available as a package.

Yes, I agree. I wish someone more knowledgeable than I would explain whether the current "default" crypt system in Linux is as good, better, worthless compared to loop-AES.

cactus · 2005-12-02 05:20:42

are you questioning the loop-aes faculty, or the encryption standard?
I can comment on encryption standards to some degree...but not on the faculty (since I dont use it).

tuxman · 2005-12-03 00:30:10

I havent tried the new linux encryption stuff yet.
A comparison based on extended testing would be interesting, above all if it consider the integration between old and new modules and the practical motivation behind new encryption aplications.
I have used loop-AES for about 2 years now, its very fast, steady, flexible and secure.
the encrypted home directory can be treated just as ani image file, backed up, copied, etc.
loop-AES is also very lightweight, for instance minmal distros like damnsmalllinux include it in their base system.

Arch Linux

#1 2005-11-16 00:14:36

AES256

#2 2005-11-21 00:48:06

Re: AES256

#3 2005-11-21 03:58:18

Re: AES256

#4 2005-11-21 04:51:21

Re: AES256

#5 2005-11-21 05:13:41

Re: AES256

#6 2005-11-21 05:20:24

Re: AES256

#7 2005-11-21 05:26:05

Re: AES256

#8 2005-11-21 05:35:01

Re: AES256

#9 2005-11-21 07:10:27

Re: AES256

#10 2005-11-21 18:32:51

Re: AES256

#11 2005-11-21 19:22:18

Re: AES256

#12 2005-11-21 21:50:09

Re: AES256

#13 2005-11-22 01:29:13

Re: AES256

#14 2005-11-23 19:00:25

Re: AES256

#15 2005-11-24 16:00:06

Re: AES256

#16 2005-11-24 20:44:02

Re: AES256

#17 2005-12-02 05:12:25

Re: AES256

#18 2005-12-02 05:20:42

Re: AES256

#19 2005-12-03 00:30:10

Re: AES256

Board footer