Bug #19193
closed
WARNING: The following packages cannot be authenticated!
Description
Hi everyone,
I noticed that some of the foreman dependencies for ubuntu Xenial were not signed by the same key you described to import with apt-key.
So in concequence under Ubuntu Xenial I encounter the following problem when installing the package:
```vagrant@vagrant-base-xenial-amd64:~$ sudo apt-get install foreman
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
augeas-lenses binutils build-essential bundler cpp cpp-5 dpkg-dev fakeroot fonts-lato foreman-debug foreman-proxy g++ g++-5 gcc gcc-5 javascript-common libalgorithm-diff-perl libalgorithm-diff-xs-perl libalgorithm-merge-perl libasan2 libatomic1 libaugeas0 libavahi-client3
libavahi-common-data libavahi-common3 libc-dev-bin libc6-dev libcc1-0 libcilkrts5 libdpkg-perl libfakeroot libfile-fcntllock-perl libgcc-5-dev libgmp-dev libgmpxx4ldbl libgomp1 libgssrpc4 libisl15 libitm1 libjs-jquery libkadm5clnt-mit9 liblsan0 libmpc3 libmpfr4 libmpx0
libnl-3-200 libquadmath0 libruby2.3 libstdc++-5-dev libtsan0 libubsan0 libvirt0 libxen-4.6 libxenstore3.0 libyajl2 libyaml-0-2 linux-libc-dev make manpages manpages-dev patch rake rsync ruby ruby-augeas ruby-bundler ruby-bundler-ext ruby-concurrent ruby-dev ruby-did-you-mean
ruby-ffi ruby-gssapi ruby-json ruby-libvirt ruby-minitest ruby-molinillo ruby-net-http-persistent ruby-net-telnet ruby-power-assert ruby-rack ruby-rack-protection ruby-rb-inotify ruby-rkerberos ruby-rubyipmi ruby-sinatra ruby-test-unit ruby-thor ruby-tilt ruby2.3 ruby2.3-dev
rubygems-integration unzip zip zlib1g-dev
Suggested packages:
augeas-doc binutils-doc cpp-doc gcc-5-locales debian-keyring g++-multilib g++-5-multilib gcc-5-doc libstdc++6-5-dbg gcc-multilib autoconf automake libtool flex bison gdb gcc-doc gcc-5-multilib libgcc1-dbg libgomp1-dbg libitm1-dbg libatomic1-dbg libasan2-dbg liblsan0-dbg
libtsan0-dbg libubsan0-dbg libcilkrts5-dbg libmpx0-dbg libquadmath0-dbg apache2 | lighttpd | httpd augeas-tools glibc-doc gmp-doc libgmp10-doc libmpfr-dev krb5-doc krb5-user libstdc++-5-doc lvm2 make-doc ed diffutils-doc ri doc-base
The following NEW packages will be installed:
augeas-lenses binutils build-essential bundler cpp cpp-5 dpkg-dev fakeroot fonts-lato foreman foreman-debug foreman-proxy g++ g++-5 gcc gcc-5 javascript-common libalgorithm-diff-perl libalgorithm-diff-xs-perl libalgorithm-merge-perl libasan2 libatomic1 libaugeas0
libavahi-client3 libavahi-common-data libavahi-common3 libc-dev-bin libc6-dev libcc1-0 libcilkrts5 libdpkg-perl libfakeroot libfile-fcntllock-perl libgcc-5-dev libgmp-dev libgmpxx4ldbl libgomp1 libgssrpc4 libisl15 libitm1 libjs-jquery libkadm5clnt-mit9 liblsan0 libmpc3 libmpfr4
libmpx0 libnl-3-200 libquadmath0 libruby2.3 libstdc++-5-dev libtsan0 libubsan0 libvirt0 libxen-4.6 libxenstore3.0 libyajl2 libyaml-0-2 linux-libc-dev make manpages manpages-dev patch rake rsync ruby ruby-augeas ruby-bundler ruby-bundler-ext ruby-concurrent ruby-dev
ruby-did-you-mean ruby-ffi ruby-gssapi ruby-json ruby-libvirt ruby-minitest ruby-molinillo ruby-net-http-persistent ruby-net-telnet ruby-power-assert ruby-rack ruby-rack-protection ruby-rb-inotify ruby-rkerberos ruby-rubyipmi ruby-sinatra ruby-test-unit ruby-thor ruby-tilt
ruby2.3 ruby2.3-dev rubygems-integration unzip zip zlib1g-dev
0 upgraded, 95 newly installed, 0 to remove and 0 not upgraded.
Need to get 92.4 MB of archives.
After this operation, 362 MB of additional disk space will be used.
Do you want to continue? [Y/n]
WARNING: The following packages cannot be authenticated!
ruby-bundler-ext ruby-libvirt ruby-rkerberos ruby-rubyipmi foreman foreman-debug foreman-proxy
Install these packages without verification? [y/N]
```
I was not able to fix this issue, or find any other SO/ redmind topic about it. could someone have a look at the server configuration for these ruby-bundler-ext ... dependencies.
```
vagrant@vagrant-base-xenial-amd64:~$ apt-cache policy ruby-bundler-ext
ruby-bundler-ext:
Installed: (none)
Candidate: 0.4.1-1
Version table:
0.4.1-1 500
500 http://deb.theforeman.org xenial/stable amd64 Packages
```
Best Regards
--
Eric
Updated by Dominic Cleal about 7 years ago
Can you show exactly which key you did import? (apt-key list output would be helpful too)
Updated by Dominic Cleal about 7 years ago
- Status changed from New to Need more information
Updated by Eric Keller about 7 years ago
- Status changed from Need more information to Feedback
`
vagrant@vagrant-base-xenial-amd64:~$ apt-key list
/etc/apt/trusted.gpg
--------------------
pub 1024D/437D05B5 2004-09-12
uid Ubuntu Archive Automatic Signing Key <ftpmaster@ubuntu.com>
sub 2048g/79164387 2004-09-12
pub 4096R/C0B21F32 2012-05-11
uid Ubuntu Archive Automatic Signing Key (2012) <ftpmaster@ubuntu.com>
pub 4096R/EFE21092 2012-05-11
uid Ubuntu CD Image Automatic Signing Key (2012) <cdimage@ubuntu.com>
pub 1024D/FBB75451 2004-12-30
uid Ubuntu CD Image Automatic Signing Key <cdimage@ubuntu.com>
pub 4096R/563278F6 2016-04-08 [expires: 2018-04-08]
uid Foreman Automatic Signing Key (2016) <packages@theforeman.org>
sub 4096R/6F1B04B4 2016-04-08 [expires: 2018-04-08]
pub 4096R/1AA043B8 2014-07-01 [expired: 2016-06-30]
uid Foreman Automatic Signing Key (2014) <packages@theforeman.org>
`
I followed the instructions from your installation site:
`
wget q http://deb.theforeman.org/pubkey.gpg -O | sudo apt-key add -
`
Updated by Dominic Cleal about 7 years ago
Have you run apt-get update since importing the key? The archive seems to be signed correctly as far as I can tell.
The only way I can reproduce your error is to have added the archive source to apt, run apt-get update (which logs an error that it can't verify the key) and then to try installing the packages. If you import the key after the apt-get update then apt will still warn about them being unverified until the archive cache is updated.
Updated by Eric Keller about 7 years ago
Yep I did some apt-get update before installing...
This is strange I tried to reproduce it from a docker container and there everything seems to be ok
```
cat << EOF > Dockerfile
FROM ubuntu:xenial
MAINTAINER "Eric Keller"
RUN apt-get update && apt-get install y wget | apt-key add -
RUN echo "deb http://deb.theforeman.org/ xenial stable" > /etc/apt/sources.list.d/foreman.list
RUN wget -q http://deb.theforeman.org/pubkey.gpg -O
RUN apt-get update && apt-get install -y foreman
EOF
```
```
docker build -t xenial-forman .
```
Results in a good installation, seems there are some problem with my vagrant box!
I think you can close this ticket I will have a look on my setup...
Cheers
Updated by Dominic Cleal about 7 years ago
- Status changed from Feedback to Rejected
Thanks for confirming.