SQLitePCL.raw v3

[tranb3r]

Hi,
I've been using SQLite3MultipleCiphers with SQLitePCLRaw for a while in a .NET MAUI app, and it has been working perfectly.
However, I noticed that starting from version 3, SQLitePCLRaw no longer provides free builds with encryption support.
Is there any plan to offer free builds of SQLite3MultipleCiphers for use with SQLitePCLRaw as part of this repository?
Thanks!

[utelle]

I've been using SQLite3MultipleCiphers with SQLitePCLRaw for a while in a .NET MAUI app, and it has been working perfectly.

Glad to hear that.

However, I noticed that starting from version 3, SQLitePCLRaw no longer provides free builds with encryption support.

Yes, this is very unfortunate. The author of SQLitePCLRaw, Eric Sink, decided to drop support for builds with encryption extensions, after he became a more or less official member of the SQLite developer team. AFAIK he intends to support only the official SQliet Encryption Extension (SEE) in the future, although he claims that it will be possible to use separate encryption extensions with SQLitePCLRaw - as long as you build the binaries yourself.

Is there any plan to offer free builds of SQLite3MultipleCiphers for use with SQLitePCLRaw as part of this repository?

Actually, I have a separate repository SQLite3MultipleCiphers-cb, which I used for testing purposes in the past, while SQLite3 Multiple Ciphers binaries were still provided by SQLitePCLRaw.

Unfortunately, Eric Sink has changed the way to generate the binaries for SQLitePCLRaw version 3 - and decided to not publish his new approach. Nevertheless, I guess that the binaries generated in my test repository should be usable in conjunction with the new version of SQLitePCLRaw. But I haven't tested that myself, because the .Net world is definitely not my world.

Since the test repository was used for tests only in the past, the binaries generated by the GitHub CI workflow were never published. However, the binaries generated by the latest update are still available here - but they will be deleted by GitHub. So, I don't know how long they will be available.

In addition, I have the repository SQLite3MultipleCiphers-NuGet, which I created with huge support from @bricelam. Again, the package created by the GitHub CI workflow after the latest update is still available here.

In principle, the plan is to provide a solution that can be combined with the latest SQLitePCLRaw version, but unfortunately I am not able to do this without expert support.

[bricelam]

The plan is to provide a solution that can be combined with the latest SQLitePCLRaw version, but unfortunately I am not able to do this without expert support.

My spare time is limited these days, but I still plan on digging into this with you. I'll keep you updated as I make progress.

[tranb3r]

I've been able to use SQLite3 Multiple Ciphers 2.2.4 with SQLitePCLRaw 3.0.2, for dotnet maui on android:

• use the default official provider: SQLitePCLRaw.provider.e_sqlite3
• extract libsqliteX.so from sqlite3mc-2.2.4-sqlite-3.50.4-android.aar
• the lib has to be renamed into libe_sqlite3.so for the provider to use it

The only issue I've faced is when migrating from 2.2.0 to 2.2.1.
So far I was using PRAGMA key = "x'myhexkey'". This does not work anymore in 2.2.1. I have to use instead PRAGMA key = "raw:myhexkey".
Could this be a bug in sqlite3mc introduced in 2.2.1 ?
I'm using this url "file:{dbPath}?cipher=sqlcipher&legacy=4".

Now, I have to figure out how to make it work for iOS...

[utelle]

I've been able to use SQLite3 Multiple Ciphers 2.2.4 with SQLitePCLRaw 3.0.2, for dotnet maui on android:

• use the default official provider: SQLitePCLRaw.provider.e_sqlite3
• extract libsqliteX.so from sqlite3mc-2.2.4-sqlite-3.50.4-android.aar
• the lib has to be renamed into libe_sqlite3.so for the provider to use it

Yes, that's certainly a possible way to do it. However, I will at least try to provide a more convenient way in the future.

The only issue I've faced is when migrating from 2.2.0 to 2.2.1. So far I was using PRAGMA key = "x'myhexkey'". This does not work anymore in 2.2.1. I have to use instead PRAGMA key = "raw:myhexkey". Could this be a bug in sqlite3mc introduced in 2.2.1 ? I'm using this url "file:{dbPath}?cipher=sqlcipher&legacy=4".

Version 2.2.1 introduced the option to specify raw keys for all ciphers, not only for SQLCipher. I will have to look into that to find out whether a bug sneaked in. This feature is not used by many users.

Now, I have to figure out how to make it work for iOS...

Could you check whether the binaries from the GitHub CI workflows in my other repos are usable for your purposes?

• Android, subdirectory e_sqlite3mc/android
• iOS, subdirectory e_sqlite3mc/ios