Uploaded image for project: 'Artifactory Binary Repository'
  1. Artifactory Binary Repository
  2. RTFACT-25704

After uploading GPG Signing key and reindexing Debian repository, metadata is still not signed

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open
    • Resolution: Unresolved
    • Affects Version/s: 7.17.11
    • Fix Version/s: None
    • Component/s: Debian
    • Labels:
      None
    • Severity:
      Medium

      Description

      After adding a GPG signing key as described [here](https://www.jfrog.com/confluence/display/JFROG/Artifactory+Security#ArtifactorySecurity-SigningKeysManagement) and reindexing a debian repository, there is still no Release.gpg or InRelease file. Nor is there any indication of why the repository isn't signed.

       

      After finding https://stackoverflow.com/search?q=%5Bartifactory%5D+InRelease I tried using a different GPG key that is 2048 bits instead of 3072 bits, but I still have the issue.  Verifying the GPG key says it is valid, and it shows up under /api/security/keypair/default-gpg-key

        Attachments

          Activity

              People

              Assignee:
              Unassigned
              Reporter:
              lthayne Thayne
              Votes:
              5 Vote for this issue
              Watchers:
              9 Start watching this issue

                Dates

                Created:
                Updated:

                  Sync Status

                  Connection: RTFACT Sync
                  RTMID-25704 -
                  SYNCHRONIZED
                  • Last Sync Date: