search

guardianproject / haven

Haven is for people who need a way to protect their personal spaces and possessions without compromising their own privacy, through an Android app and on-device sensors
https://guardianproject.github.io/haven/
GNU General Public License v3.0
6.61k stars 726 forks source link

[Feature Request] Allow users to set storage location #276

Open VA2XJM opened 6 years ago

VA2XJM commented 6 years ago

Hi,

I'd like to see a new feature appears in Haven so the users can select the path where Haven stores pictures.

This would kind of fix #48 and #126 in a simple way. In fact storing pictures in a selected folder will allow users to be able to sync with whatever other devices/computers using SyncThing or whatever other sync apps allowing folders to be synced.

Use case : If the Haven device is removed or destroyed when discovered, evidences will most likely be transferred to other device(s). In my case for example I would sync my Haven device with my home server (24/7) and with my cellphone (not always on network).

ghost commented 6 years ago

I must expand on this, and say that all logs (not just video logs), should be capable of remote storage.

One of the important features of Haven is to escape the dodgy 3rd party cloud that other security tools subject their users to, so it would not be a good idea (for example) to say "tick this box and expose your junk to dropbox (w/Condaleeza Rice on the board)". At the same time, remote logging is very important for security.

Simple approach:

User specifies where on the SD card to store all logs. That's it, as far as Haven goes. Some other tool can be responsible for syncing that directory to a remote location. The beauty of this is very little effort on the Haven project, and no redundant coding is needed. Also, Android users probably would like to have their phones backed up anyway, so this same syncing tool could be responsible for monitoring other local folders (e.g. /mnt/sdcard/DCIM) as well. We would want the syncing tool to be Orbot-aware, so that the remote server could be an .onion address.

SSHFS approach:

Ideally, a local mount point would establish a webdav or SSH connection to remote storage. The mount point appears local to the app, but it's instantly transmitted remotely.

The only problem with this approach is that there are no SSHFS tools on F-Droid.org. So a tool may need to be reinvented so people don't need to rely on google playstore blobs. I'm also not sure if the Playstore version of SSHFS can connect to .onion addresses.

If the network is disrupted, it would be important for Haven to continue logging things locally and sync them the moment it's reestablished. This perhaps suggests doing a hybrid of the two approaches.

(edit: this looks like free software for SSHFS => https://github.com/greyltc/android_external_sshfs. Not sure why that's not on F-Droid)

FTP:

We also might want to consider that some proprietary SOHO routers include file servers, which I think is normally FTP. Not sure though. Perhaps it's sufficient to say Openwrt routers have SSH and can adapt to whatever is needed, so no need to cater for FTP.

jbizzle2 commented 6 years ago

jbwolf On Aug 6, 2018 11:42 AM, "libBletchley" notifications@github.com wrote:

I must expand on this, and say that all logs (not just video logs), should be capable of remote storage.

One of the important features of Haven is to escape the dodgy 3rd party cloud that other security tools subject their users to, so it would not be a good idea (for example) to say "tick this box and expose your junk to dropbox (w/Condaleeza Rice on the board)". At the same time, remote logging is very important for security.

Simple approach:

User specifies where on the SD card to store all logs. That's it, as far as Haven goes. Some other tool can be responsible for syncing that directory to a remote location. The beauty of this is very little effort on the Haven project, and no redundant coding is needed. Also, Android users probably would like to have their phones backed up anyway, so this same syncing tool could be responsible for monitoring other local folders (e.g. /mnt/sdcard/DCIM) as well. We would want the syncing tool to be Orbot-aware, so that the remote server could be an .onion address.

SSHFS approach:

Ideally, a local mount point would establish a webdav or SSH connection to remote storage. The mount point appears local to the app, but it's instantly transmitted remotely.

The only problem with this approach is that there are no SSHFS tools on F-Droid.org. So a tool may need to be reinvented so people don't need to rely on google playstore blobs. I'm also not sure if the Playstore version of SSHFS can connect to .onion addresses.

If the network is disrupted, it would be important for Haven to continue logging things locally and sync them the moment it's reestablished. This perhaps suggests doing a hybrid of the two approaches.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/guardianproject/haven/issues/276#issuecomment-410752627, or mute the thread https://github.com/notifications/unsubscribe-auth/AmDdVJAfzRFT2AC-AOQ-qx6E46X-TGmdks5uOGPPgaJpZM4S6YED .

deviantollam commented 6 years ago

when talking to @n8fr8 we discussed this and now Issue #330 exists... dupe of this?

n8fr8 commented 5 years ago

I think #330 represents the simple use case, and one we can finish this sprint.

The rest of this ticket is more about remote sync/transfer options. We are looking into both rsync and webdav, as well as an RSS/JSON feed that could be synced over the onion address.