On Tue, Mar 05, 2002 at 02:31:42PM +0000, Markus Kuhn wrote:
> Alexander Gelfenbain wrote on 2002-03-04 22:04 UTC:
> > In addition to that we were considering adding a rich security
> > model with font certificates (public/private key pairs) and permissions, 
> > but decided to do it in the second version, as soon as we implement font
> > sharing between ST Server running on different machines and make
> > ST Font Server speak SLP.
> 
> What threats exactly shall this security model protect against?

Sharing commercial fonts in distributed rendering systems and keeping
the lawyers happy. Once we make ST Font Servers talk to one another
and exchange fonts we need to make sure that we can only share fonts 
that are licensed for that. That is especially important for some
CJK fonts.

> Are there highly font-specific security concerns that can't be addressed
> by existing more generic X11 access control mechanisms?
> 
> Developping an entire public key infrastructure separately for something
> as specialized as a font rendering API sounds like megabloat to me, but
> perhaps I just misunderstood the suggestion.

If we don't figure out how to do it elegantly we might defer to some
simple permissions model or disable font sharing whatsoever.

> 
> Markus
> 


AG

-- 
Alexander Gelfenbain, Sun Microsystems, Inc.
+1 (408) 635-0612 
_______________________________________________
Fonts mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/fonts

Reply via email to