Add note on opening existing SQLCipher databases with SQLite3 Multiple Ciphers

[Copilot]

Users migrating from the removed bundle_e_sqlcipher package to SQLite3 Multiple Ciphers need to know that existing SQLCipher-encrypted databases require explicit cipher configuration in the connection string.

• Added a subitem under the SQLite3 Multiple Ciphers mitigation option explaining how to open existing SQLCipher databases using URI cipher parameters
• Links to upstream documentation for full details

Example connection string for opening an existing SQLCipher database:

Data Source=file:example.db?cipher=sqlcipher&legacy=4;******

[Copilot]

Pull request overview

Adds guidance to the EF Core 11.0 breaking changes documentation to help users migrating from the removed bundle_e_sqlcipher package open existing SQLCipher-encrypted databases when using SQLite3 Multiple Ciphers.

Changes:

• Updates the “SQLite3 Multiple Ciphers” mitigation link to point to the upstream SQLite3MultipleCiphers-NuGet documentation.
• Adds a sub-bullet explaining that opening existing SQLCipher databases requires specifying cipher settings via URI parameters in the connection string.

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.

[AndriySvyryd]

@bricelam @utelle FYI

[utelle]

Thank you for letting us know.

It definitely makes sense to mention the SQLite3 Multiple Ciphers NuGet package's availability. Also, the point about the need to specify additional configuration parameters for existing SQLCipher encrypted databases is valid.

However, I would like to point out that this applies not only to existing databases, but in general. If a user wants to encrypt a new database with the SQLCipher scheme, it is also necessary to specify configuration parameters accordingly. Only for the default cipher scheme (which is chacha20) no additional configuration parameters are required.