Skip to contentSkip to conversation

request for comment: generic kernel interface for malware vendors

DISCUSSION Bodo Eggert 2 participants 2 messages Jul 23, 2008 2 messages not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

#2 lore raw
Quoted 11 lines · Rafael C. de Almeida
Quoted 1 line · Eric Paris

[Kernel support for malware scanners]

I'm a newbie here, so don't take me too serious. But I don't see why that needs a kernel interface, at least from the example on the Documentation directory (patch 9). Seems to me you could just use file permission to deny or allow the access for a certain file. The only thing that would be a little trickier from user-space is to know when a given file is read. So, talpa should do only that or you could take advantage of preload like trickle does for bandwidth shapping.

How do you ensure that the LD_PRELOAD variable stays intact and will be honored by all applications - including that commercial one supplying it's own libc, by suid-binaries and by programs written in a non-libc-language?

#3 lore raw
Quoted 14 lines · On Wed, 23 Jul 2008 14:43:09 +0200 Bodo Eggert <[email protected]> wrote:
Quoted 4 lines · Rafael C. de Almeida
Quoted 1 line · Eric Paris

[Kernel support for malware scanners]

Quoted 8 lines

I'm a newbie here, so don't take me too serious. But I don't see why that needs a kernel interface, at least from the example on the Documentation directory (patch 9). Seems to me you could just use file permission to deny or allow the access for a certain file. The only thing that would be a little trickier from user-space is to know when a given file is read. So, talpa should do only that or you could take advantage of preload like trickle does for bandwidth shapping.

Quoted 4 lines

How do you ensure that the LD_PRELOAD variable stays intact and will be honored by all applications - including that commercial one supplying it's own libc, by suid-binaries and by programs written in a non-libc-language?

neither approach is fool proof for that matter it's just a matter of how high you want to put the bar.

that's why it's really important to see the design ideas for this code... to figure out what it is supposed to do ;)

Signature · 3 lines
If you want to reach me at my work email, use [email protected]
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org