NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
How does a Linux user logon to their account on a Readynas
ReadyNas Rn104 - Firmware: OS 6.10.3 ReadyCloud: Enabled Share protocols enabled: SMB, NFS, AFP, HTTP Environment: Linux home network. All devices running Linux Mint 19.3 or 20 A few months ago, ...
Thanks to all for your helpful responses.
Unfortunately, all they have done is confirmed my opinion that the ReadyNas is NOT suitable for the Linux environment. I don't see why Iit should be necessary to install Samba on every machine on the network simply to access a ReadyNas, which is after all a Linux device.
I have instead decided to abandon the ReadynNas and install the drives in a JBOD enclosure driven by a Raspbery Pi. I can acheive everything I want to much more easily.
It's a shame, as I was given 2 of these boxes which, had they been more flexible, could have proved useful.
Thanks again and goodbye
Nibbles0522 wrote:
I can find no documentation or posts anywhere that explains how a user is to log onto their account.
First of all, you should consider if you really want to use home folders. They are a bit of a pain. If you don't want people to see the home folders of other family members, then you probably should use them. But if you don't care about that, then you are better off using public share. You can still restrict access if you like.
But to answer your question: The home folder is created when you access the NAS with SMB using the user's credentials.
Nibbles0522 wrote:I can find no documentation or posts anywhere that explains how a user is to log onto their account.
Any authenticated access - SMB, FTP, AFP, SSH, and to the admin Web UI (only for members of the admin group as there is no user login on http(s)) - is considered a login _and_ does create the "username" home folder.
NFSv3 and the simple NFSv4 on the other hand (leaving the fully blown NFSv4 implementation with my big friend Kerberos alone) does not need any authentication - it's all UID/GID/exports access based.
StephenB wrote:First of all, you should consider if you really want to use home folders. They are a bit of a pain. If you don't want people to see the home folders of other family members, then you probably should use them.
That's exactly what the home folders here on ReadyNAS are designed for. Unfortunately - and different from the big NAS makers - e.g. admin's can't get access as a folder e.g. by SMB for administrative tasks). These are private folders, not shared folders.
A member of the admin group on can (of course) enumerate and access these folders in the admin Web UI - but not by SMB, AFP. When using FTP, even admin can only see /home/admin - neither admin nor other members of the admin group will be able to gain access.
When allowing SSH access to a user why ever, he will be able to enumerate the folders in /home but won't be able to access these thanks to the very basic U**x protection in place by default:
stephenssh@RN516:~$ ls -als /home
total 4
0 drwxr-xr-x 1 admin admin 160 Nov 17 2014 .
4 drwxr-xr-x 1 root root 296 Mar 3 22:28 ..
0 drwx------ 1 admin admin 18 Aug 9 2013 admin
0 drwx------ 1 anyotheruser users 60 Dec 5 2019 anyotheruser
...
0 drwx------ 1 stephen users 0 Jul 16 09:29 stephen
0 drwx------ 1 stephenssh users 0 Jul 16 09:43 stephenssh
...
stephenssh@RN516:~$ cd ../anyotheruser
-bash: cd: ../anyotheruser: Permission denied
In the ReadyNAS scope, this is perfectly correct.
schumaku wrote:
StephenB wrote:
First of all, you should consider if you really want to use home folders. They are a bit of a pain. If you don't want people to see the home folders of other family members, then you probably should use them.
That's exactly what the home folders here on ReadyNAS are designed for. Unfortunately - and different from the big NAS makers - e.g. admin's can't get access as a folder e.g. by SMB for administrative tasks). These are private folders, not shared folders.
The annoying lack of access by admin's is why I said "probably".
But perhaps more on target, I suspect most home NAS users don't really need private folders (and might not want them for their kids). Personally I keep them turned off.
schumaku wrote:That's exactly what the home folders here on ReadyNAS are designed for. Unfortunately - and different from the big NAS makers - e.g. admin's can't get access as a folder e.g. by SMB for administrative tasks). These are private folders, not shared folders.
Sure you can, if you use SMB to access the top level of the NAS and use the admin credentials, the home folders are in the home folder of your primary volume (typically data/home). I've not tried other protocols, but have always believed it works for them as well.
It's been that way since OS 3.x on the NV, though the main volume was C there.
On my NAS, I can access \\192.168.0.42 (without specifying a share) using the admin credentials and one of the folders is data, in which lies home, in which lie the user folders.
home does also show up at top level, where access is denied. I'm not sure why that is.
Yes, you are correct Sandshark - using SMB and the admin user UI does allow the access, missed to add this. It's a bad (no, very bad) way to access NAS resources by admin (aehm root). Especially where one can't use (leaving the trick alone using once the name and once the IP) frm the same (Windows) client.
Does it work for users in the admin group then, too?
Here again, other vendors allow to control the access to the home folder.I don't have other admin users, so I've not tried it, but /etc/frontview/samba/Shares.conf.admin gives the entire admin group access to the top level of every volume, so I assume it works.
Can't work on other protocols like ftp because /home is not ACL enabled, a standard ftp daemon is in place and standard U**x apply. That's why admin can only see /home/admin ...
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
