Kibana: artifacts.elastic.co deb repo is not properly signed

[gerardorochin]

Trying install Kibana 5.0.0-beta1 from debian oficial packages following the official steps https://www.elastic.co/guide/en/elasticsearch/reference/5.x/deb.html#deb-repo and response this message:

Reading state information...
The following NEW packages will be installed:
  kibana
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 40.5 MB of archives.
After this operation, 147 MB of additional disk space will be used.
WARNING: The following packages cannot be authenticated!
  kibana

Kibana: 5.0.0-beta1

More info about for PR for docker official image docker-library/kibana/pull/55

[jbudz]

/cc @rjernst, any ideas?

Ign:7 https://artifacts.elastic.co/packages/5.x-prerelease/apt stable Release.gpg
Get:8 https://artifacts.elastic.co/packages/5.x-prerelease/apt stable/main amd64 Packages [1,452 B]
Fetched 97.5 kB in 0s (117 kB/s)
Reading package lists... Done
W: The repository 'https://artifacts.elastic.co/packages/5.x-prerelease/apt stable Release' is not signed.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.

[rjernst]

Thanks for the report! The problem is the Release signature file is named incorrectly. Instead of Release.gpg, it is called Release.asc. I'll try to get this fixed next week.

[gerardorochin]

Thanks, waiting for fix.

[rjernst]

This is fixed in our release process, so the repo should be signed once we release our next preview release.