# Modernise .gitconfig Signing Block Name

2 messages from 2024-03-02 to 2024-03-02. Participants: admin@inferencium.net, Junio C Hamano.
Thread: https://gitlist.dev/t/61040

## admin@inferencium.net, 2024-03-02 20:01

Subject: Modernise .gitconfig Signing Block Name
Message-ID: <KfyeAjLLXySd6IEKwEmOvrDqtBIhoCRPon7r8IuUIwPbUhlf8XR0CCmqP3Y5D-8hur57_SFQPqwk0xOA7p0h6xqw48ZMdNbzTBPN2hh9Ph4=@inferencium.net>
URL: https://gitlist.dev/e/KfyeAjLLXySd6IEKwEmOvrDqtBIhoCRPon7r8IuUIwPbUhlf8XR0CCmqP3Y5D-8hur57_SFQPqwk0xOA7p0h6xqw48ZMdNbzTBPN2hh9Ph4%3D%40inferencium.net

```
As SSH has been supported as a signing method for a while now in Git, the block name `gpg` within `.gitconfig` no longer makes sense as it's not the only method of signing commits and tags. I propose renaming `[gpg]` to something such as `[sig]` or `[sign]`. The current method of achieving this is `format = ssh` within the `[gpg]` block, which would be the same (hypothetically) as redefining SHA-1 to be SHA-256 via `format = sha256` within a `[sha1]` block; it really doesn't make sense in 2024 for it to be this way.

The outcome of this would be using `format = gpg` or `format = ssh` within a `[sig]` or `[sign]` block (or whatever anyone comes up with which could be better).

For backwards compatibility, `[gpg]` can also be allowed as an alias for the new name. The default could also be `format = gpg`, as it's still the most widely-used signing method.

```

## Junio C Hamano, 2024-03-02 21:08

Subject: Re: Modernise .gitconfig Signing Block Name
Message-ID: <xmqqsf18wddm.fsf@gitster.g>
URL: https://gitlist.dev/e/xmqqsf18wddm.fsf%40gitster.g
In-Reply-To: <KfyeAjLLXySd6IEKwEmOvrDqtBIhoCRPon7r8IuUIwPbUhlf8XR0CCmqP3Y5D-8hur57_SFQPqwk0xOA7p0h6xqw48ZMdNbzTBPN2hh9Ph4=@inferencium.net>

```
admin@inferencium.net writes:

> For backwards compatibility, `[gpg]` can also be allowed as an
> alias for the new name. The default could also be `format = gpg`,
> as it's still the most widely-used signing method.

Sounds good.  Patches welcome.

Thanks.

```
