This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author kindloaf
Recipients brian.curtin, kindloaf
Date 2010-02-28.20:07:22
SpamBayes Score 1.652428e-08
Marked as misclassified No
Message-id <3ec02ba21002281207r593b69e5pe5e829bb884dbe18@mail.gmail.com>
In-reply-to <1265642584.58.0.729329564395.issue5802@psf.upfronthosting.co.za>
Content
Sorry for the delay, it's been a busy month.

I just tried python 3.1  If installed under c:\program files, the
access control list would be correct, only system & administrator
accounts get the modify privilege.

The default installation is to c:\python31, in which the access
control list has the issue that unprivileged users can modify it.

I guess a possible remedy to this is that after installation, the
setup program can just remove "authenticated users" from the access
control list, or at least remove the "modify" privilege from the
corresponding entry.

Thanks,
Hong

On Mon, Feb 8, 2010 at 7:23 AM, Brian Curtin <report@bugs.python.org> wrote:
>
> Brian Curtin <curtin@acm.org> added the comment:
>
> Is the situation any different if you install Python to "C:\Program Files"? This seems to be at least part of the reason IronPython installs to "C:\Program Files", which was discussed on the IronPython list [1] a few months ago.
>
>
> [1] http://lists.ironpython.com/pipermail/users-ironpython.com/2009-October/011345.html
>
> ----------
> nosy: +brian.curtin
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue5802>
> _______________________________________
>
History
Date User Action Args
2010-02-28 20:07:26kindloafsetrecipients: + kindloaf, brian.curtin
2010-02-28 20:07:23kindloaflinkissue5802 messages
2010-02-28 20:07:22kindloafcreate