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
| ||
|
Date: Wed, 6 Aug 2008 08:17:03 -0700 From: Greg KH <greg@...ah.com> To: tvrtko.ursulin@...hos.com Cc: Arjan van de Ven <arjan@...radead.org>, "Press, Jonathan" <Jonathan.Press@...com>, linux-kernel@...r.kernel.org, linux-security-module@...r.kernel.org, malware-list@...ts.printk.net Subject: Re: [malware-list] [RFC 0/5] [TALPA] Intro to a linuxinterfaceforon access scanning On Wed, Aug 06, 2008 at 11:05:43AM +0100, tvrtko.ursulin@...hos.com wrote: > Greg KH wrote on 05/08/2008 21:26:21: > > > > [JON PRESS] I wouldn't call it lazy, actually. It's more like > > > "economical" or "ergonomic" -- or, dare I say it -- "user-friendly." > In > > > this case, the users are the AV vendors who will have to write to the > > > API that will come out of this spec. We will be more inclined to > > > appreciate the SDK (for want of a better term) if it covers all the > > > bases, rather than force us to go elsewhere for some of our > > > requirements. When we write SDKs, we try to make sure that our users > > > will find whatever they need. > > > > But realize that you are adding an overhead on us, the kernel community, > > to make your life easier. We are the ones that are taking our time to > > review and comment on this code. We are the ones who will have to live > > with this code for forever, and maintain it over the lifetime of linux. > > So far, you all have shown no willingness to give anything back to us at > > all. > > We all? How is that true? I for example wrote some code and am willing to > help maintain it if it gets accepted. You did? I didn't see any patches from you here, did I just happen to miss them? If Eric's code was based on yours, that's great, but it didn't imply maintenance, especially as it doesn't look like your original patches much :) thanks, greg k-h -- 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