sqlcipher 3.4.1 was just released, and it supports OpenSSL 1.1. I think
the best approach here is to try to get 3.4.1 into stretch and remove
the hacky patches for OpenSSL 1.1 that we currently have. I don't
currently have time to take that project on, but I'm happy to answer
questions for anyone
Control: tags -1 + patch
On Fri, 20 Jan 2017 18:53:41 +0100 Kali Kaneko wrote:
> I'm facing the same issue in pysqlcipher.
>
> I found a workaround, in:
> https://github.com/sqlcipher/sqlcipher/pull/195/commits/37efb6a9e9995c21a3c9e632bb86b3ba6f613f79#diff-c2495c7f2211a99fba2bfb98a19a1916
>
> T
I'm facing the same issue in pysqlcipher.
I found a workaround, in:
https://github.com/sqlcipher/sqlcipher/pull/195/commits/37efb6a9e9995c21a3c9e632bb86b3ba6f613f79#diff-c2495c7f2211a99fba2bfb98a19a1916
They key to avoid the segfault is this line in the sqlcipher_openssl_cipher
function:
+ EVP
On Fri, 13 Jan 2017 20:53:51 +0100, Hans-Christoph Steiner
wrote:
> It would be good to get 3.4.0 included, perhaps that will help.
On the version topic, I was susprised the sqlcipher command reports a
version very different from the debian package (which I could
reproduce with the older package
Rolling back to 3.2.0-1 is not really an option for stretch, since it
ships with openssl 1.1, and the only change in 3.2.0-2 is making
sqlcipher work with openssl 1.1. It would be good to get 3.4.0
included, perhaps that will help.
I'm currently not using sqlcipher on the desktop at all, so I'm n
Hello,
This bug also affects skrooge, which also relied on sqlcipher.
I confirm rolling back to 3.2.0-1 fixes the issue there too.
Regards,
--
Vincent Pelletier
Package: libsqlcipher0
Version: 3.2.0-2
Severity: important
Dear Hans-Christoph,
This could be severity grave, but as I did not verify whether other
applications using libsqlcipher0 crash, I am setting it to important for
now.
Sometime ago qTox started crashing after entering profile password on
7 matches
Mail list logo
