New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BSD-3-Clause license "violation" #307
Comments
Hello @kapouer, thanks for getting in touch. I'm somewhat confused by this issue. SQLCipher has no dependencies on MapBox at all. If MapBox is using SQLCipher (which it seems like they might be), then their project should be including our SQLCipher copyright statement, not the other way around. In that case, this Issue should be filed against their project, since they would be the ones in violation of the license. In the event that you meant SQLite instead of MapBox, that situation is different. SQLite is not distributed under the BSD-3 clause license, it is in the public domain. As a result, there is no license to abide by. Even so, we do extensively communicate that SQLCipher is based on SQLite in all project documentation (e.g. the project website, README, Open Source Legal Notices. So, to summarize, SQLCipher is licensed under the 3-clause BSD, but SQLite is not. Projects that use SQLCipher Community Edition under that license are require to adhere to SQLCipher license and attribute SQLCipher accordingly. Projects implementing SQLCipher (or SQLite) are not required to attribute SQLite since it is public domain. However, SQLCIpher does extensively credit SQLite outside of the license text in recognition of the importance of that project as the core library that SQLCipher is based on. Let me know if that clears things up, or if there is something that we are missing. |
Oops ! I had an ongoing issue about node-sqlite and confused that one with sqlite3. Sorry ! |
Hi,
the BSD-3-Clause license states:
which is for sqlite3:
which isn't in
sqlcipher/LICENSE
Lines 1 to 2 in fda4c68
The proper way to fix this is to simply retain the original copyright line below or above your copyright line.
The text was updated successfully, but these errors were encountered: