Re: TomEE package verification not working

------3SY12HQESPKI70J837B2NNSBXULOOE
Content-Type: text/plain;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable

The link is correct=2E The key in question is contained in the file=2E

pub   rsa4096 2024-03-22 [SC]
      85FBBE98D6C37CDA8A7D8FF9F9FF83A48D339D37
uid           [ultimate] Markus Jung (CODE SIGNING KEY) <jungm@apache=2Eor=
g>
sig 3        F9FF83A48D339D37 2024-03-22  [self-signature]
sub   rsa4096 2024-03-22 [E]
sig          F9FF83A48D339D37 2024-03-22  [self-signature]

The only change ist, that Markus did the Release for 10=2E1=2E1=2E

Gru=C3=9F=20
Richard=20

Am 11=2E September 2025 18:27:31 MESZ schrieb COURTAULT Francois <francois=
=2Ecourtault@thalesgroup=2Ecom=2EINVALID>:
>THALES GROUP LIMITED DISTRIBUTION to email recipients
>
>Hello everyone,
>
>In our pipeline for building TomEE Docker base images, we do this:
>+ gpg --batch --verify apache-tomee-10=2E1=2E1-plus=2Etar=2Egz=2Easc apac=
he-tomee-10=2E1=2E1-plus=2Etar=2Egz
>gpg: Signature made Sat Aug 16 12:18:25 2025 UTC
>gpg: using RSA key 85FBBE98D6C37CDA8A7D8FF9F9FF83A48D339D37
>gpg: Can't check signature: No public key
>
>It was working with TomEE 10=2E1=2E0 but not anymore with TomEE 10=2E1=2E=
1=2E
>The keys used are located at https://downloads=2Eapache=2Eorg/tomee/KEYS
>Is this location still valid for TomEE keys ?
>
>What has changed between 10=2E1=2E0 and 10=2E1=2E1 ?
>How to fix this issue ? any idea ?
>
>Best Regards=2E
>
>
>

------3SY12HQESPKI70J837B2NNSBXULOOE--