Git signed pushes #145051
Replies: 1 comment
-
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Product Feedback
Body
I realize that GitHub at this time does not support Git signed pushed (as has been mentioned and solved in this #23515, but due to the increase in security awareness of repositories (public and private), it would be nice to have the ability to push with assurance that the commits will not be replayed out of context (the purpose of signed pushes)
This is particularly useful since GitHub supports signed commits (which can have a false sense of security for repository owners if a successful replay attack is performed), but no signed pushes (which would eliminate the security hole if it is used by the pusher and a replay attack is attempted).
A good explanation of this can be found here (pulled on 11/19/2024 17:15 UTC): https://people.kernel.org/monsieuricon/signed-git-pushes
Beta Was this translation helpful? Give feedback.
All reactions