Hey all, I'm testing staging/1.6.0 and seem to be having an issue with recording permissions where I am unable to see session recordings in the browser without changing the permissions of every session folder and session file created by guacamole-server.
I have a recording folder that is visible to both guacamole-server and guacamole-client with 777 permissions. When opening a session, I see confirmation that a file was opened for recording in the logs for guacamole-server. I am manually able to traverse the files outside of both docker containers and see that the files from the session were created but the session folder is created with 750 permissions and the recording files are created with 640 permissions. If I do a simple `chmod -R o+rx <session-id>` on the session recording folder to add back read execute permission for "others", it immediately resolves the issue and I can see the recordings in the browser again. If I look at the user id for the guacamole-server docker container it is 1000 and the user id for the guacamole-client container is 1001. I looked at the code differences between staging/1.6.0 and 1.5.5 and it seems that some changes were made to the file permissions for "others" when creating the folder and the recordings which I suspect might be where this issue originates from. Would love to hear if any others are experiencing this issue. Thanks! -Nathaniel Belles
