All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Lautrbach <lautrbach@redhat.com>
To: Jason Zaman <jason@perfinion.com>, selinux@vger.kernel.org
Cc: Jason Zaman <jason@perfinion.com>
Subject: Re: [PATCH] scripts: GPG Sign overall tarball in release
Date: Fri, 30 Jan 2026 07:35:35 +0100	[thread overview]
Message-ID: <871pj7r4js.fsf@redhat.com> (raw)
In-Reply-To: <20260130014405.47915-1-jason@perfinion.com>

Jason Zaman <jason@perfinion.com> writes:

> In the release script, there was a GPG sig for each component tarball.
> There is also the overall script with all subdirectories at once, but it
> was missing the gpg sig.
>
> Reported-by: Petr Lautrbach <lautrbach@redhat.com>
> Signed-off-by: Jason Zaman <jason@perfinion.com>

Acked-by: Petr Lautrbach <lautrbach@redhat.com>

> ---
>
> 3.10-rc1 and -rc2 had the signature missing on the upload to github.
> I've signed and uploaded to those releases. The files I signed were the
> local ones on my machines, ie did not download from github and sign, so
> there is no risk of any changes/mitm.
>
>  scripts/release | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/scripts/release b/scripts/release
> index dddbdf22..94125a7a 100755
> --- a/scripts/release
> +++ b/scripts/release
> @@ -53,6 +53,7 @@ for COMPONENT in "${DIRS[@]}"; do
>  done
>  
>  git archive -o "$DEST/selinux-${RELEASE_TAG}.tar.gz" --prefix="selinux-${RELEASE_TAG}/" "${RELEASE_TAG}"
> +gpg -b -a "$DEST/selinux-${RELEASE_TAG}.tar.gz"
>  
>  echo "Add the following to the $WIKIDIR/Releases.md wiki page:"
>  
> -- 
> 2.52.0


      reply	other threads:[~2026-01-30  6:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-30  1:44 [PATCH] scripts: GPG Sign overall tarball in release Jason Zaman
2026-01-30  6:35 ` Petr Lautrbach [this message]

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=871pj7r4js.fsf@redhat.com \
    --to=lautrbach@redhat.com \
    --cc=jason@perfinion.com \
    --cc=selinux@vger.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.