Skip to content
Permalink
Browse files

fixed documentation about our SQLite3 proprietary AES-OFB encryption

  • Loading branch information
Arnaud Bouchez
Arnaud Bouchez committed Mar 24, 2020
1 parent b4cf374 commit 0fc7d0532cc3c0e8b36b13c5835bfc5a539dea4e
Showing with 8 additions and 8 deletions.
  1. +4 −6 SynDBSQLite3.pas
  2. +3 −1 SynSQLite3.pas
  3. +1 −1 SynopseCommit.inc
@@ -96,12 +96,10 @@ TSQLDBSQLite3ConnectionProperties = class(TSQLDBConnectionProperties)
/// initialize access to a SQLite3 engine with some properties
// - only used parameter is aServerName, which should point to the SQLite3
// database file to be opened (one will be created if none exists)
// - you can specify an optional password, which will be used to access
// the database via some custom kind of encryption - not compatible with the
// official SQLite Encryption Extension module - see
// @http://www.hwaci.com/sw/sqlite/see.html (beta feature - better not to
// be used on production - in which the default encryption level is
// very low)
// - if specified, the password will be used to cypher this file on disk
// (the main SQLite3 database file is encrypted, not the wal file during run);
// the password may be a JSON-serialized TSynSignerParams object, or will use
// AES-OFB-128 after SHAKE_128 with rounds=1000 and a fixed salt on plain password text
// - other parameters (DataBaseName, UserID) are ignored
constructor Create(const aServerName, aDatabaseName, aUserID, aPassWord: RawUTF8); overload; override;
/// initialize access to an existing SQLite3 engine
@@ -2767,7 +2767,9 @@ TSQLDataBase = class(TSynPersistentLock)
// - if specified, the password will be used to cypher this file on disk
// (the main SQLite3 database file is encrypted, not the wal file during run);
// the password may be a JSON-serialized TSynSignerParams object, or will use
// AES-OFB-128 after SHAKE_128 with rounds=1000 and a fixed salt on plain password text
// AES-OFB-128 after SHAKE_128 with rounds=1000 and a fixed salt on plain
// password text; note that our custom encryption is not compatible with the
// official SQLite Encryption Extension module
// - you can specify some optional flags for sqlite3.open_v2() as
// SQLITE_OPEN_READONLY or SQLITE_OPEN_READWRITE instead of supplied default
// value (which corresponds to the sqlite3.open() behavior)
@@ -1 +1 @@
'1.18.5889'
'1.18.5890'

0 comments on commit 0fc7d05

Please sign in to comment.
You can’t perform that action at this time.