InRelease is not signed

Hi there,

I configured an Apt hosted repo but unabled to use it because of an unsigned InRelease.
What I did :

  • I configured a signing key and it passphrase in the repo configuration
  • I added the public part in my linux target and defined the new repo
  • Did an ‘apt update’ … but encountered this issue

root@MYSERVER:~# apt update
Ign:1 xxx://my.company.com/nexus/repository/debian-stretch-proxy stretch InRelease
Atteint:2 xxx://my.company.com/nexus/repository/debian-stretch-proxy stretch-updates InRelease
Atteint:3 xxx://my.company.com/nexus/repository/debian-stretch-security-proxy stretch/updates InRelease
Atteint:5 xxx://my.company.com/nexus/repository/debian-stretch-proxy stretch Release
Réception de:4 xxx://my.company.com/nexus/repository/myhosted-deb debian InRelease [1 875 B]
Err:4 xxx://my.company.com/nexus/repository/myhosted-deb debian InRelease
Les signatures suivantes n’ont pas pu être vérifiées car la clé publique n’est pas disponible : NO_PUBKEY AB6C…
Lecture des listes de paquets… Fait
W: Erreur de GPG : xxx://my.company.com/nexus/repository/myhosted-deb debian InRelease : Les signatures suivante
E: The repository ‘xxx://my.company.com/nexus/repository/myhosted-deb debian InRelease’ is not signed.*
N: Updating from such a repository can’t be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
root@MYSERVER:~#

Is the InRelease file signed automatically when a signing key is configured ?

Regards

I’m replying to myself : upload a new .deb in the repository renew the InRelease file and sign it.
Now all is working fine !

1 Like