[JIRA] (OVIRT-830) Vdsm lost its "Forge Author" permission?

[eyal edri [Administrator] (oVirt JIRA)]

    [ https://ovirt-jira.atlassian.net/browse/OVIRT-830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=22603#comment-22603 ] 

eyal edri [Administrator] commented on OVIRT-830:
-------------------------------------------------

You don't see any security implication with this? any user (even malicious) has the potential to forge the author identity? 
Shouldn't this be restricted to maintainers of the project? 

[~sbendavi at redhat.com]

> Vdsm lost its "Forge Author" permission?
> ----------------------------------------
>
>                 Key: OVIRT-830
>                 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-830
>             Project: oVirt - virtualization made easy
>          Issue Type: By-EMAIL
>            Reporter: danken
>            Assignee: infra
>
> Until recently, any registered user could take on somebody else's change,
> and post a new patchset to it.
> It's very useful when someone wants to fix a typo in someone else's
> code, or when we need to take on a work of a sick/vacating developer.
> Please amend this. I'm not 100% sure, but it could be fix by setting
> "Forge Author" on the vdsm project.
> https://gerrit-review.googlesource.com/Documentation/access-control.html#category_forge_author



--
This message was sent by Atlassian JIRA
(v1000.526.2#100018)