Documentation Source Text

Check-in [94ad3e51e7]
Login

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview
Comment:Fix typos in the defense-against-dark-arts document.
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA3-256: 94ad3e51e735c14da42042dd80916dbcab2190786b562e6d9b591d21e2819f94
User & Date: drh 2018-12-14 19:01:35
Context
2019-01-09
19:54
Fixes to the syntax diagrams for window functions: The parentheses were missing around the window-defn for the WINDOW clause. check-in: 83da33aabc user: drh tags: trunk
2018-12-15
01:17
Merge defense-against-dark-arts fixes from trunk. check-in: a8707b40a7 user: drh tags: branch-3.26
2018-12-14
19:01
Fix typos in the defense-against-dark-arts document. check-in: 94ad3e51e7 user: drh tags: trunk
15:54
Rename the "security.html" document as "Defense Against Dark Arts". Add the additional recommendation to avoid memory-mapped I/O on untrusted database files. check-in: 11d0259504 user: drh tags: trunk
Changes
Hide Diffs Side-by-Side Diffs Ignore Whitespace Patch

Changes to pages/security.in.

     5      5   
     6      6   <h1>SQLite Always Validates Its Inputs</h1>
     7      7   
     8      8   <p>
     9      9   SQLite should never crash, overflow a buffer, leak memory,
    10     10   or exhibit any other harmful behavior, even with presented with
    11     11   maliciously malformed SQL inputs or database files.  SQLite should
    12         -always detected erroneous inputs and raise an error, not crash or
           12  +always detect erroneous inputs and raise an error, not crash or
    13     13   corrupt memory.
    14     14   Any malfunction caused by an SQL input or database file
    15     15   is considered a serious bug and will be promptly addressed when
    16     16   brought to the attention of the SQLite developers.  SQLite is
    17     17   extensively fuzz-tested to help ensure that it is resistant
    18     18   to these kinds of errors.
    19     19   
................................................................................
    28     28   <p>
    29     29   Applications that accept untrusted SQL inputs should take the following
    30     30   precautions:
    31     31   
    32     32   <ol>
    33     33   <li><p>
    34     34   Set the [SQLITE_DBCONFIG_DEFENSIVE] flag.
    35         -This prevents ordinary SQL statements from corrupted the database
           35  +This prevents ordinary SQL statements from corrupting the database
    36     36   file.
    37     37   
    38     38   <li><p>
    39     39   Consider using the [sqlite3_set_authorizer()] interface to limit
    40     40   the scope of SQL that will be processed.
    41     41   </ol>
    42     42   
................................................................................
    43     43   <h2>Untrusted SQLite Database Files</h2>
    44     44   
    45     45   <p>Applications that accept untrusted database files should do the following:
    46     46   
    47     47   <ol>
    48     48   <li value="3"><p>
    49     49   Run [PRAGMA integrity_check] or [PRAGMA quick_check] on the database
    50         -as first SQL statement after opening the database files and
           50  +as the first SQL statement after opening the database files and
    51     51   prior to running any other SQL statements.  Reject and refuse to
    52     52   process any database file containing errors.
    53     53   
    54     54   <li><p>
    55     55   Enable the [PRAGMA cell_size_check=ON] setting.
    56     56   
    57     57   <li><p>