Visitar URL original
Less permissive file modes for /Users mount by embray · Pull Request #1152 · boot2docker/boot2docker · GitHub
Skip to content
This repository was archived by the owner on Jan 1, 2021. It is now read-only.

Less permissive file modes for /Users mount - #1152

Open
embray wants to merge 1 commit into
boot2docker:masterfrom
embray:patch-1
Open

embray wants to merge 1 commit into
boot2docker:masterfrom
embray:patch-1

Conversation

@embray

@embray embray commented Mar 22, 2016

Copy link
Copy Markdown

When mounting C:\Users and the like, at least on Windows (I'm not sure if this is the same if the host OS is OSX in which case this might need adjusting) all files are given mode 777. This is a problem for a few reasons that I listed in sagemath/docker-images#19

Setting 600 for files seems to make sense, since for directories under /Users/C:\Users most files should be private anyways. I'm split on whether files should be executable or not, but ultimately going with not to be on the safe side.

When mounting C:\Users and the like, at least on Windows (I'm not sure if this is the same if the host OS is OSX in which case this might need adjusting) all files are given mode `777`.  This is a problem for a few reasons that I listed in sagemath/docker-images#19

Setting `600` for files seems to make sense, since for directories under `/Users`/`C:\Users` most files should be private anyways.  I'm split on whether files should be executable or not, but ultimately going with not to be on the safe side.
@tianon

tianon commented Nov 14, 2016

Copy link
Copy Markdown
Contributor

I'm hesitant on this one given that it's technically a breaking change. 😞

(Bind-mounting this directory into various containers running as various UIDs is likely to cause all sorts of trouble, for example.)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants