Sorry, you need to enable JavaScript to visit this website.

Invalid signature for

26 posts / 0 new
Martin van Es's picture
Martin van Es

Feb 17, 2016 - 05:58am

  • I'm having the same problem. Ubuntu Mate 15.10. Is there a fix for this?

    Feb 17, 2016 - 10:15am
  • Same here. The signature on the directory is 894A3A8D​ but is expected to have D14BDB0DB3438B6C
    Feb 17, 2016 - 05:05pm
  • Hi- I've pinged the release team about this, hopefully the public keys will be up soon.

    Feb 18, 2016 - 11:45am
  • I'm told the key should be here:
    And it does seem to be mentioned in the release notes here:

    Is there somewhere that mentions the old keys but not the new one?

    Feb 18, 2016 - 12:38pm
  • I have imported that key as described in the release notes. It is not the correct key.

    Feb 18, 2016 - 12:55pm
  • Same. It will not update correctly without that key. I did use the Ubuntu signature in the release notes:

    wget --no-check-certificate -O - | \
    sudo apt-key add -

    And though it appeared to work as intended at that step, it went on to give me this:


    W: GPG error: wily InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D14BDB0DB3438B6C


    I assume everyone else is getting the same.

    Feb 18, 2016 - 04:57pm
  • See here for my more detailed explanation as to why it's not working:



    Incidentally, using --no-check-certificates is unnecessary and creates a potential security risk.


    Still waiting for an updated key!

    Feb 18, 2016 - 05:26pm
  • RPM-GPG-KEY-ilg-3 is simply not the right key, someone at intel should read up on pub/priv key crypto!


    $ gpg --with-fingerprint RPM-GPG-KEY-ilg-3           
    pub  2048R/894A3A8D 2015-11-18 ANUSHASRIVATSA <>
         Key fingerprint = 6C82 391D C413 65FB 56EC  3CE4 A496 EB03 894A 3A8D
    sub  2048R/DA056CC3 2015-11-18

    Feb 19, 2016 - 12:50am
  • Same issue here. I've imported all the keys but none of them matches the required one.

    Feb 19, 2016 - 06:38am
  • Still no solution for this?

    Feb 19, 2016 - 07:01pm