Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(237)

Side by Side Diff: third_party/sqlite/src/ext/userauth/user-auth.txt

Issue 901033002: Import SQLite 3.8.7.4. (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@master
Patch Set: Chromium changes to support SQLite 3.8.7.4. Created 5 years, 10 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch
OLDNEW
1 Activate the user authentication logic by including the 1 Activate the user authentication logic by including the
2 ext/userauth/userauth.c source code file in the build and 2 ext/userauth/userauth.c source code file in the build and
3 adding the -DSQLITE_USER_AUTHENTICATION compile-time option. 3 adding the -DSQLITE_USER_AUTHENTICATION compile-time option.
4 The ext/userauth/sqlite3userauth.h header file is available to 4 The ext/userauth/sqlite3userauth.h header file is available to
5 applications to define the interface. 5 applications to define the interface.
6 6
7 When using the SQLite amalgamation, it is sufficient to append 7 When using the SQLite amalgamation, it is sufficient to append
8 the ext/userauth/userauth.c source file onto the end of the 8 the ext/userauth/userauth.c source file onto the end of the
9 amalgamation. 9 amalgamation.
10 10
(...skipping 144 matching lines...) Expand 10 before | Expand all | Expand 10 after
155 when the second argument is NULL. 155 when the second argument is NULL.
156 156
157 The built-in version of of sqlite_crypt() uses a simple Ceasar-cypher 157 The built-in version of of sqlite_crypt() uses a simple Ceasar-cypher
158 which prevents passwords from being revealed by searching the raw database 158 which prevents passwords from being revealed by searching the raw database
159 for ASCII text, but is otherwise trivally broken. For better password 159 for ASCII text, but is otherwise trivally broken. For better password
160 security, the database should be encrypted using the SQLite Encryption 160 security, the database should be encrypted using the SQLite Encryption
161 Extension or similar technology. Or, the application can use the 161 Extension or similar technology. Or, the application can use the
162 sqlite3_create_function() interface to provide an alternative 162 sqlite3_create_function() interface to provide an alternative
163 implementation of sqlite_crypt() that computes a stronger password hash, 163 implementation of sqlite_crypt() that computes a stronger password hash,
164 perhaps using a cryptographic hash function like SHA1. 164 perhaps using a cryptographic hash function like SHA1.
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698