Searched refs:untrusted (Results 1 – 8 of 8) sorted by relevance
/plugin/embeddedphp/ |
H A D | README | 8 untrusted or incompetent people are able to edit wiki pages!
|
/plugin/aichat/vendor/erusev/parsedown/ |
H A D | README.md | 43 To tell Parsedown that it is processing untrusted user-input, use the following: 49 If instead, you wish to allow HTML within untrusted user-input, but still want output to be free from XSS it is recommended that you make use of a HTML sanitiser that allows HTML tags to be whitelisted, like [HTML Purifier](http://htmlpurifier.org/).
|
/plugin/codeprettify/code-prettify/ |
H A D | CHANGES.md | 114 rewrite the HTML and then inject it, so anyone doing that with untrusted HTML 116 untrusted source, sanitize first.
|
/plugin/findologicxmlexport/vendor/twig/twig/doc/ |
H A D | intro.rst | 17 * *Secure*: Twig has a sandbox mode to evaluate untrusted template code. This
|
H A D | api.rst | 342 environment, making it safe to evaluate untrusted code. 473 The ``sandbox`` extension can be used to evaluate untrusted code. Access to 502 untrusted template code by using the ``sandbox`` tag:
|
/plugin/commonmark/vendor/league/commonmark/ |
H A D | README.md | 57 ? If you will be parsing untrusted input from users, please consider setting the `html_input` and `allow_unsafe_links` options per the example above. See <https://commonmark.thephpleague.com/security/> for more details. If you also do choose to allow raw HTML input from untrusted users, consider using a library (like [HTML Purifier](https://github.com/ezyang/htmlpurifier)) to provide additional HTML filtering.
|
H A D | CHANGELOG-0.x.md |
|
/plugin/diagramsnet/lib/js/diagramly/ |
H A D | Editor.js | 1812 Editor.configure = function(config, untrusted) argument 2083 if (config.plugins != null && !untrusted)
|