RE: [malware-list] TALPA - a threat model? well sorta.

[Press, Jonathan]

> -----Original Message-----
> From: malware-list-bounces@xxxxxxxxxxxxxxxx [mailto:malware-list-
> bounces@xxxxxxxxxxxxxxxx] On Behalf Of tvrtko.ursulin@xxxxxxxxxx
> Sent: Thursday, August 14, 2008 5:31 AM
> To: Theodore Tso
> Cc: peterz@xxxxxxxxxxxxx; linux-kernel@xxxxxxxxxxxxxxx; malware-
> list@xxxxxxxxxxxxxxxx; hch@xxxxxxxxxxxxx; viro@xxxxxxxxxxxxxxxxxx;
> andi@xxxxxxxxxxxxxx; malware-list-bounces@xxxxxxxxxxxxxxxx;
> alan@xxxxxxxxxxxxxxxxxxx; Arjan van de Ven
> Subject: Re: [malware-list] TALPA - a threat model? well sorta.

 
> Hm, maybe by implementing a facility with which a client can register
it's
> interface usage intent? Something like:
> 
> register(I_HAVE_NO_INTEREST_IN_CONTENT);
> register(I_WANT_TO_EXAMINE_CONTENT);
> 
> All former ones would run first because they only want to have the
> opportunity to block and do something unrelated to file content (like
> HSMs), and later group would be ran last since they want to examine
the
> content.
> 
> Ordering inside those two groups is not important because I don't see
how
> a model other than restrictive can make sense with content security
> scanning.

I'm not sure I understand why "interest in content" means not blocking,
and vice versa.  However, I think this is a good idea if made more
explicit, i.e.:

> register(BLOCK);
> register(DON'T_BLOCK);


Jon Press

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/