From: Benjamin Kramer Date: Wed, 29 Mar 2023 16:49:04 +0000 (+0200) Subject: [docs] Fix a typo (malicously-crafter) X-Git-Tag: upstream/17.0.6~13301 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=2657e554d1bbe0cfff47e21a9df3f25ac0f1da4a;p=platform%2Fupstream%2Fllvm.git [docs] Fix a typo (malicously-crafter) --- diff --git a/llvm/docs/Security.rst b/llvm/docs/Security.rst index 7687b37..11acac3 100644 --- a/llvm/docs/Security.rst +++ b/llvm/docs/Security.rst @@ -223,7 +223,7 @@ The security-sensitive parts of the LLVM Project currently are: The parts of the LLVM Project which are currently treated as non-security sensitive are: -* Language front-ends, such as clang, for which a malicious input file can cause undesirable behavior. For example, a maliciously-crafter C or Rust source file can cause arbitrary code to execute in LLVM. These parts of LLVM haven't been hardened, and compiling untrusted code usually also includes running utilities such as `make` which can more readily perform malicious things. +* Language front-ends, such as clang, for which a malicious input file can cause undesirable behavior. For example, a maliciously crafted C or Rust source file can cause arbitrary code to execute in LLVM. These parts of LLVM haven't been hardened, and compiling untrusted code usually also includes running utilities such as `make` which can more readily perform malicious things. * *FUTURE*: this section will be expanded.