Hi Filippo.
On Wed, 2008-02-13 at 22:39 +0100, Filippo Zangheri wrote:
> have you conducted further tests? Have you discovered anything?
I actually conducted some tests last week (also with aes-cbc-essiv) but
wasn't able to reproduce the two errors (tested it on the same computer,
with the same
Hi Filippo.
On Wed, 2008-02-13 at 22:39 +0100, Filippo Zangheri wrote:
have you conducted further tests? Have you discovered anything?
I actually conducted some tests last week (also with aes-cbc-essiv) but
wasn't able to reproduce the two errors (tested it on the same computer,
with the same
On Mon, 2008-02-04 at 10:17 +0100, Milan Broz wrote:
> Yes, so if you hit this with 2.6.24 too is very important to sent OOps
> log to identify problem (or link to screen snapshot, digital camera
> snapshot or so).
I did about 5 complete tests today and dozens of mkfs.ext3's but I
wasn't able to
Christoph Anton Mitterer wrote:
> On Sun, 2008-02-03 at 23:06 +0100, Milan Broz wrote:
...
>>> 2) The second bug happens only rarely and leads to a panic.
>>> Unfortunately it's difficult to reproduce, but it always happened when I
>>> mkfs.ext3 on the /dev/mapper/sda2.
>>> There's a stack-trace
Christoph Anton Mitterer wrote:
On Sun, 2008-02-03 at 23:06 +0100, Milan Broz wrote:
...
2) The second bug happens only rarely and leads to a panic.
Unfortunately it's difficult to reproduce, but it always happened when I
mkfs.ext3 on the /dev/mapper/sda2.
There's a stack-trace printed which
On Mon, 2008-02-04 at 10:17 +0100, Milan Broz wrote:
Yes, so if you hit this with 2.6.24 too is very important to sent OOps
log to identify problem (or link to screen snapshot, digital camera
snapshot or so).
I did about 5 complete tests today and dozens of mkfs.ext3's but I
wasn't able to
Hi Milan Broz
On Sun, 2008-02-03 at 23:06 +0100, Milan Broz wrote:
> Are you sure, that your USB-stick is not faulty ?
I actually tested the stick, too. But I consider problems in the stick
(you mean the key-holding stick, do you?) as highly unlikely.
If the key would be wrong a good crypto
Christoph Anton Mitterer wrote:
> ok but this is just, because those files are still cached in RAM>
>
>
>
> Here's the first problem:
> 1) When I now diff the two versions again (the unencrypted and the one
> from the encrypted partition) I get differences...
> I'm quite sure that this is not
Hi.
I think I've found a bug somewhere in dm-crypt...
First of all the system that I use:
Debian (sid) with kernel 2.26.24 on AMD64 (intel core2 duo), 2GB RAM
For several days now I try to fully encrypt that system (that is, all
partitions are encrypted an I boot from an USB stick)
There are
Hi.
I think I've found a bug somewhere in dm-crypt...
First of all the system that I use:
Debian (sid) with kernel 2.26.24 on AMD64 (intel core2 duo), 2GB RAM
For several days now I try to fully encrypt that system (that is, all
partitions are encrypted an I boot from an USB stick)
There are
Christoph Anton Mitterer wrote:
when I diff -q -r /mnt/unencrypted /mnt/encrypted/ here, everything is
ok but this is just, because those files are still cached in RAM
unmount + close mapping + reboot
create mappings and mount everything again
Here's the first problem:
1) When I now diff
Hi Milan Broz
On Sun, 2008-02-03 at 23:06 +0100, Milan Broz wrote:
Are you sure, that your USB-stick is not faulty ?
I actually tested the stick, too. But I consider problems in the stick
(you mean the key-holding stick, do you?) as highly unlikely.
If the key would be wrong a good crypto
12 matches
Mail list logo
