diff options
| author | Hans-Christoph Steiner <hans@eds.org> | 2012-09-25 21:24:35 -0400 |
|---|---|---|
| committer | Hans-Christoph Steiner <hans@eds.org> | 2012-09-27 15:24:21 -0400 |
| commit | 1d0102794ca90b4520129336794da06e4e79b0d1 (patch) | |
| tree | 7e40d7d2232ee6a03a36e891e508a875fe3b77a4 /debian/libsqlcipher0.lintian-overrides | |
| parent | 16f07f9eca01294dc1a4dd62f4b13856ddbdf262 (diff) | |
get lintian overrides working, and generalize rule to all archs
Diffstat (limited to 'debian/libsqlcipher0.lintian-overrides')
| -rw-r--r-- | debian/libsqlcipher0.lintian-overrides | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/debian/libsqlcipher0.lintian-overrides b/debian/libsqlcipher0.lintian-overrides new file mode 100644 index 0000000..3553c12 --- /dev/null +++ b/debian/libsqlcipher0.lintian-overrides @@ -0,0 +1,11 @@ +# lintian correctly finds a version of sqlite in the sqlcipher libs. SQLCipher +# is a customized version of SQLite3 that adds encryption support. +# Unfortunately, this cannot be implemented as a plain plugin to SQLite +# because it is not possible to make the encryption transparent without +# modifying the core of SQLite. For example, with SQLCipher, you only need to +# know about sqlite_key()/sqlite_rekey() and the related PRAGMAS, and the rest +# of the API and SQL calls are exactly the same as SQLite. I believe this is +# not even possible using the SQLite author's proprietary encryption plugin. +# +# Some more info on its design is available here: http://sqlcipher.net/design +libsqlcipher0: embedded-library usr/lib/*/libsqlcipher.so.0.8.6: sqlite |