What steps will reproduce the problem?
1. Define a repo as "Restrict View, Clone, & Push" in order to give read permissions
only to selected users/teams (include "user A" here, not "user B")
2. As user A, create a fork of the repository accepting the default settings
3. As user B (no access to the upstream repo), browse to the user page of user A (/users/a)
and click on the link to forked repository (and browse / clone it).
4. User B has now read access to a repository, which was not intended to be seen by
him.
What is the expected output? What do you see instead?
- I think the fork should inherit the same permission level as the upstream repo. Adding
a "view for all" permission is not a good default.
- If the fork is completely private by default, or if all the upstream's users/teams
should be added, could be discussed (configured?).
- Probably the best would be a "inherit from upstream" setting. This would also keep
the permissions of the fork in sync with the upstream repo. I think this would be the
most sensible default (with an option to override to custom access permissions).
What version of the product are you using? On what operating system?
- 1.6.0 on Tomcat
Reported by steffen@steffen-gebert.de on 2014-09-05 07:38:23
The text was updated successfully, but these errors were encountered:
Originally reported on Google Code with ID 495
Reported by
steffen@steffen-gebert.de
on 2014-09-05 07:38:23The text was updated successfully, but these errors were encountered: