Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Fri, 16 Jun 2006 01:02:02 +0400
From: Solar Designer <>
Subject: Re: Owl: crypto

On Thu, Jun 15, 2006 at 05:53:45PM +0400, Maxim Timofeyev wrote:
> I was mistaken when using SHA1. But for example AES does not work.
> It is possible to ask to give an example precisely working?

Here it is, running off an Owl 2.0 boot CD under QEMU:

localhost!root:~# losetup -e aes /dev/loop0 /dev/ram1
localhost!root:~# mke2fs /dev/loop0
localhost!root:~# losetup -d /dev/loop0
localhost!root:~# mount /dev/ram1 /mnt -oencryption=aes
localhost!root:~# df /mnt
Filesystem           1K-blocks      Used Available Use% Mounted on
/ram/dev/ram1             3963        13      3746   1% /mnt

Of course, I could have mounted /dev/loop0 right away, without the
"losetup -d", but I wanted to illustrate how to mount the filesystem
later on.

> # losetup -e AES /dev/loop0 /tmp/cr
> Password:
> ioctl: LOOP_SET_STATUS: Invalid argument, requested cipher or key length (128
> bits) not supported by kernel

It appears that you don't have some required component compiled or
loaded into your kernel.  Please start with the known-working kernel
configuration off the CD.

Alternatively, maybe your losetup version/build are not right.  You did
not specify what version of the package you're using.  Please try the
known-working version from Owl 2.0.

Alexander Peslyak <solar at>
GPG key ID: B35D3598  fp: 6429 0D7E F130 C13E C929  6447 73C3 A290 B35D 3598 - bringing security into open computing environments

Was I helpful?  Please give your feedback here:

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.