Title.

The situation is basically this:

  • NFS works, it’s very fast, keeps the xattrs but if used without Kerberos it’s not secure. If used with Kerberos it works, but has a ticket that expires and forces me to reenter the credentials frequently in order to use it. If there was a way to use NFS with Kerberos and save the credentials NFS would be the perfect solution.

  • Samba works fine too, also keeps the xattrs but I had some troubles with filenames (mainly with some special characters, emoji, etc). Besides, as both my server and my clients run Linux I prefer to avoid it if I have the choice.

  • sshfs would be the natural choice, not as fast as NFS but it’s pretty secure, I already use it in most of my network shares but I just can’t find a way to make it preserve the files xattrs.

Do you guys have any suggestions or maybe any other options that I might use?

    • CtrlAltOoops@lemmy.worldOP
      2·
      5 months ago

      Thanks for the suggestion. In fact I tried rsync and it works. But is it possible to integrate in my current workflow? Maybe copying/moving files using a file manager?

      I’m asking because with the 3 options I mentioned I may, for example, create mount points in fstab and from this there on everything would be transparent to the user. Would it be possible using rsync?

      • SolidGrue@lemmy.worldEnglish
        13·
        5 months ago

        Secure file transfers frequently trade off some performance for their crypto. You can’t have it both ways. (Well, you can but you’d need hardware crypto offload or end to end MACSEC, where both are more exotic use cases)

        rsync is basically a copy command with a lot of knobs and stream optimization. It also happens to be able to invoke SSH to pipeline encrypted data over the network at the cost of using ssh for encrypting the stream.

        Your other two options are faster because of write-behind caching in to protocol and transfer in the clear-- you don’t bog down the stream with crypto overhead, but you’re also exposing your payload

        File managers are probably the slowest of your options because they’re a feature of the DE, and there are more layers of calls between your client and the data stream. Plus, it’s probably leveraging one of NFS, Samba or SSHFS anyway.

        I believe “rsync -e ssh” is going to be your best over all case for secure, fast, and xattrs. SCP might be a close second. SSHFS is a userland application, and might suffer some penalties for it

        • CtrlAltOoops@lemmy.worldOP
          4·
          5 months ago

          I’ll take a closer look into rsync possibilities and see if it applies to my situation. I appreciate your input.

      • CCRhode@lemmy.ml
        1·
        5 months ago

        Maybe copying/moving files using a file manager?

        <plugging package=“file_manager”>FileZilla</plugging>

        -or-

        <plugging package=“file_manager”>Gnome Commander</plugging>

        …but call me quaint. I still like…

        <plugging package=“file_manager”>mc</plugging>

        … 'cause it always just works. mc can ostensibly preserve attributes, time-stamps, and (with appropriate privilege on the receiving end) ownership of transferred files (using an sftp server supposedly).

      • mumblerfish@lemmy.world
        1·
        5 months ago

        How much delay could you live with between syncs? If it’s not important to be immidiate, just an end-of-the-day thing you could cronjob the rync with the update flag every so often.