sqlcipher | standalone fork of SQLite that adds 256 bit AES encryption | Database library

I figured this out and hope this helps. First I had to do everything inside memscoped so we had access to alloc() methods.

Then I realised one issue was my database path was incorrect. Using XCode you can click on Window -> Devices & Simulators, click your app, then click the cog and press Download Container. Then inspect the container of your app to see where the database is. For me it was inside Application Support.

You can then check if your DB exists like so:

Kotlin/Native's cinterop tool should have all compiler options specified explicitly to "see" the header the same way as your compiler did when building the library. To specify the compiler options, please use the DSL as described in the documentation.

In general, something like that should work:

Gorm uses a system of drivers that adapt the individual database clients for its use.

You'd have to create a new module that copies the source of go-gorm/driver/sqlite but updating https://github.com/go-gorm/sqlite/blob/master/sqlite.go#L8 to import the alternate library of your choice. Since these are forks and they comply with the database/sql interface, it should just work. You'll then be able to use this new driver as per normal in gorm:

I'm not too sure about the cause of the problem,
but have you considered manualy downloading it from github and setting it near the code that uses that?

I know it's probably not the solution you were searching for but it might be all it takes...

Turns out i have to change the context that i pass into Dagger in the dynamic feature module fragment. So, instead using requireContext(), use requireActivity().appicationContext in my case. The code should be looking like this:

Found the answer!

Steps:

1. Compile openssl (I use 1.1.1) - keep libcrypto.so
2. Compile sqlcipher (I use 4.3.0) with the libcrypto you just created.
3. Download DBD-SQLite (Latest right now is 1.66) and unzip
4. Copy sqlite3.c sqlite3.h sqlite3ext.h from sqlcipher folder to DBD-SQLite
5. Copy libcrypto.so to DBD-SQLite
6. Edit LDFLAGS, LDDLFLAGS, CFLAGS add this after all defenition:

'PRAGMA rekey' is used to change existing password for the database. To set password for unencrypted database or remove it from a password protected one should use sqlcipher_export() function. This is described in SQLCipher documentation here.

And maybe someone would find code sample useful. For decrypting db you should just establish connection like:

If there is exactly one post, it does not make sense to filter, you should use get_object_or_404(…) [Django-doc]:

I just had the same issue today, with pretty much exactly the same setup. I needed to do two modifications in order to successfully compile sqlcipher3:

1. The content of the MODULE_NAME precompiler definition is set in line 38 of setup.py. The function quote_argument, which is called here, differentiates between Windows and other platforms. On Windows, the quote character is escaped with a backslash. At least for MSVC2019, this seems to be incorrect. To fix it, just remove the Windows-specific stuff on line 35.

2. The library names of OpenSSL have changed in version 1.1.0. If you are using a newer version, you might have to change the library name from libeay32.lib to libcrypto.lib or whatever the library is called on your system (in line 132). In addition, you might have to set the environment variable OPENSSL_CONF, to help the build script to find OpenSSL on your system.

With these two small modifications, the build process worked fine.