Christian Mauderer commented on a discussion: https://gitlab.rtems.org/rtems/rtos/rtems/-/work_items/5657#note_156668 Seems that I didn't manage to explain my point: There is a difference between author and Signed-off-by: The author is something, that is enforced by git. You can't make a commit without an author. But it doesn't say anything about whether the author accepts any rules of any project. A Signed-off-by line is something that is enforced by a project. So the project more or less says: If you want to contribute, accept these rules. The author of a commit accepted that by actively adding the Signed-off-by line. And that is visible in the git history and not only in some related merge request or some mail written by the author. If someone enables signed off by default in his config, that's his problem. That is like writing blank checks: The project can then write anything in the rules. So the big difference between author and Signed-off-by line is who is asking for the line. Author is tool enforced. Signed-off-by is project enforced. The cryptographic signature that you mentioned multiple times is a further dimension. It makes sure that an author doesn't change between commits. And it allows an author to prove that he is the author of a commit. But it doesn't say anything about whether the author accepted any project rules. A cryptographic signature would have advantages for a project from a security point of view. You make it sure that someone is not suddenly replaced by someone else who captured the identity. Or at least you make it harder because the private key is necessary. -- View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/work_items/5657#note_156668 You're receiving this email because of your account on gitlab.rtems.org. Unsubscribe from this thread: https://gitlab.rtems.org/-/sent_notifications/5-5o5h52r6fnkfqazmrahd8blo1-1d/unsubscribe | Manage all notifications: https://gitlab.rtems.org/-/profile/notifications | Help: https://gitlab.rtems.org/help
_______________________________________________ bugs mailing list [email protected] http://lists.rtems.org/mailman/listinfo/bugs
