All of lore.kernel.org
 help / color / mirror / Atom feed
From: Carlo Arenas <carenas@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Sep 2021, #01; Thu, 2)
Date: Mon, 6 Sep 2021 01:55:50 -0700	[thread overview]
Message-ID: <CAPUEspgnRFNRoFuEvP1hpY3iKukk3OnF4zk85wkdkmiVuPuRTw@mail.gmail.com> (raw)
In-Reply-To: <xmqq35qmiofp.fsf@gitster.g>

> * fs/ssh-signing (2021-08-29) 9 commits
>  - ssh signing: test that gpg fails for unknown keys
>  - ssh signing: tests for logs, tags & push certs
>  - ssh signing: duplicate t7510 tests for commits
>  - ssh signing: verify signatures using ssh-keygen
>  - ssh signing: provide a textual signing_key_id
>  - ssh signing: retrieve a default key from ssh-agent
>  - ssh signing: add ssh key format and signing code
>  - ssh signing: add test prereqs
>  - ssh signing: preliminary refactoring and clean-up
>
>  Use ssh public crypto for object and push-cert signing.
>
>  Will merge to 'next'.

This is causing ssh-keygen from OpenSSH 8.7 to segfault,
would it be reasonable to hold it until they get a chance to fix that?

Carlo

PS. provided them with a patch, and crash is reproducible with the tests

  parent reply	other threads:[~2021-09-06  8:56 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-02 22:48 What's cooking in git.git (Sep 2021, #01; Thu, 2) Junio C Hamano
2021-09-03  0:59 ` Philippe Blain
2021-09-03  4:38   ` Junio C Hamano
2021-09-03  2:25 ` Taylor Blau
2021-09-03  4:38   ` Junio C Hamano
2021-09-06  8:55 ` Carlo Arenas [this message]
2021-09-06 10:02   ` Ævar Arnfjörð Bjarmason
2021-09-06 21:52     ` Junio C Hamano
2021-09-07 17:39       ` Junio C Hamano
2021-09-06 10:36 ` Han-Wen Nienhuys
2021-09-06 21:55   ` Junio C Hamano
2021-09-06 22:21     ` Ævar Arnfjörð Bjarmason
2021-09-07 10:13 ` Ævar Arnfjörð Bjarmason
2021-09-07 17:15   ` Junio C Hamano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAPUEspgnRFNRoFuEvP1hpY3iKukk3OnF4zk85wkdkmiVuPuRTw@mail.gmail.com \
    --to=carenas@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.