Comment

Comment on

non_burglar@lemmy.world ⁨13⁩ ⁨hours⁩ ago

Regarding the access to cloud, it’s been done with fuse many times and it is very useful for those who need it.

You should know that many of these cloud services claim they “don’t know what’s in your files”, but have been shown to absolutely be able to access them on request from court order or law enforcement. Just saying.

source

Sort:hotnew top

perishthethought@piefed.social ⁨13⁩ ⁨hours⁩ ago
Just checking - you know I plan to self host this, on my own PC, inside my LAN, yes?

Are you suggesting there are app owners who’ve written their code such that they can see inside that arrangement and access the files there?

source
- non_burglar@lemmy.world ⁨11⁩ ⁨hours⁩ ago
  You said you were going to use the cloud services, so even if you self-host, using a cloud service api carries the same risk as using their apps. This is an app to unify all the remote storage things.
  
  However, after looking at the code, I retract my comment and caution you not to use Drivebase:
  
  [crypto]
  
  Generate: openssl rand -base64 32
  
  masterKeyBase64 = “<base64-encoded-32-byte-key>”
  
  If this is a salt or a seed, the documentation is wrong. But it looks Luke they're using this base64 value as the actual key. base64 values can be reversed very trivially. Don't use this.
  
  source
- frongt@lemmy.zip ⁨12⁩ ⁨hours⁩ ago
  
  I’m also liking Drivebase supporting multiple cloud providers, as I have files in more than one place.
  
  Does this not means you have files on cloud provider platforms?
  
  source
  - perishthethought@piefed.social ⁨12⁩ ⁨hours⁩ ago
    To be clear, right now all my files are local on the server right now. Someday I expect to have files backed up on a VSP server but that’s not there yet.
    
    source
- Onomatopoeia@lemmy.cafe ⁨12⁩ ⁨hours⁩ ago
  Well you said cloud - cloud to most of us here doesn’t mean on your systems, but a “cloud” of systems - i.e. not controlled by you.
  
  source

Generate: openssl rand -base64 32