| 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: <Xine.LNX.4.64.0807212054001.17349@us.intercode.com.au> Date: Mon, 21 Jul 2008 21:17:45 +1000 (EST) From: James Morris <jmorris@...ei.org> To: Eric Paris <eparis@...hat.com> cc: malware-list@...ts.printk.net, linux-kernel@...r.kernel.org Subject: Re: request for comment: generic kernel interface for malware vendors On Mon, 21 Jul 2008, Eric Paris wrote: [ITYM anti-malware vendors...] > First I'd like to thank Sophos who stepped up and originally wrote a lot > of this code. They might not recognize it since I've gotten my hands on > it, but they were nice enough to get the ball rolling by giving me some > GPL code which addressed near every request people on the malware list > had. We need a document explaining what the problem being solved actually is. What is the rationale for adding malware scanning to the Linux kernel? How does it benefit people? Why does it need to be in the kernel? What are the general requirements, and how does this interface meet those ? Does this interface represent an approach suitable to a range of anti-malware vendors ? (I'm assuming the fundamental question of whether malware scanning is a good idea or not is not up for discussion, because there'll never be consensus). - James -- James Morris <jmorris@...ei.org> -- 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