Artifactory Cloud is not generating Inrelease
file or Release.gpg
file for Debian repositories. Thus not allowing repository metadata signing.
I have uploaded a private/public gpg file to Artifactory settings, yet no signing is taking place in the repos.
2
Answers
TL;DR: Try using
gpg --full-generate-key
and manually specify a 2048-bit key.I had this same issue, and just worked through it with jfrog support. I was creating key pairs using gpg, which defaults to 3072-bit keys. It appears that at least some versions of artifactory will silently fail to handle these keys. Once I used
gpg --full-generate-key
and manually specified a 2048-bit key, my key was recognized, and the InRelease and Release.gpg files were created (after recalculating the index).If you go to Application | Artifactory | Artifacts and click on the top level folder, you should see an information panel like this:
When I was using 3072-bit keys, the final line "Signing Key" did not appear. This is despite the "Verification" process in the admin panel claiming that the key and passphrase were successfully verified.
What worked for me was to define a passphrase when defining gpg keys.
You can add a passphrase when you are uploading keys through UI:
or, as in my case, with help of Terraform JFrog provider:
The gpg key was genereted with
gpg --gen-key
command.After uploading the key with a passhrase and hitting Recalculate Index the InRelease and Release.gpg were created by Artifactory.