From 2657e554d1bbe0cfff47e21a9df3f25ac0f1da4a Mon Sep 17 00:00:00 2001 From: Benjamin Kramer Date: Wed, 29 Mar 2023 18:49:04 +0200 Subject: [PATCH] [docs] Fix a typo (malicously-crafter) --- llvm/docs/Security.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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. -- 2.7.4