Comment

Comment on Private network storage for my users?

<- View Parent

avidamoeba@lemmy.ca ⁨6⁩ ⁨days⁩ ago

Not sure I’m getting you. Let me explain what I mean:

Host exposes a network share (1-time setup)
Client mounts the network share (N-time setup, could be automated)
Client creates a LUKS or VeraCrypt file in that network share, secured with their key. The key is generated on the client and it doesn’t enter the host. (1-time setup)
Client decrypts the image with their key and mounts it on the client (N-time setup)
Client modifies data in the decrypted vol
Client unmounts the volume (N-time, not required)
Client unmounts the network share (N-time, not required)

At no point does the client’s key leave their computer and the host only ever sees encrypted data.

source

Sort:hotnew top

just_another_person@lemmy.world ⁨5⁩ ⁨days⁩ ago
OP said they DON’T want LUKS. I’m also missing how the admin of the server (OP) wouldn’t have or store the keys unless and have these mounts available at all times?

You seem to be suggesting there is some way for a remote user to mount a LUKS image on its host, which is not a thing unless you’re first SSH’ing to said host and mounting it and making it available for export mount elsewhere, which is clearly not what OP is asking for here when they just want space for people to store media. Maybe I’m misunderstanding.

There Hook, Filen, Yeetfile, BatchIT…tons of these self-hosted stacks that do this with auth and user management built in. That’s what OP is asking about.

source
- avidamoeba@lemmy.ca ⁨5⁩ ⁨days⁩ ago
  The host mounts no LUKS. The host just exports a network share via NFS. The client mounts that NFS share to a local mount pount. Then the client has a dir which actually resides on the host. So far completely standard NAS stuff. Then the client creates a file in that dir. E.g. secretcontainer.img. This file is then encrypted on the client using cryptsetup (LUKS). Then it’s mounted on the client using LUKS. All the LUKS stuff happens on the client. The host just sees a file appear called secretcontainer.img on its storage. The same idea would work with VeraCrypt instead of LUKS. Or Cryptomator. Or anything else that can store encrypted data in file(s) in a directory.
  
  source
  - just_another_person@lemmy.world ⁨5⁩ ⁨days⁩ ago
    Bud…been doing this for 20 years. Don’t need your explainer.
    
    The fact you didn’t mention the barest of minimums in your comment if where the issue lies. You’re just adding stacks on stacks of things by using any other network mount and having the user manage an encrypted image inside that mount. Also absent from what you were trying to explain. I’d work on that.
    
    Point being, for a multi-user/tenant utility like OP is asking for, there are better tools for the job, of which I just named a couple standalone options. If they are running TrueNAS, Synology, or QNAP, or even NextCloud, there are already built-ins for this purpose, and apps to match.
    
    If not, any of the other solutions I mentioned are much better suited for the use-case, especially, and if not only because, OP specifically said they DID NOT want exactly what you’re describing.
    
    source
    avidamoeba@lemmy.ca ⁨5⁩ ⁨days⁩ ago
    
    The fact you didn’t mention the barest of minimums in your comment if where the issue lies.
    
    I described the procedure step-by-step mentioning each layer. That’s the best I could do.
    
    OP specifically said they DID NOT want exactly what you’re describing.
    
    OP said they’re worried about performance with this solution. Hence why my first response addressed the performance issue. The rest was responding to you (and anyone else who is reading) since you thought that is not an E2E solution. I tried explaining why it’s client-side encryption and no keys are stored on the host.
    
    source