- Devant mon ordinateur
- https://arkensys.dedyn.io
-
Find me on the Fediverse: @hardcoresushi@mastodon.cipherbliss.com
- Joined on
2021-01-07
How many processor cores does your device have?
Can you try to close all running applications (force close if necessary), then try again to create a cryfs volume?
On my 8-core device,…
Thank you very much. The only relevant line I spot in the provided logs is the following:
[libcryfs] [error] Crashed: std::bad_alloc
I think cryfs is failing to allocate enough memory…
OK, that's hard to tell what's the problem without seeing the logcat. Can't you use adb or LogFox?
Do you have the same issue with…
Unfortunatly I cannot reproduce. It would be very helpful if you could show the logcat.
How long the message "Creating volume..." is displayed before showing the error? Can you reproduce the…
Great. The fix has been pushed: b503f134d5c4ecc97f3421530671d1e7cf1766fe. The next release should solve the issue.
The conflict must be due to the F-Droid version that is signed with different keys.
So the test version still doesn’t work? How did you get this new crash log?
This version may fix the issue. Could you please tell me if it works fine when opening files, internal camera and when trying to change password?
-----BEGIN PGP SIGNED MESSAGE-----
Hash:…Does it also happen when opening the internal camera or changing a volume's password?
If it's the same problem, the good news is that it's already been solved. Just upgrade to v2.1.2 (should be on F-Droid in a few days).
Is it the same issue as in #237?
Did you update from F-Droid? Can you show your logcat please?
There are actually two sides to an encryption program like gocryptfs. The decrypted/plaintext side has been modified to be accessible via function calls, but the encrypted/ciphertext side has not…
As explained in the README, this is not possible. This is because gocryptfs and cryfs are programs designed to access the encrypted volume via direct file system calls. The only way to open remote…