4 commits

Author	SHA1	Message	Date
physikerwelt	94b035b26a	Coverage tests for the Math extension ... * Include generated tests for a better test coverage of the Math extension. * Compiles texvc in testsuite (if required) * Test generator now included * Replaces the old parser tests * Fixes whitspace issues Bug: 61090 Change-Id: Iff7eeb5ee72137492c3f6659e4d4d106e5715586	2014-03-11 15:35:07 +00:00
physikerwelt	dcc3f0fd3c	Differentiate missing texvccheck from missing texvc ... Introduce different error messages for missing texvccheck and texvc and update the README file. Bug: 61154 Change-Id: I52f796f181f6a3ab6d65a8e8d89f59d523d5b7b8	2014-02-12 01:38:01 +00:00
Chad Horohoe	e0b3883c55	Wrap texvccheck call in PoolCounter ... Change-Id: Iae9693d1948bec6dd08473bce3cb704f24338ff8	2014-02-10 09:38:35 -08:00
physikerwelt	6a0af8f3b4	Validate TeX input for all renderers, not just texvc ... The user input specified in the math tag a. la <math>E=m <script>alert('attacked')</script>^2 </math> is verified in PNG rendering mode, but not in plaintext, MathJax or LaTeXML rendering mode. This is a potential security issue. Furthermore, the texvc specific commands such as $\reals$ that is expanded to $\mathbb{R}$ might be rendered differently depended on the rendering mode. Therefore, the security checking and rewriting portion of texvc have been extracted from the texvc source (see I1650e6ec2ccefff6335fbc36bbe8ca8f59db0faa) and are now available as a separate executable (texvccheck). This commit will now enable this enhancement in security and provide even more compatibility among the different rendering modes. Bug: 49169 Change-Id: Ida24b6bf339508753bed40d2e218c4a5b7fe7d0c	2014-01-22 10:07:27 +00:00