Skip to content

Commit 9f28dbd

Browse files
CopilotAndriySvyryd
andcommitted
Format SQLCipher note as a subitem under SQLite3 Multiple Ciphers bullet
Agent-Logs-Url: https://github.com/dotnet/EntityFramework.Docs/sessions/c1c4c436-88bb-41f4-be7a-5f502b6293c3 Co-authored-by: AndriySvyryd <6539701+AndriySvyryd@users.noreply.github.com>
1 parent 9d77950 commit 9f28dbd

1 file changed

Lines changed: 2 additions & 1 deletion

File tree

entity-framework/core/what-is-new/ef-core-11.0/breaking-changes.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -87,7 +87,8 @@ If you need SQLite encryption, you have the following options:
8787

8888
- **SQLite Encryption Extension (SEE)**: This is the official encryption implementation from the SQLite team. A paid license is required. See [https://sqlite.org/com/see.html](https://sqlite.org/com/see.html) for details. NuGet packages are available through [SourceGear's SQLite build service](https://github.com/ericsink/SQLitePCL.raw/wiki/SQLite-encryption-options-for-use-with-SQLitePCLRaw).
8989
- **SQLCipher**: Purchase supported builds from [Zetetic](https://www.zetetic.net/sqlcipher/), or build the [open source code](https://github.com/sqlcipher/sqlcipher) yourself.
90-
- **SQLite3 Multiple Ciphers**: NuGet packages are available from [SQLite3MultipleCiphers-NuGet](https://github.com/utelle/SQLite3MultipleCiphers-NuGet). If you need to open an existing database that was encrypted with SQLCipher, you must configure the cipher scheme in the connection string using URI parameters--for example: `Data Source=file:example.db?cipher=sqlcipher&legacy=4;Password=Password12!`. See [How to open an existing database encrypted with SQLCipher](https://github.com/utelle/SQLite3MultipleCiphers-NuGet#how-to-open-an-existing-database-encrypted-with-sqlcipher) for details.
90+
- **SQLite3 Multiple Ciphers**: NuGet packages are available from [SQLite3MultipleCiphers-NuGet](https://github.com/utelle/SQLite3MultipleCiphers-NuGet).
91+
- If you need to open an existing database that was encrypted with SQLCipher, you must configure the cipher scheme in the connection string using URI parameters--for example: `Data Source=file:example.db?cipher=sqlcipher&legacy=4;Password=Password12!`. See [How to open an existing database encrypted with SQLCipher](https://github.com/utelle/SQLite3MultipleCiphers-NuGet#how-to-open-an-existing-database-encrypted-with-sqlcipher) for details.
9192

9293
For more details, see [SQLite encryption options for use with SQLitePCLRaw](https://github.com/ericsink/SQLitePCL.raw/wiki/SQLite-encryption-options-for-use-with-SQLitePCLRaw) and [SQLitePCLRaw 3.0 Release Notes](https://github.com/ericsink/SQLitePCL.raw/blob/main/v3.md).
9394

0 commit comments

Comments
 (0)