linux-ext4 - Re: ask for help; hash-directory machanism of ext3 cannot work well

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20070622062000.GA17097@thunk.org>
Date:	Fri, 22 Jun 2007 02:20:00 -0400
From:	Theodore Tso <tytso@....edu>
To:	LIOU Payphone <lioupayphone@...il.com>
Cc:	linux-ext4@...r.kernel.org
Subject: Re: ask for help; hash-directory machanism of ext3 cannot work well

On Fri, Jun 22, 2007 at 09:52:55AM +0800, LIOU Payphone wrote:
> 
> What makes me puzzled is there are two entries both  named  "3220" with ino
> "3350" were shown under "/mnt" when I "ls  -li  /mnt".

Hmm.  I still can't verify this.

Can you replicate the result?  If so, can you send me the output of
dumpe2fs?

> The version of kernel is 2.6.17-1.2142; and e2fsprogs-1.28. 

That looks like a vendor version of the kernel; what distribution are
you using?

E2fsprogs 1.28 is a frighteningly old version of e2fsprogs.  Did you
really mean 1.28?  Or 1.38?

> You know that we can set "s_def_hash_version" to be "DX_HASH_LEAGCY" in
> function  "main{}" of mke2fs.c 

Oh, so you were modifying your sources to set this variable?

> But I don't know why the latest version e2fsprogs-1.39 takes "DX_HASH_TEA"
> for default. Why "DX_HASH_LEAGCY" cannot be taken for default? Could you
> tell me the reason for it? Thanks.  :-)

Because DX_HASH_TEA is a better hash, and because it is keyed off of a
per-filesystem secret hash value stored in the superblock.

						- Ted
-
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html