I've tried to install the latest Intel Graphics but it fails to find i915-4.3.3-4.2.0-dkms. Is their GPG key expired or wrong or is that a problem on my side somehow?
I've tried to install the latest Intel Graphics but it fails to find i915-4.3.3-4.2.0-dkms. Is their GPG key expired or wrong or is that a problem on my side somehow?
There was a problem, but it has now been resolved.
The repository key has been corrected and the drivers can now be installed successfully.
Historic answer
Prior to approximately 2016-02-23 13:00 UTC there was a problem. Intel were aware of it, investigated it, and corrected it. The basics of the problem were that the key of the repository referred to by the installer did not match the sourced public key in the documentation. This was corrected by them updating the key on the repository.
Intel said that an internal testing key was mistakenly used in place of the production key. Although, the only person from Intel reporting on this indicated that they themselves were in the dark on the timeline for a resolution. The repository key was updated approximately 24-hours after they made that statement.
Prior to the key being corrected, it was possible to force an installation with the key mismatch, but this was not advised as it can create a security issue which is irreversible.*
To remove the warning, a user could either disable the repository using the GUI, or delete the files
/etc/apt/sources.list.d/intellinuxgraphics.*
(Until the repository key was corrected, if the Intel installer was rerun after deleting these files the problem would return.)There is no safe way of obtaining the package remotely if the keys do not match.
Detailed explanation
The Intel Graphics 1.4.0 installer installs an apt repository file in
/etc/apt/sources.list.d/intellinuxgraphics.list
which contains:When you run,
apt-get update
, each repository must be verified by a PGP key. Prior to 2016-02-23 13:00 UTC, the apt-key repository was signed with a key with ID D14BDB0DB3438B6C, hence the warning:In the intel documentation, it's indicated that the key is supposed to be installed by getting it from https://download.01.org/gfx/RPM-GPG-KEY-ilg-3 :
Here, the
-O
switch towget
pipes the file to stdout, and the-
when callingapt-key
indicates to read the file from stdinIf we replace the call to
apt-key
with agpg --dry-run
, then we can see the key ID that is being supplied from that URL, e.g.So, key 894A3A8D from the downloaded key did not match key D14BDB0DB3438B6C required to decrypt the https://download.01.org/gfx/ubuntu/15.10/main repository correctly. This has now been fixed, and the key of the repository is now 894A3A8D.
This was confirmed in Intel's own forums here, and subsequently corrected and notified there also.
Removing the repository (whether by disabling it or removing the file) would cause the warning to go away, however, that also means that the contents of the repository were inaccessible.
Running the installer again would simply reenable the repository but not fix the key problem, so the error kept returning until the repository key had been fixed. It now works correctly.
It is possible to force an installation when the keys don't match, but this is not advised as it can create a security issue which is irreversible.
Until the correct key was published, there was no safe way of obtaining the package remotely. However, the repository key has now been updated and so the error has been resolved and the drivers can be installed safely and correctly.
I manage to install Intel Drivers 1.4.0 on 15.10 64-bit
First remove previous ppa from software sources, uninstall intel-graphic-installer, then type in terminal:
wget --no-check-certificate https://download.01.org/gfx/RPM-GPG-KEY-ilg-3 -O - | sudo apt-key add -
After that download and install 1.4.0 from Intel® Graphics for Linux
An Intel engineer had just announced on intel's forum that a new build will come shortly. We just have to be patient :-)
" Update: new packages should land shortly (nothing wrong with the current packages but the final release build was done with an internal for-testing key instead of the official release key). "
Here is how I got it working: If you remove the 01 repository before running the 1.4.0 installer, you should be good to go.