mirror of
https://github.com/nextcloud/documentation.git
synced 2026-01-02 17:59:36 +07:00
fix typos in security docs
This commit is contained in:
@@ -25,7 +25,7 @@ To prevent this, always use prepared queries:
|
||||
$params = array(1);
|
||||
$result = $query->execute($params);
|
||||
|
||||
If the App Framework is used, write SQL queries like this in the a class that extends the Mapper:
|
||||
If the App Framework is used, write SQL queries like this in a class that extends the Mapper:
|
||||
|
||||
.. code-block:: php
|
||||
|
||||
@@ -107,7 +107,7 @@ Clickjacking
|
||||
|
||||
To prevent such attacks Nextcloud sends the `X-Frame-Options` header to all template responses. Don't remove this header if you don't really need it!
|
||||
|
||||
This is already built into Nextcloud if :php:class:`OC_Template`.
|
||||
This is already built into Nextcloud in :php:class:`OC_Template`.
|
||||
|
||||
Code executions / file inclusions
|
||||
---------------------------------
|
||||
@@ -136,7 +136,7 @@ Code executions and file inclusions can be easily prevented by **never** allowin
|
||||
Directory traversal
|
||||
-------------------
|
||||
|
||||
Very often developers forget about sanitizing the file path (removing all \\ and /), this allows an attacker to traverse through directories on the server which opens several potential attack vendors including privilege escalations, code executions or file disclosures.
|
||||
Very often developers forget about sanitizing the file path (removing all \\ and /), this allows an attacker to traverse through directories on the server which opens several potential attack vectors including privilege escalations, code executions or file disclosures.
|
||||
|
||||
**DON'T**
|
||||
|
||||
|
||||
Reference in New Issue
Block a user