Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Packages installed from wheel have incorrect permissions on Windows #1547

Closed
craigholm opened this Issue Feb 8, 2014 · 0 comments

Comments

Projects
None yet
2 participants

On Windows, packages installed from wheels retain the permissions of the installing user's temp directory, rather than inheriting the permissions of the destination site-packages directory. This means users who aren't administrators and aren't the installing user can't access the installed package.

Output from accesschk:

C:\Users\admin\AppData\Local\Temp>accesschk -q -d .
C:\Users\admin\AppData\Local\Temp
  RW NT AUTHORITY\SYSTEM
  RW BUILTIN\Administrators
  RW MYPC\admin

C:\Users\admin\AppData\Local\Temp>accesschk -q -d C:\Python33\Lib\site-packages
C:\Python33\Lib\site-packages
  RW BUILTIN\Administrators
  RW NT AUTHORITY\SYSTEM
  R  BUILTIN\Users

C:\Users\admin\AppData\Local\Temp>accesschk -q C:\Python33\Lib\site-packages\sqlalchemy\__init__.py
C:\Python33\Lib\site-packages\sqlalchemy\__init__.py
  RW NT AUTHORITY\SYSTEM
  RW BUILTIN\Administrators
  RW MYPC\admin

This doesn't seem to happen with packages that aren't installed from wheels. I would assume (and Process Monitor suggests) that the files installed from wheels are moved instead of copied (on Windows, files that are moved retain their permissions; new/copied files inherit the parent directory's). This was tested on Windows 7 64-bit with Python 2.7.6 and 3.3.3.

@dstufft dstufft modified the milestones: 1.6, 1.5.5 Mar 28, 2014

@dstufft dstufft modified the milestones: 1.6, 1.5.5 May 3, 2014

@dstufft dstufft closed this in #2135 Nov 20, 2014

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