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: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070704204759.GA341@thunk.org>
Date:	Wed, 4 Jul 2007 16:47:59 -0400
From:	Theodore Tso <tytso@....edu>
To:	Erik Mouw <mouw@...linux.org>
Cc:	alan <alan@...eserver.org>, J?rn Engel <joern@...fs.org>,
	"H. Peter Anvin" <hpa@...or.com>,
	Jack Stone <jack@...keye.stone.uk.eu.org>,
	linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
	akpm@...ux-foundation.org, viro@...iv.linux.org.uk
Subject: Re: Versioning file system

On Wed, Jul 04, 2007 at 07:32:34PM +0200, Erik Mouw wrote:
> (sorry for the late reply, just got back from holiday)
> 
> On Mon, Jun 18, 2007 at 01:29:56PM -0400, Theodore Tso wrote:
> > As I mentioned in my Linux.conf.au presentation a year and a half ago,
> > the main use of Streams in Windows to date has been for system
> > crackers to hide trojan horse code and rootkits so that system
> > administrators couldn't find them.  :-)
> 
> The only valid use of Streams in Windows I've seen was a virus checker
> that stored a hash of the file in a separate stream. Checking a file
> was a matter of rehashing it and comparing against the hash stored in
> the special hash data stream for that particular file.

And even that's not a valid use.  All the virus would have to do is to
infect the file, and then update the "special hash data stream".  Why
is it that when programmers are told about streams as a potential
technology choice, it makes their thinking become fuzzy?  :-)

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ