[Dev] Canoga Security Design

[Wes Felter]

On Jan 2, 2004, at 5:34 PM, Chih-Chao Lam wrote:

> I've written up a design document on our security framework plans for  
> Canoga thus far. Appreciate your comments on the wiki page or on this  
> list.
>
> <http://wiki.osafoundation.org/twiki/bin/view/Chandler/ 
> CanogaSecurityDesign>

I find it easier to reply by email, so here goes:

 > For Canoga, we will support the PLAIN (RFC 2595) SASL mechanism.

I really think you should support some kind of challenge-response  
method. I don't know what the most widely supported one is; maybe  
CRAM-MD5? The universities need Kerberos but it doesn't help the  
individual users.

 > We need to prevent malicious code to be installed as part of a  
third-party capplet/filter/agent

Pretty difficult. Most other apps have punted on this.

 > We need to prevent viruses and worms from propagating from Email and  
IM

Seems easy enough; just never execute anything received in email or IM.  
You should probably pay special attention to preventing incoming  
content from triggering bugs in filters/agents.

 > Will we support third-party Capplet sharing in Canoga?
 > Will we support filter sharing in Canoga?
 > Will we support agent sharing in Canoga?

I don't think anyone has ever done this, so what's the use case?

Wes Felter - wesley at felter.org - http://felter.org/wesley/