The generated freetype2.pc file lists ${includedir}/freetype2 but
not ${includedir} which causes code to fail to find ft2build.h if
freetype is installed in a non-standard directory. freetype-config,
on the other hand, gets this right. Trivial patch attached.
Applied, thanks.
Werner
On Thursday, August 25th, 2005 14:17Z George Williams wrote:
First of all that seems a very weak form of protection.
I believe it is more social than technically effective.
Secondly I don't really understand what damage a font can do to my
system. The worst I can think of is
a) crash the X
On 8/26/05, Antoine Leca [EMAIL PROTECTED] wrote:
DSIG is a MS thing, and they have (thanks to the monolithic architecture
which integrates the GUI with the kernel, while targetting both workstations
and servers) to think about these issues.
I don't see how a bad font can have any real
Salut David,
Tu peux dormir ? ;-)
On Thursday, August 25th, 2005 15:18Z Turner, David wrote:
My opinion is that the DSIG table is the brain-child of DRM-obsessed
managers at Microsoft Typography (or above), who don't understand much
things regarding security.
They only understand that
Salut Antoine,
Useless about security, probably.
Yes
Worse, the MS tool that signs does not check many things (and
certainly not possible exploit, since none are known ;-)), and anyway you
can set it up to allow signing using /another/ checking tool...
Which are the reasons why you,
I seem to remember talk about testing FreeType on randomly corrupted
fonts; has any work on this been done?
AFAIK, George has started with some work. For my part, I've done
nothing, alas.
Werner
___
Freetype-devel mailing list
On Fri, 2005-08-26 at 05:44, Werner LEMBERG wrote:
I seem to remember talk about testing FreeType on randomly corrupted
fonts; has any work on this been done?
AFAIK, George has started with some work. For my part, I've done
nothing, alas.
I have a little program which
makes a
