All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>
To: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
	keys@kernel.org,  Juri Lelli <juri.lelli@redhat.com>
Subject: Re: New key
Date: Tue, 17 Nov 2026 12:16:03 +0100	[thread overview]
Message-ID: <avtNGdnmyBUYEgTn@monoceros> (raw)
In-Reply-To: <CA+JHD93y3917AhdpaT_WoNjz_cGk=aFmXRMW32wW=ug0jbWwEA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1679 bytes --]

Hello Arnaldo,

On Mon, Nov 16, 2026 at 02:20:56PM -0300, Arnaldo Carvalho de Melo wrote:
> On Mon, Nov 16, 2026, 1:59 PM Uwe Kleine-König <u.kleine-koenig@baylibre.com>
> wrote:
> 
> > On Fri, Nov 13, 2026 at 10:22:52AM -0300, Arnaldo Carvalho de Melo wrote:
> > > Hi,
> > >
> > >       Here is my new key, with an expiry date, signed by my previous
> > > one and by Juri Lelli.
> >
> > What is your plan with the previous key (D65016F35352AA40)?
> >
> > I'm asking because:
> >
> >         $ sq cert lint < keys/D65016F35352AA40.asc
> >         Certificate D65016F35352AA40 is not valid under the standard
> > policy: No binding signature at time 2026-11-16T16:57:45Z
> >         Certificate D65016F35352AA40 contains a User ID (Arnaldo Carvalho
> > de Melo (kernel.org) <acme@infradead.org>) protected by SHA-1
> >         Certificate D65016F35352AA40 contains a User ID (Arnaldo Carvalho
> > de Melo <acme@kernel.org>) protected by SHA-1
> >         Certificate D65016F35352AA40, key 4C6AB5766A82C4CC uses a
> > SHA-1-protected binding signature.
> >         [...]
> >
> 
> 
> I'll try to follow Konstantin's instructions to remove those SHA-1 self
> cert signatures and add an expiration date one year from now. Please advise
> if I need to do anything else.

That sounds good.

> Juri tells me he'll send his new key tomorrow, replying to Konstantin's
> question in another message.

That, too. Juri now sent his certificate, but Juris signature on your
certificate wasn't imported when Konstantin added it. So the keyblock
you sent must be reimported once Juri's certificate is added to benefit
from that.

Best regards
Uwe

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  parent reply	other threads:[~2026-11-17 11:16 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-13 13:22 New key Arnaldo Carvalho de Melo
2026-11-16 16:19 ` Konstantin Ryabitsev
2026-11-17  6:55   ` Juri Lelli
2026-11-17 11:02     ` Revoked certificates not imported by current scripts [Was: Re: New key] Uwe Kleine-König
2026-11-16 16:59 ` New key Uwe Kleine-König
     [not found]   ` <CA+JHD93y3917AhdpaT_WoNjz_cGk=aFmXRMW32wW=ug0jbWwEA@mail.gmail.com>
2026-11-17 11:16     ` Uwe Kleine-König [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-05-09  9:51 Konrad Dybcio
2023-05-09 18:49 ` Konstantin Ryabitsev
2023-04-14 15:30 Konrad Dybcio
2023-04-17 16:35 ` Konstantin Ryabitsev
2023-02-09 10:53 David Gibson
2023-02-09 20:41 ` Konstantin Ryabitsev
2023-02-10  0:06   ` David Gibson
     [not found]   ` <Y+mh9AALS6uCC/0A@yekko>
2023-02-21 22:28     ` Konstantin Ryabitsev
2023-02-22  3:42       ` David Gibson
2023-02-23 16:19         ` Konstantin Ryabitsev
2023-02-24  4:05           ` David Gibson
2023-02-24  4:21             ` David Gibson

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=avtNGdnmyBUYEgTn@monoceros \
    --to=u.kleine-koenig@baylibre.com \
    --cc=acme@kernel.org \
    --cc=arnaldo.melo@gmail.com \
    --cc=juri.lelli@redhat.com \
    --cc=keys@kernel.org \
    /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.