Can't reauthorize with endpoint using new GPG key

Can't reauthorize with endpoint using new GPG key

[Duje Mihanović]

Hi,

After replacing my GPG key, I was unable to reflect a patch series with the 
following error:

Error from endpoint: No matching key, please complete web auth first.

When I run `b4 send --web-auth-new`, I get the following error:

500 response from the endpoint: {"result": "error", "message": 
"i=duje.mihanovic@skole.hr;s=default is already authorized"}

After doing some short digging around b4 and korg documentation I couldn't 
find a way to revoke the old authorization and be able to use my new GPG key. 
Is there a way to do this?

Regards,
-- 
Duje

Re: Can't reauthorize with endpoint using new GPG key

[Konstantin Ryabitsev]

On Mon, Jul 29, 2024 at 11:07:41PM GMT, Duje Mihanović wrote:
> Hi,
> 
> After replacing my GPG key, I was unable to reflect a patch series with the 
> following error:
> 
> Error from endpoint: No matching key, please complete web auth first.
> 
> When I run `b4 send --web-auth-new`, I get the following error:
> 
> 500 response from the endpoint: {"result": "error", "message": 
> "i=duje.mihanovic@skole.hr;s=default is already authorized"}
> 
> After doing some short digging around b4 and korg documentation I couldn't 
> find a way to revoke the old authorization and be able to use my new GPG key. 
> Is there a way to do this?

Right, updating existing keys is currently not supported -- because I need to
figure out how to do it sanely and securely. 

Your best bet is to define your new key as a different selector.
Add the following to your ~/.gitconfig:

    [patatt]
    signingkey = openpgp:YOURNEWKEYID
    selector = 20240729

For example, for me:

    [patatt]
    signingkey = openpgp:E63EDCA9329DD07E
    selector = 20240729

This should let you register your new key with the web endpoint. You can make
selector anything else, including your keyid, it just needs to be defined so
it's not "default".

Sorry for the lack of documentation on this.

-K

Re: Can't reauthorize with endpoint using new GPG key

[Duje Mihanović]

On Monday, July 29, 2024 11:19:44 PM GMT+2 Konstantin Ryabitsev wrote:
> Your best bet is to define your new key as a different selector.
> Add the following to your ~/.gitconfig:
> 
>     [patatt]
>     signingkey = openpgp:YOURNEWKEYID
>     selector = 20240729
> 
> For example, for me:
> 
>     [patatt]
>     signingkey = openpgp:E63EDCA9329DD07E
>     selector = 20240729
> 
> This should let you register your new key with the web endpoint. You can 
make
> selector anything else, including your keyid, it just needs to be defined so
> it's not "default".

Worked, thanks!

> Sorry for the lack of documentation on this.

I suppose I could send a patch to document this if I get around to writing 
one?

-- 
Duje