Skip to main content
T
twosenses
Participant
October 3, 2016

P: Ignoring ACLs on Mac OS X

  • October 3, 2016
  • 14 replies
  • 604 views

I wanted to submit a bug report after running into this issue with a client and confirming it on my own system. This is with Adobe Photoshop CC 2015.5. According to the client the issue did not exist on 2015.4

The client has a SAN that uses ACLs to control permissions due to having multiple AD groups in use. They recently updated to Photoshop 2015.5 and immediately started having permission issues with PSD files. They were no longer able to save PSDs that other users had created. 

In looking into the issue I found that even though the ACLs were correct on the filesystem Photoshop was completely ignoring them and was defaulting to the POSIX permissions. POSIX on OS X are restricted to Owner R/W by default so this quickly became a problem. I verified it was only looking at POSIX by modifying the POSIX permissions on a test file (opened it to rwx-rw-r--) so that the group could write the file. This allowed the user to save the file which had been created by another user.

I also verified this on my own system running 2015.5 and found that when I created a new PSD file in a folder with ACLs the ACLs were not inherited by the PSD file. I then changed the POSIX permissions and verified that ACLs were being ignored. 

In my eyes (and the client's eyes) this is a major issue. Many people utilize ACLs in their shared storage environments for various reasons (like Premiere coming up with it's own POSIX permissions and zip files) and Photoshop ignoring those ACLs will cause problems. I am aware that you can change the POSIX after the fact and modify the umask to 002 but at the same time I shouldn't have to mess around with file system permissions to get Photoshop to work correclty in a shared storage environment. 

I do hope that this is solved in the next release of Photoshop.

    This topic has been closed for replies.

    14 replies

    Show previous replies
    J
    J453
    Legend
    October 4, 2016
    Ok. As far as I know, there weren't any major to changes to this area of the app. That said, if we can determine for for sure that it did work properly for them in a version Photoshop, that might provide some clues. It may have been some change at the OS version - that they may have coincided with a PS update. In either case, having a repro state where it works and then doesn't helps our cause for tracking down.
    T
    twosensesAuthor
    Participant
    October 4, 2016
    Jeff,

    I went ahead and installed 2015.2.1 and the behavior was exactly the same. No ACL inherited from the parent folder and POSIX permissions were the only permissions used.

    I'll need to check with the client on what previous version they were using though it might have been 2014 which I'll test as well.

    Ethan 
    T
    twosensesAuthor
    Participant
    October 4, 2016
    Hi Jeff,

    I'm 10.11.4 and the client is also running 10.11 though I need to verify the point release.

    Apologies for screwing up the release number, I'm not sure how I managed to do that. I'll go ahead and put on 2015.2.1 alongside my 2015.5 install and let you know what happens. The client is using 2015.5 due to it fixing some bugs they were concerned about so I don't know if they would want to downgrade but I'll see if I can get them to sideload 2015.2.1

    Ethan
    J
    J453
    Legend
    October 3, 2016
    Hi Ethan,

    Can you confirm what version of OS X is running on these systems? Additionally, there was no 2015.4 update. The update prior was 2015.2.1. Can you confirm the problem does not occur with 2015.2.1? You can install the prior version side by side with 2015.5.x. Info here: https://helpx.adobe.com/creative-cloud/help/download-install-app.html#Installpreviousversionsofapps
    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices