Skip to content

Commit 163da87

Browse files
authored
[Docs] Mention security of libclang (llvm#149357)
Libclang is a wrapper around the Clang frontend, and frontends are not security-sensitive components of the LLVM project. However, libclang is often embedded in people's downstream tools, so it's best to mention that explicitly.
1 parent 6f28eec commit 163da87

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

clang/docs/LibClang.rst

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -404,3 +404,9 @@ following situations are explicitly unsupported:
404404
compatible across library versions.
405405
* For the same reason as above, serializing objects from one version of the
406406
library and deserializing with a different version is also not supported.
407+
408+
Note: because libclang is a wrapper around the compiler frontend, it is not a
409+
`security-sensitive component`_ of the LLVM Project. Consider using a sandbox
410+
or some other mitigation approach if processing untrusted input.
411+
412+
.. _security-sensitive component: https://llvm.org/docs/Security.html#what-is-considered-a-security-issue

0 commit comments

Comments
 (0)