Apple Event: May 7th at 7 am PT

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

File permissions issue on OS X El Capitan and SMB share

Since updating to El Capitan all files in SMB and AFP shares have the 'x' bit set, even though the premissions were properly displayed on earlier OS. The SMB share is shared by Samba on Ubuntu, while the AFP share is shared by Apple Time Capsule. I couldn't find an option to disable this and I see no reason in not preserving the permissions. Is there a fix or a workaround for this issue? Thanks!


See also: http://stackoverflow.com/questions/33090925/file-permissions-issue-on-os-x-el-ca pitan-and-smb-share/33093076#33093076

MacBook Pro with Retina display, OS X El Capitan (10.11)

Posted on Oct 12, 2015 7:32 PM

Reply
Question marked as Best reply

Posted on Oct 12, 2015 7:42 PM

There no longer is a need to repair permissions. All permissions are locked under the new "rootless" environment. They no longer require repairing.

22 replies

Mar 9, 2016 12:51 PM in response to eladts

Thanks for the info on sshfs.


Only other reason to add a comment is a "+1 bump" to this. I understand that El Capitan got rid of most native NTFS-based connections, but I thought the intent of SMB protocol was that it was transparent to whether there was NTFS behind it or not. Not sure if they are related, but it seems suspect that I can't connect r/w to a simple Windows share anymore.


Frustrating - this smacks more of a technical marketing strategy than interoperability issue.

Mar 9, 2016 1:30 PM in response to jasiakman

Update and mea culpa - I think I did discover it to be a share permission issue. Not sure why, but it seems that regardless of user, an "everyone 'read'" permission needs to be set on the Windows filesystem share, and not just rw for the SMB user on the folder.


Not sure why this is, and everyone else's mileage may vary, but this doesn't have anything to do with the NTFS changes. It *might* have something to do with how El Capitan changed its SMB API/interaction layer, but I found a workaround at least.


Apologies, good luck, and carry on.

Mar 21, 2016 5:47 PM in response to eladts

Hello eldats et al,


As usual, it is all about the "All Mighty Dollar".


Historical Gossip:

Some years ago, as new technology continued developing and those developers wished to trap you into only using their system, each mega-conglomarete developed their own file formatting system (smb://, afp://, nfs://, ntfs://, etc.) Some are so similar, than in reality, I personally do not see the point, but I digress. Big Dollar Corporations were determined to keep their money in their pockets rather than keep up with technology development. Fast forward to 4 or 5 years ago. The big wigs of the "Software Developing Community" decided to create a unified file sharing system, one that will be more efficient than all the others combined. Left stage entry for: cifs://. Every OS's was on board until, gramps Win decided to pull out of the joint effort, created what we could call: smb2 but didn't "officially" tell the rest of the team.


Today:

The smb:// that you see on the Apple's System Preference File Sharing window is a legacy command (smb1://) that not even MS supports any longer. However, the development of the interpreter was and is one of the most successful achievements in the history of software development since putting a man on the Moon with technology equivalent to that of a Casio watch.


Short answer A:

Use Terminal to enable NTFS support on Hardrive in El Capitan

We do not talk about why Mac OS X does not support full NTFS itself or why This feature is hidden from Mac OS X. We absolutely can use Terminal command to manually Enable NTFS write support. Let’s see how it works.

  • To run Terminal: Applications > Utilities > Terminal
  • Type: sudo nano /etc/fstab
  • Fill your user password
  • You now are brought to a program called nano and it’s the text editor that’s built into Terminal. The file that you’ll edit is called
    stab.
  • Within nano type:LABEL=DRIVE_NAME none ntfs rw,auto,nobrowse

Notice: DRIVE_NAME is the name of the drive. The drive’s name should contain no spaces, as adding a space to the configuration file would tell your Mac to interpret whatever’s after that space as a separate command. If your DRIVE_NAME is made up of two words separated with a space, for example, “NO NAME”, you have to add a “\” before the space for the system to recognize the space. For example, “NO\ NAME”.

Finally, you just Control-O to save the file and Control-X to exit nano.

In Finder, verify the Volume is recognized and Mount it.

Short answer B

On the sharing server one have to options:

1. Un-click the share using smb:// in the Options pane. This way el capitan will know that all incoming files are afp://.

2. if one do not have option of removing smb:// all together from the alternatives, then let the receiving end handle the files.


On the receiving side, always mount the servers that so graciously have been shared with you, and to do so:

1. Open a new Finder window.

2. From the Finder Menu click on: Go -> Connect to Server (or what is the same, press: cmdK simultaneously)

3. Use the filing system command cifs:// and the server IP address a / and a folder name if it is necessary: cifs://192.27.10.254/

4. Return to the Finder Menu click on: Go -> Connect to Server (or what is the same, press: cmdK simultaneously)

5. and click the + sign to save the address to favorites.

If the server doesn't automatically mounts at Boot, the server will remain listed on your Finder window to easily activate.

Good Luck.

May 6, 2016 1:23 PM in response to Wide_Receiver

Wide_Receiver wrote:


Today:

The smb:// that you see on the Apple's System Preference File Sharing window is a legacy command (smb1://) that not even MS supports any longer. However, the development of the interpreter was and is one of the most successful achievements in the history of software development since putting a man on the Moon with technology equivalent to that of a Casio watch.


Apple actually introduced SMB3 in OS X El Capitan:


User uploaded file


https://www.apple.com/osx/all-features/pdf/osx_elcapitan_core_technologies_overv iew.pdf


Unless there's something I'm missing.

May 24, 2016 4:32 AM in response to eladts

Hi eladts, did you find any solution for this.

We're having the same problem here.


Connecting to a Ubuntu Server with SMB1 from a Mac running 10.9 = no problems

Connecting to the same Server with SMB1 from a Mac running 10.11 = we see the execute bit set, where should be none


With SMB2/3 the permissions become totaly wrong on client side.

File permissions issue on OS X El Capitan and SMB share

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.