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: <20070925213528.GA11088@infradead.org>
Date:	Tue, 25 Sep 2007 22:35:28 +0100
From:	Christoph Hellwig <hch@...radead.org>
To:	Kay Sievers <kay.sievers@...y.org>
Cc:	Karel Zak <kzak@...hat.com>, Theodore Tso <tytso@....edu>,
	Eric Sandeen <sandeen@...hat.com>,
	Andreas Dilger <adilger@...sterfs.com>,
	linux-ext4@...r.kernel.org,
	List util-linux-ng <util-linux-ng@...r.kernel.org>
Subject: Re: [PATCH] obsolete libcom-err for SuSE e2fsprogs

On Tue, Sep 25, 2007 at 10:25:50PM +0200, Kay Sievers wrote:
> >  Technical details :-)
> 
> What do you miss, these are all technical details. :) In simple words,
> we need a completely policy-free, not try-to-be-smart in any sense set
> of functions to identify a bytestream by magic bytes.

Which is exactly what mount and fsck should be doing aswell for a given
device.  In addition they also have the need to find a device if the
fstab line is identified with  LABEL and UUID.  But these are rather
separate issues.

> Hmm, only if you reaqlly don't want to pull it in util-linux, we could
> have it as a separate tree. I still think util-linux is the best place,
> because the most important user of it is mount/fsck. It's your call, I
> would have no problem sending patches against util-linux. :)

Shipping this with util-linux would make some sense.  Then again I'm
a big fan of not mixing up shared libraries and binaries in the same
package.  This just means the distros have to split them into separate
packages again.

-
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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ