Relocating a vault #31

New Issue

srapzr · 2024-09-19T06:41:02+02:00

srapzr commented

2024-09-19 06:41:02 +02:00

I got it that DroidFS use a whole folder as vault file system (I am not a developer).

If for example I set a folder like emulate/0/Secure as main folder for vaults, DroidFS call the first vault "Secure".

Instead I just want set a destination folder for all my vaults (currents and future) and deciding at the vault creation how to name them. In the case I choose CryFS cypher.

Currently it is not allowed.

I got it that DroidFS use a whole folder as vault file system (I am not a developer). If for example I set a folder like emulate/0/Secure as main folder for vaults, DroidFS call the first vault "Secure". Instead I just want set a destination folder for all my vaults (currents and future) and deciding at the vault creation how to name them. In the case I choose CryFS cypher. Currently it is not allowed.

hardcoresushi commented

2024-09-19 11:45:34 +02:00

DroidFS is just a port of gocryptfs and CryFS for Android. What you describe is not how gocryptfs or CryFS work.

Instead, just create a base directory such as /sdcard/Vaults, and create any volumes you want inside it with DroidFS.

DroidFS is just a port of gocryptfs and CryFS for Android. What you describe is not how gocryptfs or CryFS work. Instead, just create a base directory such as `/sdcard/Vaults`, and create any volumes you want inside it with DroidFS.

srapzr commented

2024-09-19 12:11:30 +02:00

And why I cannot do the same in emulate/0/Secure?

Sorry for my ignorance in this discipline.

And why I cannot do the same in emulate/0/Secure? Sorry for my ignorance in this discipline.

hardcoresushi commented

2024-09-19 12:21:07 +02:00

You can of course, but the actual path should be /storage/emulated/0/Secure.

You can of course, but the actual path should be `/storage/emulated/0/Secure`.

srapzr commented

2024-09-19 12:30:52 +02:00

Mmm if I create a vault within /Secure DroidFS generates one file and one folder.

So I had to create another sub-folder like /Secure/CryFS/vault-name.

I didnt understand where I wrong.

Mmm if I create a vault within /Secure DroidFS generates one file and one folder. So I had to create another sub-folder like /Secure/CryFS/vault-name. I didnt understand where I wrong.

hardcoresushi commented

2024-09-19 12:33:25 +02:00

Create your base folder first, then use DroidFS to select subfolders inside it for each of your vaults.

srapzr commented

2024-09-19 12:39:10 +02:00

To see if I properly understand you:

Manually I create the primary folder with (i.e.) a file manager (Anemo doesn't allow DroidFS writing permissions) in a writable directory.
Create a vault with DroidFS app.

At this point I see (in /Secure/CryFS) one .bin file and a folder, not a vault folder.

Have I manually create it?

For example /Secure/CryFS/Moon for the Moon vault and /Secure/CryFS/Mars for the Mars one?

To see if I properly understand you: 1. Manually I create the primary folder with (i.e.) a file manager (Anemo doesn't allow DroidFS writing permissions) in a writable directory. 2. Create a vault with DroidFS app. At this point I see (in /Secure/CryFS) one .bin file and a folder, not a vault folder. Have I manually create it? For example /Secure/CryFS/Moon for the Moon vault and /Secure/CryFS/Mars for the Mars one?

hardcoresushi commented

2024-09-19 12:57:23 +02:00

Yes you have to manually create vault subfolders.

👍 1

srapzr commented

2024-09-24 08:32:37 +02:00

It lacks "Open an existing volume" button.
I haven't to create a new volume, just I moved an already existent one from A to B.

Now that it is in a new location, just I have to say to DroidFS where it is ---> Open...

It lacks "Open an existing volume" button. I haven't to create a new volume, just I moved an already existent one from A to B. Now that it is in a new location, just I have to say to DroidFS where it is ---> Open...

1000120504.jpg

214 KiB

hardcoresushi commented

2024-09-24 11:53:46 +02:00

If the button text stays to "Create volume" then it probably means you've selected the wrong path.

srapzr commented

2024-09-24 13:15:50 +02:00

I found the issue. Anemo doesn't allow writing permission even if you give it. Because Anemo create a new volume different from emulate/0/ etc.

https://f-droid.org/packages/exe.bbllw8.anemo/

In regular paths DroidFS works properly.

Could you add paths created by Anemo?

I found the issue. Anemo doesn't allow writing permission even if you give it. Because Anemo create a new volume different from emulate/0/ etc. https://f-droid.org/packages/exe.bbllw8.anemo/ In regular paths DroidFS works properly. Could you add paths created by Anemo?

hardcoresushi commented

2024-09-24 20:03:08 +02:00

Anemo uses its own private storage. Other apps can't access them by direct file access. They must use the ContentProvider API, which is not supported by DroidFS. See #6 for more info.

Anemo uses its own private storage. Other apps can't access them by direct file access. They must use the ContentProvider API, which is not supported by DroidFS. See [#6](https://github.com/hardcore-sushi/DroidFS/issues/6) for more info.

srapzr commented

2024-09-24 21:51:14 +02:00

KeepassDX can reading/writing on Anemo created path.

https://apt.izzysoft.de/fdroid/index/apk/com.kunzisoft.keepass.free

I have a Keepass vault in Anemo volume.

KeepassDX can reading/writing on Anemo created path. https://apt.izzysoft.de/fdroid/index/apk/com.kunzisoft.keepass.free I have a Keepass vault in Anemo volume.

hardcoresushi commented

2024-09-24 22:04:21 +02:00

Of course, KeepassDX does support the ContentProvider API as it's 100% native Android code, unlike DroidFS.

👍 1

Sign in to join this conversation.