diff options
| author | Peter Collingbourne <peter@pcc.me.uk> | 2015-06-25 21:02:17 +0000 |
|---|---|---|
| committer | Peter Collingbourne <peter@pcc.me.uk> | 2015-06-25 21:02:17 +0000 |
| commit | 454d8618ebadd14319064d04a87d91368d7d1875 (patch) | |
| tree | 24960c730ad8685d0cf3d1e9c4bd19da75852557 /docs/SafeStack.rst | |
| parent | 187ff59f6b7bfee80c2970d3a120299c3179dd4c (diff) | |
docs: Fix bad link in SafeStack.rst.
git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@240696 91177308-0d34-0410-b5e6-96231b3b80d8
Diffstat (limited to 'docs/SafeStack.rst')
| -rw-r--r-- | docs/SafeStack.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/SafeStack.rst b/docs/SafeStack.rst index 79e02cabef..21e9b6c621 100644 --- a/docs/SafeStack.rst +++ b/docs/SafeStack.rst @@ -87,7 +87,7 @@ that are stored on the heap or the unsafe stack, such as `CPI <http://dslab.epfl.ch/proj/cpi/>`_, or a forward-edge control flow integrity mechanism that enforces correct calling conventions at indirect call sites, such as `IFCC <http://research.google.com/pubs/archive/42808.pdf>`_ with arity -checks. Clang has control-flow integrity protection scheme for `C++ virtual +checks. Clang has control-flow integrity protection scheme for :doc:`C++ virtual calls <ControlFlowIntegrity>`, but not non-virtual indirect calls. With SafeStack alone, an attacker can overwrite a function pointer on the heap or the unsafe stack and cause a program to call arbitrary location, which in turn |