nas4free permissions do not work well with Windows.

[single_platinum]

One thing that people complain about the most when I try to get them to use NAS4free instead of a QNAP or Synology is the weirdness of the permissions. I wish the NAS4free team would get this to work better with Windows, which is where a majority of users are coming from....

So if I have a directory structure under the share like this:

\upload admin -full control, everyone -change Owner: admin
\videos admin -full control, everyone -read+execute Owner:admin

I want anyone to be able to dump files into upload, and they can. However, when they do the Owner is not admin and I have to go into advanced permission settings and take control. What is worse is when I move the file into the \videos directory it does not inherit any of the permissions, admin gets removed as the owner, and I cant take full control. I am using Windows7 clients.

It seems as though NAS4free is not fully compatible with Windows file security settings or using Windows7 to set security properties, including ownership and inheritance.
Will a future release address this?

EDIT: This was never a problem with Nexenta, all of the Windows permissions and inheritance worked flawlessly.

[kenZ71]

The permissions work very well for me.

I like the ability to lock the system down so only certain users can access the data. Seems like a good idea to me.

If your setting up NAS machines what is the level of permissions your client want? It would be very easy to leave the shares wide open or even use an AD server to control permissions.

[alexey123]

As for me permissions work very well. I use Authentication as local user.

[single_platinum]

Again, this is the setup:

I have a directory structure under the share like this:

\upload admin -full control, everyone -change Owner: admin
\videos admin -full control, everyone -read+execute Owner:admin

I want anyone to be able to dump files into upload, and they can. However, when they do the Owner is not admin and I have to go into advanced permission settings and take control. What is worse is when I move the file into the \videos directory it does not inherit any of the permissions, admin gets removed as the owner, and I cant take full control. I am using Windows7 clients.

Can anyone explain why this does not work?

[alexey123]

You not understand Unix permissions. Executable is unix-executable,not windows. You need only readable.
See my old post - it can help you
I understand, you want folder uploads must be open for all for read and write
folder movies must be read-only for users and read+write for admin.
define your users from group nobody, and define admin from group wheel.
Create folders same as on pictures

for each users admin include create Home directory as /mnt/data/samba on tab Access|Users|Add
define share as

As for me work as expected. Also I deny Inherit permissions.

[single_platinum]

Again, you are basically saying that the windows permissions dialog doesn't really work. The majority of users coming to NAS4free are windows users. Expecting them to just to conform themselves to Unix permissions isn't a reasonable expectation, and as long as that is an assumption then Windows users will continue to gravitate towards QNAP and Synology boxes.

Nexenta does a much better job of integrating with Windows permissions. I guess I will have to steer users towards that solution.

[alexey123]

Why all work on my network? What I do wrong?

Again, you are basically saying that the windows permissions dialog doesn't really work.

I not need on my server permissions from unknow system such windows.

[Onichan]

Again, you are basically saying that the windows permissions dialog doesn't really work. The majority of users coming to NAS4free are windows users. Expecting them to just to conform themselves to Unix permissions isn't a reasonable expectation, and as long as that is an assumption then Windows users will continue to gravitate towards QNAP and Synology boxes.

Nexenta does a much better job of integrating with Windows permissions. I guess I will have to steer users towards that solution.

NTFS uses ACL's, if you want the same kind of permissions on Unix then you are required to use ACL's as well. Which I haven't personally used, but I heard isn't too hard. Though I will agree it takes more work then those prebuilt boxes such as Synology. I don't think this really is an issue though as anybody comparing the two should easily notice NAS4Free takes a little bit of effort when setting it up and is designed for people at least a little technically inclined.

[single_platinum]

When I set up a Nexenta install, the permission inheritance works right out of the box. I can set permissions and inheritance with the native windows file dialog box. Why is it considered sacrilege to expect this functionality out of NAS4free?

When I get criticized for asking why something doesn't work as expected, it is like your saying "we don't want new users" or "we don't want this project to be successful".

When you crap on new users, what is it that you expect to accomplish? Do you expect this will magically attract more users to the platform?

[Onichan]

I am not familiar with Nexenta, but are you saying it pulls user account info from your desktop by default and uses that for permissions? If that is true then that seems the wrong way to go about it. A NAS generally speaking is designed to be accessed by multiple systems with different local accounts. If that isn't what you are saying then I don't understand.

Anyways I think new users are good, but to me it seems like you are complaining about something small and trying threaten that other people aren't going to use NAS4Free just because of this when I don't think anybody really cares what you use and they aren't begging users to use it.

[siftu]

I have a post about windows and acls

http://n4f.siftusystems.com/index.php/2 ... ions-acls/

I dont use windows, but it seems to be what most users are after. And I agree these options should at least be dropdowns when creating datasets.

[single_platinum]

I have a post about windows and acls

http://n4f.siftusystems.com/index.php/2 ... ions-acls/

I dont use windows, but it seems to be what most users are after. And I agree these options should at least be dropdowns when creating datasets.

siftu, THANK YOU! That is EXACTLY what I am talking about.
It appears Nexenta defaults to this CIFS functionality out of the box. I really wish this was the default for NAS4free.
Yes, I made this text deliberately huge because I am quite pleased with the response from siftu.

[single_platinum]

I have just finished testing this out and it appears to work predictably.

Siftu, how can I lobby the developers to have these be the default CIFS settings? This will really solve most users permission problems when using Windows.

[siftu]

Well I was going to add the options when creating the datasets.. I just have to find some time

[single_platinum]

Well I was going to add the options when creating the datasets.. I just have to find some time

Thank you, thank you, thank you!

I hope somebody on the team is doing statistical analysis of tech support related complaints. I am quite sure that changing this will result in a measurable decrease in file permission related complaints about CIFS shares.

[single_platinum]

I did an import of my Nexenta volume, and followed the instructions here: http://n4f.siftusystems.com/index.php/2 ... ions-acls/
I would have thought the chown -R command would have given me permissions on the imported pool, but it does not.
Any suggestions???

[kenZ71]

Well I was going to add the options when creating the datasets.. I just have to find some time

Thank you, thank you, thank you!

I hope somebody on the team is doing statistical analysis of tech support related complaints. I am quite sure that changing this will result in a measurable decrease in file permission related complaints about CIFS shares.

Sorry, I seem to be missing something.

I understand the permissions are not exactly what you want - that can be fixed.

I also know that the permissions standards that CIFS is using is rock solid. FreeBSD, the guts of NAS4Free, powers some huge / robust servers.

Please don't give up, you will have a very secure system once your done.

[single_platinum]

The ZFS pool I imported from Nexenta had all of the permissions reset to d---------
The only way to fix it was to go in with advanced file manager to each subdirectory and manually set them to drwxr-xr-x

It would be nice if the system were able to fix all of the permissions when importing a ZFS pool.

[durcom]

Siftu:

Thanks for the windows ACL post. It works for me. One problem I have though. It seems zfs snapshots are no longer exposed in the share accessed via windows explorer (no .zfs folders and no "previous versions")

Any ideas?

[siftu]

The .zfs directory can be exposed via setting the snapdir attribute. "zfs set snapdir=visible pool/dataset"

Not sure about the shadow copy thing

[durcom]

I have enabled that setting in the gui to expose .zfs and it doesn't work

Also, I created another share, using the standard CIFS parameters and the .zfs folders are exposed.
As soon as I enable ZFS ACL and your suggested additional parameters, .zfs folders are no longer exposed on the share

[durcom]

Just tested again..."Enable ZFS ACL" seems to be the culprit...enable it an no .zfs folder, disable it and .zfs folders appear