sqlite-net-sqlcipher license

[a3cc007]

I referenced sqlite-net-sqlcipher via nuget, and automatically added x64/sqlcipher.dll under bin, is it a free version or a commercial version added this way?

[a3cc007]

I quoted the above 2 packages, will there be a copyright issue？

[ericsink]

Are you sure the file was named sqlcipher.dll ?

If it was named e_sqlcipher.dll, then it's one of the unofficial SQLCipher builds from the SQLitePCLRaw project. More info on those here:

https://github.com/ericsink/SQLitePCL.raw/wiki/Expectation-setting-for-e_sqlcipher

[sjlombardo]

Hello @a3cc007 - in addition to the licenses for the sqlite-net and SQLitePCLRaw packages, if you are using a version of SQLCipher under community edition (open source) terms you should provide attribution as described here:

https://www.zetetic.net/sqlcipher/license/

[a3cc007]

Are you sure the file was named sqlcipher.dll ?

If it was named e_sqlcipher.dll, then it's one of the unofficial SQLCipher builds from the SQLitePCLRaw project. More info on those here:

https://github.com/ericsink/SQLitePCL.raw/wiki/Expectation-setting-for-e_sqlcipher

The program was compiled, and there were e_sqlite3.dll and sqlcipher.dll in the bin/x86 folder

[ericsink]

I'm not entirely sure where that build came from, but I vaguely recall maybe doing sqlcipher builds a long time ago without the e_ prefix, so that's the most likely explanation.

[a3cc007]

I'm not entirely sure where that build came from, but I vaguely recall maybe doing sqlcipher builds a long time ago without the e_ prefix, so that's the most likely explanation.

Will there be a fee for this?

[ericsink]

If it's a build I made as part of SQLitePCLRaw, then it is based on code obtained under an open source license (mentioned by @sjlombardo above) and is distributed on nuget at no cost, with the caveats I describe in the wiki article I mentioned above.

[a3cc007]

Thanks for all the help @ericsink @sjlombardo