• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Totally stuck setting permissions using OI + Napp it

L

lordsegan

Gawd
Joined
Jun 16, 2004
Messages
624
I was able to install my OpenIndiana Server with Oi and Napp it, and I can see the share folder which is set to guest access on.

I have NO IDEA how to set permissions.

I fooled around with ACL settings, the command line, the web GUI, and the Windows 7 machine.... I am stuck!

Can someone walk me through it?

The doc here does not really explain http://napp-it.org/doc/downloads/napp-it.pdf

:(
 
Last edited:
It is discussed in the napp-it thread --- and yes, it's confusing as heck and everyone has a different answer, even Sun! :O :)

(It's somewhat of a dark art - one day I will get to the bottom of it and not rely on "guest" full control.)
 
Rectal Prolapse said:
It is discussed in the napp-it thread --- and yes, it's confusing as heck and everyone has a different answer, even Sun! :O :)

(It's somewhat of a dark art - one day I will get to the bottom of it and not rely on "guest" full control.)
Click to expand...

All due respect, this isn't a very helpful post.

The only napp-it thread I see here is nearly 127 pages long...

I need the same help the OP does.
 
That was my point roach...the answer is in there but you have to search for it. Gea has answered it a few times already. And it isn't an easy answer otherwise I would've given you a soundbite-worthy answer that politicians use to win elections!

With all due respect.
 
I was able to get 115mb/sec with OI. It's worth it if you can figure it out (I havent yet, still on guest access).
 
And this is why when MS releases the next gen of storage spaces based on windows 8....many of us will go running. Seriously...if people here with moderate *nix experience are getting crushed by this issue what makes you think those of us willing to put our toes in the water won't say screw it?

WHS v1/v2 --> add user, use radio buttons to set permissions
OI --> read 127 page thread, your answer is in there somewhere
 
But it's really easy to do in FreeNAS as well.

Create share with read-only privs.
Then create admin share with full access.

Takes 15 seconds. Why isn't this an option in OI?!
 
lordsegan said:
I was able to install my OpenIndiana Server with Oi and Napp it, and I can see the share folder which is set to guest access on.

I have NO IDEA how to set permissions.

I fooled around with ACL settings, the command line, the web GUI, and the Windows 7 machine.... I am stuck!

Can someone walk me through it?

The doc here does not really explain http://napp-it.org/doc/downloads/napp-it.pdf

:(
Click to expand...

I found the ACL stuff really confusing as well... here's what I've been doing in Nexenta... I don't remember exactly for OI+Napp-It but it was similar.

First, create some users in Nexenta/Napp-It. Make sure guest access is enabled on the share, then connect to the share as the smb user (usually have to map a drive letter to specify a user to connect as, sometimes have to remove existing connections with the "net use" command) browse to the mapped drive letter, open up the drive, right-click, properties, security, edit and you should be able to edit the permissions... you can add a user to the folder permissions by clicking add, advanced, and "find now" will show a list of all users on the server.
 
roach9 said:
But it's really easy to do in FreeNAS as well.

Create share with read-only privs.
Then create admin share with full access.

Takes 15 seconds. Why isn't this an option in OI?!
Click to expand...

Its not OI vs FreeBSD but OI kernel-based CIFS server vs SAMBA (also available on OI)

On OI kernel based CIFS server is used per default instead of SAMBA because it is mostly faster,
has better Windows AD and ACL compatibility and is fully integrated into ZFS as a property.
The last thing (ZFS property) is the reason of a major difference to SAMBA - you cannot nest shares
and you cannot share a folder twice with different settings.


How to set shares

Goto napp-it menu ZFS folder and klick to off in the SMB colum, set a sharename
Klick on a sharename to stop sharing

1. open for all: share with guest=on
You are not asked for name/pw when you connect, everyone can modify,
You cannot (should not) restrict ACL settings

2. share it with different permissions for different users
Share the folder without guest=on

In this case, the folder is shared with the default, that only the owner (root) has full access.
You can connect from Windows only as root (with full permissions)

If you need access for other users, you must add ACL permissions like
everyone@=any permission
OI-user paul=any permission

Tipp:
If you create a OI-user with the same name as your Windows user (names are case sensitive)
and the same pw, you should be able to connect without entering name and password


How to set ACL
You can set folder/file ACL either
- from Windows when connectes as root (not possible with every Windows version, problem with home editions but also win7 ultimate)
- via CLI and Solaris version of chmod
- via napp-it and its ACL extension (basic user settings are free)

with napp-it ACL extension, open the extension, select the shared folder and add everyone@ and user permissions


Where are the problems
- Kernel based CIFS server is ACL only (set ACL instead of Unix permission - but be aware, they depend on each other)
use trivial ACL like everyone@, group@ or owner@ if you want ACL similar to unix permissions
- do not set any id-mappings in workgroup mode, you must use local unix-user - you cannot map them to other local users
- SMB passwords are different to Unix passwords. They must be created additional (The reason you must reenter root-pw after setup of napp-it)
- Windows and OI ACL behaves quite similar with one difference. Windows looks first on dany rules, then on allow while OI use the order of ACL
where the first matching entry do the job. From Windows, you cannot set order. This is mostly an item if you use deny rules.
 
Last edited:
Trepidati0n said:
And this is why when MS releases the next gen of storage spaces based on windows 8....many of us will go running. Seriously...if people here with moderate *nix experience are getting crushed by this issue what makes you think those of us willing to put our toes in the water won't say screw it?

WHS v1/v2 --> add user, use radio buttons to set permissions
OI --> read 127 page thread, your answer is in there somewhere
Click to expand...

Unless WHS does ZFS, it won't matter. And frankly, seeing how MS removed the storage pool from WHS, I don't know why you're optimistic about the next one.
 
Aesma said:
Unless WHS does ZFS, it won't matter. And frankly, seeing how MS removed the storage pool from WHS, I don't know why you're optimistic about the next one.
Click to expand...

I used WHS as an example because I haven't done Server 2008 (only 2003 which is ancient) to give a simple counter in that regards. The new version of storage spaces (which will be built into most of their server products) does pretety much what ZFS does (bit rot and all that fun stuff).

Don't think of my argument as WHS vs OI. Think of my argument of "any reasonable product with a GUI" vs OI + ZFS. Many of us would love to jump deeper into the *nix pool.
 
You must log in or register to reply here.
Back
Top