linux-kernel - Re: [malware-list] TALPA - a threat model? well sorta.

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: <20080815201622.GD31584@cs.cmu.edu>
Date:	Fri, 15 Aug 2008 16:16:22 -0400
From:	Jan Harkes <jaharkes@...cmu.edu>
To:	Rik van Riel <riel@...hat.com>
Cc:	"Press, Jonathan" <Jonathan.Press@...com>,
	Alan Cox <alan@...rguk.ukuu.org.uk>,
	Eric Paris <eparis@...hat.com>, peterz@...radead.org,
	linux-kernel@...r.kernel.org, malware-list@...ts.printk.net,
	hch@...radead.org, andi@...stfloor.org, viro@...IV.linux.org.uk,
	arjan@...radead.org
Subject: Re: [malware-list] TALPA - a threat model?  well sorta.

On Wed, Aug 13, 2008 at 05:35:29PM -0400, Rik van Riel wrote:
> On Wed, 13 Aug 2008 17:24:28 -0400
> "Press, Jonathan" <Jonathan.Press@...com> wrote:
> 
> > I may be missing something about your suggestion, but I don't see how
> > this would work.  Who does the chmod?
> 
> Chmod is also not a solution to the hierarchical storage (or incremental
> restore from backup) problem.
> 
> I believe we really do need the block-on-open.

Or use either the Fuse or Coda kernel modules and handle such requests
in userspace. With FUSE you should even be able to block on a per-page
granularity, Coda only has session semantics so it will only notify
userspace of the open and close events, while read and write and mmap
are passed directly to the underlying file.

Jan

--
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/