Documentation Source Text

Check-in [2ffc105f81]
Login

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

Overview
Comment:Fix typo on the security.html webpage.
Downloads: Tarball | ZIP archive | SQL archive
Timelines: family | ancestors | descendants | both | branch-3.26
Files: files | file ages | folders
SHA3-256:2ffc105f81a74dad74838f763f0fdb77d89d5a3fc134c3b2840d44b281d6ea8a
User & Date: drh 2018-12-26 12:00:45
Context
2019-01-09
19:56
Fixes to the syntax diagrams for window functions: The parentheses were missing around the window-defn for the WINDOW clause. check-in: fd152b335d user: drh tags: branch-3.26
2018-12-26
12:00
Fix typo on the security.html webpage. check-in: 2ffc105f81 user: drh tags: branch-3.26
2018-12-15
11:12
Fix a typo in the assert.html document. check-in: 538a9a3099 user: drh tags: branch-3.26
Changes
Hide Diffs Unified Diffs Ignore Whitespace Patch

Changes to pages/security.in.

3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
  {defense against dark arts}</tcl>
<fancy_format>

<h1>SQLite Always Validates Its Inputs</h1>

<p>
SQLite should never crash, overflow a buffer, leak memory,
or exhibit any other harmful behavior, even with presented with
maliciously malformed SQL inputs or database files.  SQLite should
always detect erroneous inputs and raise an error, not crash or
corrupt memory.
Any malfunction caused by an SQL input or database file
is considered a serious bug and will be promptly addressed when
brought to the attention of the SQLite developers.  SQLite is
extensively fuzz-tested to help ensure that it is resistant







|







3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
  {defense against dark arts}</tcl>
<fancy_format>

<h1>SQLite Always Validates Its Inputs</h1>

<p>
SQLite should never crash, overflow a buffer, leak memory,
or exhibit any other harmful behavior, even when presented with
maliciously malformed SQL inputs or database files.  SQLite should
always detect erroneous inputs and raise an error, not crash or
corrupt memory.
Any malfunction caused by an SQL input or database file
is considered a serious bug and will be promptly addressed when
brought to the attention of the SQLite developers.  SQLite is
extensively fuzz-tested to help ensure that it is resistant