search

mhogomchungu / sirikali

A Qt/C++ GUI front end to sshfs, ecryptfs-simple, cryfs, gocryptfs, securefs, fscrypt and encfs
http://mhogomchungu.github.io/sirikali
GNU General Public License v3.0
752 stars 58 forks source link

Unable to mount securefs volume #257

Closed himboruah closed 5 months ago

himboruah commented 5 months ago

I can create securefs volume just fine. But when I try to mount it later, it says "Not supported volume encountered".

Securefs binary used: securefs v1.0.0

Tested on Windows 10 x64

mhogomchungu commented 5 months ago

The problem is caused by securefs changing the name of the config file from .securefs.json to .config.pb.

Renaming the config file back to .securefs.json in your new volume should solve the issue.

There are other changes in this 1.0.0 the developer says he is going to reverse "in a few days" and i am waiting for a new securefs release with the changes before i make a new release of SiriKali that supports this new configuration file name.

himboruah commented 5 months ago

Oh! Didn't know that. Thanks for the info. I'll look forward to the updates.

Also, it's great to see you right behind the other devs. Thank you.

mhogomchungu commented 4 months ago

New version is out and it should now work as expected with the latest version of securefs.

https://github.com/mhogomchungu/sirikali/releases/tag/1.6.0

himboruah commented 4 months ago

Hi @mhogomchungu, just tried the new version. But I'm facing issues with it. SiriKali hangs when I try to create a new securefs volume. And if I force close it and try to open the volume that I just created, it throws the following error.

Failed To Complete The Task And Below Log was Generated By The Backend.

[Error] [00000000000017BC] [2024-05-11 15:10:53.585817800 UTC] [int __cdecl securefs::commands_main(int, const char const ):1446] class securefs::POSIXException: No such file or directory (Z:.12482)

mhogomchungu commented 4 months ago

I have updated windows build, try version 1.6.0.1 and see if it solves the problem.

himboruah commented 4 months ago

O yea, it solved the issue. Thank you very much.

One small thing that I noticed while creating a securefs volume is, the default "Volume Path" is set to "C:/Users/Username/Desktop/Desktop". This creates a folder named desktop on the desktop. I think you can get rid of that folder, if it's not by design.

himboruah commented 4 months ago

Screenshot 2024-05-13 114531

And I believe it should've been "Password+KeyFile" instead of "Key+Keyfile".