Linux

48181 readers

968 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago

MODERATORS

nooter692@lemmy.ml

AgreeableLandscape@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

authenticated remote filesystem access for home/SOHO use? (lemmy.ca)

submitted 8 months ago by phx@lemmy.ca to c/linux@lemmy.ml

12 comments fedilink hide all child comments

(sorry in advance for the long post)

What I'm looking for:

Basically, without a lot of work to setup and maintain a Domain/Kerberos server, what's the best way to provide consistent logins and remote folder/share (from a server) access across various Linux desktops

I've configured domain controllers using Samba. I've also configured Linux systems as domain-joined hosts. Between the two I tend to find that keeping talking - especially for systems that are only on infrequently - can be a bit troublesome. Updates sometimes break the Samba server, tokens expire, etc etc

I've also used NFS of various versions, but found v4 with the Kerberos implementation a bit finicky (for similar reasons to the SMB based implementation). NFSv3 of course is fairly fast and efficient, but lacks the user-level authentication and relies on IP's for access-control.

Now it's been awhile since I've given a shot at this except for some NFS shares between VMs and SSHFS for desktops, it would be nice to have a consistent but easily maintainable way to provided common shares for larger files (videos, albums, 3d models, and projects etc) without having to constantly troubleshoot. Maybe the domain/NFS route had gotten easier but it still seems to be fairly manual at times.

you are viewing a single comment's thread
view the rest of the comments

[–] navigatron@beehaw.org 3 points 8 months ago (1 children)

NFS for storage, tailscale / wireguard for access control?

[–] phx@lemmy.ca 1 points 8 months ago (1 children)

I haven't played with tailscale, and most of my wireguard shenanigans have involved connecting to others' systems. Wouldn't those mostly control the network-level access but not the account-level access (centralized account/UID/gid and remote permissions) part?

[–] navigatron@beehaw.org 2 points 8 months ago (1 children)

Indeed, and good points. How many users do you have? I assume this isn’t just for you, and setting up multiple nfs shares with tailscale access policies isn’t feasible. SMB might be the best play. I’ll have to refresh my memory on file sharing protocols

[–] phx@lemmy.ca 1 points 8 months ago

Not too many users, but an ever changing variety of devices and services :-)