Re: [OmniOS-discuss] SMB issues after r151014 -> r151018

Thanks, I didn't know that. I thought that it was better not to leave anything undefined, so after a positive match for the intended user, I added a deny for everyone else, thinking that the order of the ACLs also gave priority to the allow statements. After your explanation, I will just

Re: [OmniOS-discuss] SMB issues after r151014 -> r151018

On Fri, Apr 22, 2016 at 3:53 AM, Gordon Ross wrote: > I'm not sure how anyone ever gets access when your ACL has this ACE: > everyone@:rwxpdDaARWcCos:fd-:deny excellent catch! Deny ace's always get processed first in cifs, how could I miss that ;-) --

Re: [OmniOS-discuss] SMB issues after r151014 -> r151018

On Thu, Apr 21, 2016 at 9:53 PM, Gordon Ross wrote: > I'm not sure how anyone ever gets access when your ACL has this ACE: > everyone@:rwxpdDaARWcCos:fd-:deny > > Every long has the group ... Hah! Spell checkers - Gr! That should have read: Every

Re: [OmniOS-discuss] SMB issues after r151014 -> r151018

I'm not sure how anyone ever gets access when your ACL has this ACE: everyone@:rwxpdDaARWcCos:fd-:deny Every long has the group "everyone" as a member, therefore that ACE will match every logon. The ace also lists every possible permission, so nothing should get through, no matter

Re: [OmniOS-discuss] SMB issues after r151014 -> r151018

> On Apr 21, 2016, at 3:21 PM, Steven Ford wrote: > > Dan, since you made these commits, do you have any thoughts? Could these be > related? > Those are both kernel panic fixers (improper release after failure). The non-global-zone SMB/CIFS fixes went into r151016,

Re: [OmniOS-discuss] SMB issues after r151014 -> r151018

Hi Olaf On Thu, Apr 21, 2016 at 8:31 PM, Olaf Marzocchi wrote: > Thanks for the help. > Well first of all, how can the SMB server require everyone to have > read/execute access? no more private shares? > > Anyway, I got it working (for now) with: > > drwxr-xr-x+ 16 olaf

Re: [OmniOS-discuss] SMB issues after r151014 -> r151018

Olaf, The large number of changes between the version of OpenIndiana I was running and r151016 made it daunting to pinpoint the problem. If this is the same problem, I think it's safe to say the change was between r151014 and r151016. I'm not very savvy with the source code but I'll take a look.

Re: [OmniOS-discuss] SMB issues after r151014 -> r151018

Between r151014 and r151016, the only commits that look relevant to me are: https://github.com/omniti-labs/illumos-omnios/commit/8f5190a540d64d2debee6664bbc740e4c38f5b7f https://github.com/omniti-labs/illumos-omnios/commit/0f92170f1ec2737ee5a0e51b5f74093904811452 However, I am not familiar with

Re: [OmniOS-discuss] SMB issues after r151014 -> r151018

Thanks for the help. Well first of all, how can the SMB server require everyone to have read/execute access? no more private shares? Anyway, I got it working (for now) with: drwxr-xr-x+ 16 olaf olaf 16 Apr 21 20:25 olaf user:olaf:rwxpdDaARWcCos:fd-:allow

Re: [OmniOS-discuss] SMB issues after r151014 -> r151018

Yes I saw it but it was about guest access, while my case is about a share restricted only to its owner because I wanted to be sure that private data stay private: OmniOS-Xeon:~ olaf$ ls -lV /tank/home/ total 34 drwx--+ 15 olaf olaf 15 Oct 25 11:27 olaf

Re: [OmniOS-discuss] SMB issues after r151014 -> r151018

Olaf, This reminds me a a problem I was having after updating to 151016. I posted about it on stack exchange. http://serverfault.com/questions/762160/where-is-my-zfs-smb-share. My problem boiled down to the folder had needed everybody to have read permissions for the SMB share to appear. Hope

Re: [OmniOS-discuss] SMB issues after r151014 -> r151018

Yes it has. Did you see Gordon Ross's mail about it? Dan Sent from my iPhone (typos, autocorrect, and all) > On Apr 20, 2016, at 6:28 PM, Olaf Marzocchi wrote: > > Has anything changed about permissions with SMB2? ___

[OmniOS-discuss] SMB issues after r151014 -> r151018

I updated as indicated in the guide and to do that I had to uninstall some packages: serf@1.3.8,5.11-0.151014:20151015T214958Z apr-util@1.4.1,5.11-0.151014:20150508T204811Z apr@1.5.1,5.11-0.151014:20150529T175834Z uuid@1.41.14,5.11-0.151014:20150508T153803Z After reboot I got two main