New packager key of tpkessler

Add a new packager key

Details

• Username: @tpkessler
• PGP key ID: 04CF0CD6F6EE93AE1896F58407D06351CA5B31BE
• Sponsors: @svenstaro @archange
• Application: https://lists.archlinux.org/archives/list/aur-general@lists.archlinux.org/thread/3HLMZQBHIFASXSCGHCNS3PCP3BMKMMUU/
• Results: https://lists.archlinux.org/archives/list/aur-general@lists.archlinux.org/message/CFGTPPLUE4RIRHXDUHWJF4SBOEEWQMJ6/

details.txt.asc

Checks

Owner of new key

• The workflow for adding a new packager key has been followed
• The key pair contains one user ID with a valid <username>@archlinux.org email address used for signing
• The key pair has been validated according to the best practices
• The data in the Details section is attached to this issue as a clearsigned document
• The public key has been uploaded to the pgp.mit.edu and keyserver.ubuntu.com
• A merge request to add the new public key has been created

Main key holders

• The public key has been signed by all main key holders
  • @anthraxx
  • @bluewind
  • @demize
  • @dvzrv

Developers of the archlinux-keyring project

• The data in the Details section is correct and signed with a valid and trusted packager key, which is already part of archlinux-keyring

added new packager key label

assigned to @demize, @eworm, @pierre, @bluewind, @diabonas, @anthraxx, and @dvzrv

mentioned in issue infrastructure#485 (closed)

marked the checklist item The data in the Details section is correct and signed with a as completed

marked the checklist item The data in the Details section is correct and signed with a as incomplete

@tpkessler your new key id 04CF0CD6F6EE93AE1896F58407D06351CA5B31BE seems to (obviously) be different from the personal one used during the application (661C 8706 C3A2 878A C167 8BE1 AF5F F1C9 3CF0 9D12).

Could you please sign your new archlinux key with the old one, or just dump a clear-signed text message somewhere that links together your old and new key? Thanks!

I've crossed-signed the keys and resubmitted them:

Application key

Archlinux key

marked the checklist item The key pair contains one user ID with a valid <username>@archlinux.org email address as completed

marked the checklist item The key pair has been validated according to the [best as completed

marked the checklist item The data in the Details section is attached to this issue as as completed

marked the checklist item The public key has been uploaded to the pgp.mit.edu and keyserver.ubuntu.com as completed

marked the checklist item The [workflow for adding a new packager as completed

Verification mail sent

Signature added in !204 (merged)

marked the checklist item The data in the Details section is correct and signed with a as completed

mentioned in merge request !203 (closed)

marked the checklist item A merge request to add the new public key has been created as completed

mentioned in merge request !204 (merged)

Verification email sent.

Key signed and signature pushed to the MR.

marked the checklist item @demize as completed

unassigned @demize

marked the checklist item @dvzrv as completed

unassigned @dvzrv

verification mail sent

signature part of !204 (merged)

marked the checklist item @bluewind as completed

unassigned @bluewind

Available in archlinux-keyring-20221219-1 with three signatures and full trust, which is in testing now.

changed the description

unassigned @pierre and @eworm

@anthraxx this one still misses a signature from you

verification sent

@anthraxx Did you receive my reply from 2023-10-19?

@artafinde's signature received and published to key server.

Can you please create a MR towards this repository for that signature? Thanks!

See !273 (closed) It seems like I misunderstood GPG again. I thought with !258 (diffs) @artafinde's signature was part of the keyring. But ./keyringctl inspect 04CF0CD6F6EE93AE1896F58407D06351CA5B31BE only shows three signatures

    Fingerprint: 04CF0CD6F6EE93AE1896F58407D06351CA5B31BE tpkessler ✓ full
Public-key algo: EdDSA
Public-key size: 256 bits
  Creation time: 2022-12-07 14:40:02 UTC
Expiration time: 2025-12-31 11:00:01 UTC (creation time + P1119DT73199S)
      Key flags: certification, signing

         Subkey: 5B685E079D6BCB9A97066F5E9A8B7B021810A328
Public-key algo: ECDH
Public-key size: 256 bits
  Creation time: 2022-12-07 14:40:02 UTC
Expiration time: 2025-12-31 11:00:00 UTC (creation time + P1119DT73198S)
      Key flags: transport encryption, data-at-rest encryption

         UserID: Torsten Keßler <tpkessler@archlinux.org>
  Certification: Creation time: 2022-12-18 13:50:03 UTC
                 Alleged certifier: 91FFE0700E80619CEB73235CA88E23E377514E00 florian (main) ✓ full
                 Hash algorithm: SHA512
  Certification: Creation time: 2022-12-16 20:30:43 UTC
                 Alleged certifier: 69E6471E3AE065297529832E6BA0F5A2037F4F41 demize (main) ✓ full
                 Hash algorithm: SHA512
  Certification: Creation time: 2022-12-16 13:25:10 UTC
                 Alleged certifier: 2AC0A42EFB0B5CBC7A0402ED4DC95B6D7BE9892E dvzrv (main) ✓ full
                 Hash algorithm: SHA512
           Note: Certifications have NOT been verified!

You might need to update your master branch. Seems fine to me.

Indeed. After syncing my fork again, keyringctl inspect lists @artafinde's signature. A keyringctl import doesn't modify any of the files, so everything is up-to-date.

@anthraxx Friendly ping.

changed the description

unassigned @diabonas

All I wish for Christmas is 5/5 signatures for my key. @anthraxx, could you please have a look at it?

Merry xmas, ho ho ho

marked the checklist item @anthraxx as completed

marked the checklist item The public key has been signed by all main key holders as completed

added resolutioncompleted label

closed