firmloha.blogg.se

1. DEBIAN SIMPLE NETWORK FILE SHARING WITHOUT SAMBA HOW TO
2. DEBIAN SIMPLE NETWORK FILE SHARING WITHOUT SAMBA PASSWORD
3. DEBIAN SIMPLE NETWORK FILE SHARING WITHOUT SAMBA WINDOWS 7
4. DEBIAN SIMPLE NETWORK FILE SHARING WITHOUT SAMBA WINDOWS

CAVEAT: Without create mode and directory mode, and relying on only ACLs, note that ACLs cannot set the group sticky bit. Set the sticky bit to ensure new directories keep the same ACLs (which we'll set next. I like to override this because I want ensure that new files are owned by the group smbmedia and the user should be set to the user who created the file (for record keeping). I have create mode and directory mode in there, but its mostly for good measure and redundant.īecause this share is writable, the default umask will apply.

Note the This means that anyone in the group smbmedia may access this share. This is why I prefer to implement shares by groups (not by users like in most documentation):

DEBIAN SIMPLE NETWORK FILE SHARING WITHOUT SAMBA PASSWORD

The password may not be the empty string (at least I have not found a way to force this while also passing the authentication step).įile shares are often group-oriented (group of users need access to the same data).

DEBIAN SIMPLE NETWORK FILE SHARING WITHOUT SAMBA WINDOWS

This means that the password set with smbpasswd should match that of the user's password on the Windows client. If you care about security, read on.īy default, Windows passes the username and password of the currently logged-in user. If it is a guest mount, then who cares about security and you can stop reading this now. The accepted answer by "hijarian" at the time of writing is not ideal for the main reason that if the share is writable, then you cannot know which user wrote to the share. So, most important piece of config relevant to me was force user. It asked for password, I have entered the same as for the main system.Īfter that, I have added the force user and force group settings to the smb.conf: So, when ntfs-3g will mount these disks, everything will be owned by him.Īfter that, I have added this user to the Samba registry (or maybe created new identical one, don't care): # smbpasswd -a jonnie They are set to the UID and GID of the user jonnie set up on the server (obviously not root).

The most important pieces of config are uid and gid (maybe only uid, don't know). dev/sdb2 /media/disk2 ntfs defaults,noexec,noatime,relatime,utf8,uid=1000,gid=1000 0 2 I have NTFS partitions which I need to mount RW so I used the following setup in my /etc/fstab: /dev/sdb1 /media/disk1 ntfs defaults,noexec,noatime,relatime,utf8,uid=1000,gid=1000 0 2 So, what I lack in the scheme to NOT HAVE to enter login/password? This is usability question, I will not create a user-based authentication for file junkyard.Īs this is absolutely not obvious from the docs and HOWTOs and whatever, the reason this thing asks for password is because it cannot map guest user to the owner of the directory being shared. smb://homeserv/ file path in Debian (in any file browser) shows me two folders: disk1 and disk2, as intended, by trying to open them bring the login/password dialog.

DEBIAN SIMPLE NETWORK FILE SHARING WITHOUT SAMBA WINDOWS 7

Windows 7 shows login/password dialog right after I click on the shared machine in network neighborhood. NO COMBINATION of security = user, map to guest = Bad user, security = share, guest ok = yes and such helped. On both client machines, in both Debian and Windows I get the same result: login/password dialog. My smb.conf after distillation looks as follows ( verbatim, nothing else is there): In fact, my machine is Debian/Windows dualboot, and my wife's machine is Windows only.

2 local partitions which I want to share, formatted in NTFS due to being old and taken from Windows machine.sudo smbd -version gives me Version 3.6.6.I need/want to setup a completely open public file share on my home server for two workstations. I don't know how much RTFM I need to set this stuff.

DEBIAN SIMPLE NETWORK FILE SHARING WITHOUT SAMBA HOW TO

NOTE: I have read probably up to 50 different pages describing how to setup public Samba share in the span of 2 YEARS and nothing ever worked for me.