You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@fineract.apache.org by Kristof Jozsa <kr...@gmail.com> on 2025/02/06 17:28:34 UTC
[PROPOSAL] Git signed commits
Hi all,
I'd like to bring up an idea that could help us strengthen the security and
integrity of our codebase: *enabling signed commits* (
https://git-scm.com/book/ms/v2/Git-Tools-Signing-Your-Work).
Here’s why I think this is worth considering:
1.
*Trust and Authenticity*: Signed commits verify that the code changes
are coming from a trusted contributor, reducing the risk of impersonation
or malicious commits.
2.
*Accountability*: It ensures that every commit is tied to a specific
developer, making it easier to track contributions and maintain
transparency.
3.
*Security Best Practice*: Many opensource projects are adopting signed
commits as a standard practice to protect against tampering.
I think it's a small change with nice benefits, and setting it up is pretty
straightforward. If this sounds good, I’d be happy to help draft a quick
guide or collaborate on implementing it.
Let me know what you think..
Kristof
Re: [PROPOSAL] Git signed commits
Posted by Kristof Jozsa <kr...@gmail.com>.
Thanks for all your support! The vote is now complete, and work has begun
to introduce signed commits.
K
On Sat, Feb 8, 2025 at 1:12 AM James Dailey <ja...@gmail.com> wrote:
> +1
>
> You can close the VOTE after 72 hrs and tally it up. But it looks like
> no objections so maybe start the process of writing up the guide.
>
>
> On Fri, Feb 7, 2025 at 9:25 AM Inzemamul Haq <in...@gmail.com>
> wrote:
>
>> +
>>
>> On Fri, Feb 7, 2025 at 10:53 PM VICTOR MANUEL ROMERO RODRIGUEZ <
>> victor.romero@fintecheando.mx> wrote:
>>
>>> +1
>>>
>>> In the quick guide the verification process of the commit/tag signature
>>> must be included.
>>>
>>> El vie, 7 feb 2025 a las 11:01, Adam Monsen (<am...@mifos.org>)
>>> escribió:
>>>
>>>> +1
>>>>
>>>
Re: [PROPOSAL] Git signed commits
Posted by James Dailey <ja...@gmail.com>.
+1
You can close the VOTE after 72 hrs and tally it up. But it looks like no
objections so maybe start the process of writing up the guide.
On Fri, Feb 7, 2025 at 9:25 AM Inzemamul Haq <in...@gmail.com> wrote:
> +
>
> On Fri, Feb 7, 2025 at 10:53 PM VICTOR MANUEL ROMERO RODRIGUEZ <
> victor.romero@fintecheando.mx> wrote:
>
>> +1
>>
>> In the quick guide the verification process of the commit/tag signature
>> must be included.
>>
>> El vie, 7 feb 2025 a las 11:01, Adam Monsen (<am...@mifos.org>)
>> escribió:
>>
>>> +1
>>>
>>
Re: [PROPOSAL] Git signed commits
Posted by Inzemamul Haq <in...@gmail.com>.
+
On Fri, Feb 7, 2025 at 10:53 PM VICTOR MANUEL ROMERO RODRIGUEZ <
victor.romero@fintecheando.mx> wrote:
> +1
>
> In the quick guide the verification process of the commit/tag signature
> must be included.
>
> El vie, 7 feb 2025 a las 11:01, Adam Monsen (<am...@mifos.org>)
> escribió:
>
>> +1
>>
>
Re: [PROPOSAL] Git signed commits
Posted by VICTOR MANUEL ROMERO RODRIGUEZ <vi...@fintecheando.mx>.
+1
In the quick guide the verification process of the commit/tag signature
must be included.
El vie, 7 feb 2025 a las 11:01, Adam Monsen (<am...@mifos.org>) escribió:
> +1
>
Re: [PROPOSAL] Git signed commits
Posted by Adam Monsen <am...@mifos.org>.
+1
Re: [PROPOSAL] Git signed commits
Posted by Ed Cable <ed...@mifos.org>.
+1
On Fri, Feb 7, 2025 at 3:00 AM Petri Tuomola <pe...@tuomola.org> wrote:
> Agreed
>
> +1
>
> On Fri, 7 Feb 2025 at 18:55, Aleksandar Vidakovic <
> cheetah@monkeysintown.com> wrote:
>
>> ... definitely a good idea and no effort at all for the individual
>> committer...
>>
>> +1
>>
>> On Thu, Feb 6, 2025 at 6:30 PM Kristof Jozsa <kr...@gmail.com>
>> wrote:
>>
>>> Hi all,
>>>
>>> I'd like to bring up an idea that could help us strengthen the security
>>> and integrity of our codebase: *enabling signed commits* (
>>> https://git-scm.com/book/ms/v2/Git-Tools-Signing-Your-Work).
>>>
>>> Here’s why I think this is worth considering:
>>>
>>> 1.
>>>
>>> *Trust and Authenticity*: Signed commits verify that the code
>>> changes are coming from a trusted contributor, reducing the risk of
>>> impersonation or malicious commits.
>>> 2.
>>>
>>> *Accountability*: It ensures that every commit is tied to a specific
>>> developer, making it easier to track contributions and maintain
>>> transparency.
>>> 3.
>>>
>>> *Security Best Practice*: Many opensource projects are adopting
>>> signed commits as a standard practice to protect against tampering.
>>>
>>> I think it's a small change with nice benefits, and setting it up is
>>> pretty straightforward. If this sounds good, I’d be happy to help draft a
>>> quick guide or collaborate on implementing it.
>>>
>>> Let me know what you think..
>>> Kristof
>>>
>>>
--
*Ed Cable*
President/CEO, Mifos Initiative
edcable@mifos.org | Skype: edcable | Mobile: +1.484.477.8649
*Collectively Creating a World of 3 Billion Maries | *http://mifos.org
<http://facebook.com/mifos> <http://www.twitter.com/mifos>
Re: [PROPOSAL] Git signed commits
Posted by Petri Tuomola <pe...@tuomola.org>.
Agreed
+1
On Fri, 7 Feb 2025 at 18:55, Aleksandar Vidakovic <ch...@monkeysintown.com>
wrote:
> ... definitely a good idea and no effort at all for the individual
> committer...
>
> +1
>
> On Thu, Feb 6, 2025 at 6:30 PM Kristof Jozsa <kr...@gmail.com>
> wrote:
>
>> Hi all,
>>
>> I'd like to bring up an idea that could help us strengthen the security
>> and integrity of our codebase: *enabling signed commits* (
>> https://git-scm.com/book/ms/v2/Git-Tools-Signing-Your-Work).
>>
>> Here’s why I think this is worth considering:
>>
>> 1.
>>
>> *Trust and Authenticity*: Signed commits verify that the code changes
>> are coming from a trusted contributor, reducing the risk of impersonation
>> or malicious commits.
>> 2.
>>
>> *Accountability*: It ensures that every commit is tied to a specific
>> developer, making it easier to track contributions and maintain
>> transparency.
>> 3.
>>
>> *Security Best Practice*: Many opensource projects are adopting
>> signed commits as a standard practice to protect against tampering.
>>
>> I think it's a small change with nice benefits, and setting it up is
>> pretty straightforward. If this sounds good, I’d be happy to help draft a
>> quick guide or collaborate on implementing it.
>>
>> Let me know what you think..
>> Kristof
>>
>>
Re: [PROPOSAL] Git signed commits
Posted by Aleksandar Vidakovic <ch...@monkeysintown.com>.
... definitely a good idea and no effort at all for the individual
committer...
+1
On Thu, Feb 6, 2025 at 6:30 PM Kristof Jozsa <kr...@gmail.com>
wrote:
> Hi all,
>
> I'd like to bring up an idea that could help us strengthen the security
> and integrity of our codebase: *enabling signed commits* (
> https://git-scm.com/book/ms/v2/Git-Tools-Signing-Your-Work).
>
> Here’s why I think this is worth considering:
>
> 1.
>
> *Trust and Authenticity*: Signed commits verify that the code changes
> are coming from a trusted contributor, reducing the risk of impersonation
> or malicious commits.
> 2.
>
> *Accountability*: It ensures that every commit is tied to a specific
> developer, making it easier to track contributions and maintain
> transparency.
> 3.
>
> *Security Best Practice*: Many opensource projects are adopting signed
> commits as a standard practice to protect against tampering.
>
> I think it's a small change with nice benefits, and setting it up is
> pretty straightforward. If this sounds good, I’d be happy to help draft a
> quick guide or collaborate on implementing it.
>
> Let me know what you think..
> Kristof
>
>