Messages in this thread | | | Date | Tue, 7 Dec 1999 13:35:44 +0100 (CET) | From | Biondi Philippe <> | Subject | Re: malware defense |
| |
How can you rely only on an authentication method as a root intruder could obtain private keys by reading kernel space/kernel binary/module binary or even could overwrite signatures base with his own module signature, even if it is in kernel space ?
I think deactivating /dev/kmem is a first step for all concerning kernel memory (am I right ? Do I forget strange mmap uses or other hacks coming from outer space ?)
Anyway, if you try to protect some sensitive machines like firewalls or web servers or db servers, I think you can forget using dynamic module insertion features. It's a good and simple mean to be sure no one have inserted bad modules.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |