Re: Windows signing restored

On Mittwoch, 26. August 2026 17:41:19 Mitteleuropäische Sommerzeit Ingo 
Klöcker wrote:
> On Mittwoch, 26. August 2026 14:00:26 Mitteleuropäische Sommerzeit Ben
> Cooksley wrote:
> > Unfortunately due to assumptions in Craft surrounding how X.509
> > certificate
> > subject names are constructed, it is not possible to restore appx signing
> > at this time as it fails due to the following error:
> > 
> > Aug 26 11:09:02 jarvis python[30701]: java.lang.IllegalArgumentException:
> > The app manifest publisher name (CN=K Desktop Environment e. V., O=K
> > Desktop Environment e. V., S=Berlin, C=DE) must match the subject name of
> > the signing certificate (SERIALNUMBER=VR
> > 31685,jurisdictionCountry=DE,BusinessCategory=Private
> > Organization,C=DE,ST=Berlin,O=K Desktop Environment e.V.,CN=K Desktop
> > Environment e.V.)
> > 
> > (Note for those looking to update our Craft configuration - the above is
> > not the subject name that Windows will accept, you need SERIALNUMBER=VR
> > 31685, 1.3.6.1.4.1.311.60.2.1.3=DE, 2.5.4.15=Private Organization, C=DE,
> > S=Berlin,  O=K Desktop Environment e.V., CN=K Desktop Environment e.V. for
> > that)
> 
> Should be easy to fix be (optionally) replacing the fine grained
> CodeSigning/ CommonName, CodeSigning/Organization, CodeSigning/State, etc.
> settings with a simple CodeSigning/DistinguishedName setting.

This will hopefully be fixed by
https://invent.kde.org/packaging/craft/-/merge_requests/379
and
https://invent.kde.org/sysadmin/craft-ci/-/merge_requests/26

Regards,
Ingo

-----BEGIN PGP SIGNATURE-----

iJEEABYKADkWIQTbjgIOMowwlCBgvyGxb1mVFkdKugUCao8nhBsUgAAAAAAEAA5t
YW51MiwyLjUrMS4xMiwyLDIACgkQsW9ZlRZHSrpDSQD7BC4SxLLh7VRr3xjH2jzu
sfZ7MEzm0iY5S3rtDd8diV4BAL+qZ/URDMyFNztuhsDFPWWZ7TtdFWiN+GO5Fs1F
QT8A
=Fjbg
-----END PGP SIGNATURE-----