| 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
| ||
|
Message-ID: <20080805203052.3de22dd2@bree.surriel.com> Date: Tue, 5 Aug 2008 20:30:52 -0400 From: Rik van Riel <riel@...hat.com> To: Eric Paris <eparis@...hat.com> Cc: Arjan van de Ven <arjan@...radead.org>, "Press, Jonathan" <Jonathan.Press@...com>, Greg KH <greg@...ah.com>, linux-kernel@...r.kernel.org, malware-list@...ts.printk.net, linux-security-module@...r.kernel.org Subject: Re: [malware-list] [RFC 0/5] [TALPA] Intro to a linux interfaceforon access scanning On Tue, 05 Aug 2008 14:39:34 -0400 Eric Paris <eparis@...hat.com> wrote: > On Tue, 2008-08-05 at 11:27 -0700, Arjan van de Ven wrote: > > but close is... very limited in value. Open is a discrete event > > traditionally associated withh permission checks. > > Close... not so. (And if you mmap memory, you can then close the file > > and still write to it via the mmap) > > Thankfully my implementation will invalidate that close time check and > caching result. It does the invalidating the same place we update mtime > and my understanding is that mmap has been updating mtime for quite a > while now. Then isn't the close time check superfluous, since you do the checks at change time already? -- All rights reversed. -- 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