Personal Git repository transfer privacy check is stricter than normal privacy rules

Bug #1884019 reported by William Grant
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
Low
Unassigned

Bug Description

GitRepository._checkPersonalPrivateOwnership rejects a repository transfer to a person or public team whenever the repository is private. But PersonalGitNamespace.getAllowedInformationTypes permits people and non-private teams to use FREE_INFORMATION_TYPES, which includes the private PRIVATESECURITY and USERDATA types. This means it's possible for someone to create a personal private Git repository, make it public, transfer it, then make it private again, but it's not possible to transfer it directly.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.