You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Merely a suggestion / discussion point, so please don't take this as a criticism!
Has the Keystone firmware development team considered making signed commits mandatory for the firmware related repositories?
Since this is some pretty critical code, it would add some further re-assurance if the core developers were utilising GPG (Yubikey, etc) hardware keys to sign their commits, lowering the likelihood of a (compromised) developer compromising any of the code (accidentally or not).
Your team and code complexity are growing pretty rapidly, so managing these sorts of easy to solve "attack" surfaces earlier, rather than later can prevent bigger security headaches later on, in my opinion (and experience).
Curious what your thoughts on this are, or hearing more on what your current policy is.
The text was updated successfully, but these errors were encountered:
Merely a suggestion / discussion point, so please don't take this as a criticism!
Has the Keystone firmware development team considered making signed commits mandatory for the firmware related repositories?
Since this is some pretty critical code, it would add some further re-assurance if the core developers were utilising GPG (Yubikey, etc) hardware keys to sign their commits, lowering the likelihood of a (compromised) developer compromising any of the code (accidentally or not).
Your team and code complexity are growing pretty rapidly, so managing these sorts of easy to solve "attack" surfaces earlier, rather than later can prevent bigger security headaches later on, in my opinion (and experience).
Curious what your thoughts on this are, or hearing more on what your current policy is.
The text was updated successfully, but these errors were encountered: