[llvm] 2657e55 - [docs] Fix a typo (malicously-crafter)

Benjamin Kramer via llvm-commits llvm-commits at lists.llvm.org
Wed Mar 29 09:50:21 PDT 2023


Author: Benjamin Kramer
Date: 2023-03-29T18:49:04+02:00
New Revision: 2657e554d1bbe0cfff47e21a9df3f25ac0f1da4a

URL: https://github.com/llvm/llvm-project/commit/2657e554d1bbe0cfff47e21a9df3f25ac0f1da4a
DIFF: https://github.com/llvm/llvm-project/commit/2657e554d1bbe0cfff47e21a9df3f25ac0f1da4a.diff

LOG: [docs] Fix a typo (malicously-crafter)

Added: 
    

Modified: 
    llvm/docs/Security.rst

Removed: 
    


################################################################################
diff  --git a/llvm/docs/Security.rst b/llvm/docs/Security.rst
index 7687b379d93e0..11acac33f0a19 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.
 
 


        


More information about the llvm-commits mailing list