Invalid signatures when running apt-get update











up vote
5
down vote

favorite
1












I am trying to run an update, I get a lot of "Hit"'s and "Ign"'s but in the end I get these errors, does anybody know what they mean and how I can fix them?



W: GPG error: http://speglar.simnet.is olivia Release: The following signatures were invalid: BADSIG 3EE67F3D0FF405B2 Clement Lefebvre (Linux Mint Package Repository v1) <root@linuxmint.com>
W: GPG error: http://speglar.simnet.is raring Release: The following signatures were invalid: BADSIG 40976EAF437D05B5 Ubuntu Archive Automatic Signing Key <ftpmaster@ubuntu.com>
W: GPG error: http://archive.canonical.com raring Release: The following signatures were invalid: BADSIG 40976EAF437D05B5 Ubuntu Archive Automatic Signing Key <ftpmaster@ubuntu.com>
W: GPG error: http://ppa.launchpad.net raring Release: The following signatures were invalid: BADSIG 5A9A06AEF9CB8DB0 Launchpad PPA for Ubuntu Wine Team









share|improve this question
























  • Each repository (more or less) has its own key to sign packages. Did you run apt-key or a corresponding GUI to install extra keys for these repositories?
    – Gilles
    Oct 24 '13 at 23:50










  • I'm not sure how to do that, can I run gedit apt-key and add these keys into the file? What are these keys anyway?
    – Noosgam
    Oct 25 '13 at 0:00










  • You add a key by running the apt-key command (or with an equivalent GUI, for example the interface to add a PPA in the default software manager on Ubuntu does that automatically), you can't edit a file directly. Expand “Technical details about this PPA” then click on “What is this?” after “Signing key” in a PPA page for more explanations. The purpose of the signing key is to verify that the package files that you receive are genuine.
    – Gilles
    Oct 25 '13 at 0:05

















up vote
5
down vote

favorite
1












I am trying to run an update, I get a lot of "Hit"'s and "Ign"'s but in the end I get these errors, does anybody know what they mean and how I can fix them?



W: GPG error: http://speglar.simnet.is olivia Release: The following signatures were invalid: BADSIG 3EE67F3D0FF405B2 Clement Lefebvre (Linux Mint Package Repository v1) <root@linuxmint.com>
W: GPG error: http://speglar.simnet.is raring Release: The following signatures were invalid: BADSIG 40976EAF437D05B5 Ubuntu Archive Automatic Signing Key <ftpmaster@ubuntu.com>
W: GPG error: http://archive.canonical.com raring Release: The following signatures were invalid: BADSIG 40976EAF437D05B5 Ubuntu Archive Automatic Signing Key <ftpmaster@ubuntu.com>
W: GPG error: http://ppa.launchpad.net raring Release: The following signatures were invalid: BADSIG 5A9A06AEF9CB8DB0 Launchpad PPA for Ubuntu Wine Team









share|improve this question
























  • Each repository (more or less) has its own key to sign packages. Did you run apt-key or a corresponding GUI to install extra keys for these repositories?
    – Gilles
    Oct 24 '13 at 23:50










  • I'm not sure how to do that, can I run gedit apt-key and add these keys into the file? What are these keys anyway?
    – Noosgam
    Oct 25 '13 at 0:00










  • You add a key by running the apt-key command (or with an equivalent GUI, for example the interface to add a PPA in the default software manager on Ubuntu does that automatically), you can't edit a file directly. Expand “Technical details about this PPA” then click on “What is this?” after “Signing key” in a PPA page for more explanations. The purpose of the signing key is to verify that the package files that you receive are genuine.
    – Gilles
    Oct 25 '13 at 0:05















up vote
5
down vote

favorite
1









up vote
5
down vote

favorite
1






1





I am trying to run an update, I get a lot of "Hit"'s and "Ign"'s but in the end I get these errors, does anybody know what they mean and how I can fix them?



W: GPG error: http://speglar.simnet.is olivia Release: The following signatures were invalid: BADSIG 3EE67F3D0FF405B2 Clement Lefebvre (Linux Mint Package Repository v1) <root@linuxmint.com>
W: GPG error: http://speglar.simnet.is raring Release: The following signatures were invalid: BADSIG 40976EAF437D05B5 Ubuntu Archive Automatic Signing Key <ftpmaster@ubuntu.com>
W: GPG error: http://archive.canonical.com raring Release: The following signatures were invalid: BADSIG 40976EAF437D05B5 Ubuntu Archive Automatic Signing Key <ftpmaster@ubuntu.com>
W: GPG error: http://ppa.launchpad.net raring Release: The following signatures were invalid: BADSIG 5A9A06AEF9CB8DB0 Launchpad PPA for Ubuntu Wine Team









share|improve this question















I am trying to run an update, I get a lot of "Hit"'s and "Ign"'s but in the end I get these errors, does anybody know what they mean and how I can fix them?



W: GPG error: http://speglar.simnet.is olivia Release: The following signatures were invalid: BADSIG 3EE67F3D0FF405B2 Clement Lefebvre (Linux Mint Package Repository v1) <root@linuxmint.com>
W: GPG error: http://speglar.simnet.is raring Release: The following signatures were invalid: BADSIG 40976EAF437D05B5 Ubuntu Archive Automatic Signing Key <ftpmaster@ubuntu.com>
W: GPG error: http://archive.canonical.com raring Release: The following signatures were invalid: BADSIG 40976EAF437D05B5 Ubuntu Archive Automatic Signing Key <ftpmaster@ubuntu.com>
W: GPG error: http://ppa.launchpad.net raring Release: The following signatures were invalid: BADSIG 5A9A06AEF9CB8DB0 Launchpad PPA for Ubuntu Wine Team






ubuntu apt gpg






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 24 at 20:05









Rui F Ribeiro

38.3k1475126




38.3k1475126










asked Oct 24 '13 at 23:42









Noosgam

38115




38115












  • Each repository (more or less) has its own key to sign packages. Did you run apt-key or a corresponding GUI to install extra keys for these repositories?
    – Gilles
    Oct 24 '13 at 23:50










  • I'm not sure how to do that, can I run gedit apt-key and add these keys into the file? What are these keys anyway?
    – Noosgam
    Oct 25 '13 at 0:00










  • You add a key by running the apt-key command (or with an equivalent GUI, for example the interface to add a PPA in the default software manager on Ubuntu does that automatically), you can't edit a file directly. Expand “Technical details about this PPA” then click on “What is this?” after “Signing key” in a PPA page for more explanations. The purpose of the signing key is to verify that the package files that you receive are genuine.
    – Gilles
    Oct 25 '13 at 0:05




















  • Each repository (more or less) has its own key to sign packages. Did you run apt-key or a corresponding GUI to install extra keys for these repositories?
    – Gilles
    Oct 24 '13 at 23:50










  • I'm not sure how to do that, can I run gedit apt-key and add these keys into the file? What are these keys anyway?
    – Noosgam
    Oct 25 '13 at 0:00










  • You add a key by running the apt-key command (or with an equivalent GUI, for example the interface to add a PPA in the default software manager on Ubuntu does that automatically), you can't edit a file directly. Expand “Technical details about this PPA” then click on “What is this?” after “Signing key” in a PPA page for more explanations. The purpose of the signing key is to verify that the package files that you receive are genuine.
    – Gilles
    Oct 25 '13 at 0:05


















Each repository (more or less) has its own key to sign packages. Did you run apt-key or a corresponding GUI to install extra keys for these repositories?
– Gilles
Oct 24 '13 at 23:50




Each repository (more or less) has its own key to sign packages. Did you run apt-key or a corresponding GUI to install extra keys for these repositories?
– Gilles
Oct 24 '13 at 23:50












I'm not sure how to do that, can I run gedit apt-key and add these keys into the file? What are these keys anyway?
– Noosgam
Oct 25 '13 at 0:00




I'm not sure how to do that, can I run gedit apt-key and add these keys into the file? What are these keys anyway?
– Noosgam
Oct 25 '13 at 0:00












You add a key by running the apt-key command (or with an equivalent GUI, for example the interface to add a PPA in the default software manager on Ubuntu does that automatically), you can't edit a file directly. Expand “Technical details about this PPA” then click on “What is this?” after “Signing key” in a PPA page for more explanations. The purpose of the signing key is to verify that the package files that you receive are genuine.
– Gilles
Oct 25 '13 at 0:05






You add a key by running the apt-key command (or with an equivalent GUI, for example the interface to add a PPA in the default software manager on Ubuntu does that automatically), you can't edit a file directly. Expand “Technical details about this PPA” then click on “What is this?” after “Signing key” in a PPA page for more explanations. The purpose of the signing key is to verify that the package files that you receive are genuine.
– Gilles
Oct 25 '13 at 0:05












2 Answers
2






active

oldest

votes

















up vote
7
down vote



accepted










As Gilles explained, most Linux repositories are signed with GPG encryption keys. apt then uses these keys to ensure the authenticity of the repositories. In order to safely use a repository, you need to add it's keys to the list that apt considers trusted.



Each necessary key needs to be downloaded from a key server which is done with this command (I am using keyserver.ubuntu.com but you can use others):



apt-key adv --recv-keys --keyserver keyserver.ubuntu.com KEY_NAME


From man apt-key:



   adv
Pass advanced options to gpg. With adv --recv-key you can download
the public key.


In your case, apt is complaining about keys 3EE67F3D0FF405B2,40976EAF437D05B5,40976EAF437D05B5 and 5A9A06AEF9CB8DB0, you can get all three of them by running:



sudo apt-key adv --recv-keys --keyserver keyserver.ubuntu.com 3EE67F3D0FF405B2 40976EAF437D05B5 40976EAF437D05B5 5A9A06AEF9CB8DB0


If all goes well you should see various lines of output including:



gpg: Total number processed: 4
gpg: imported: 4 (RSA: 1)
gpg: unchanged: 0
gpg: new signatures: 4





share|improve this answer




























    up vote
    1
    down vote













    Alternate possibility, if your apt-get/aptitude has been found in an unusual state recently, is that its internal lists are damaged and incompatible with the true keys. Cleaning the cache and restarting on fresh basis can help:



       sudo rm -r /var/lib/apt/lists
    sudo mkdir -p /var/lib/apt/lists/partial
    sudo aptitude update


    (op: http://ubuntuforums.org/showthread.php?t=802156&p=9697234#post9697234 )






    share|improve this answer





















      Your Answer








      StackExchange.ready(function() {
      var channelOptions = {
      tags: "".split(" "),
      id: "106"
      };
      initTagRenderer("".split(" "), "".split(" "), channelOptions);

      StackExchange.using("externalEditor", function() {
      // Have to fire editor after snippets, if snippets enabled
      if (StackExchange.settings.snippets.snippetsEnabled) {
      StackExchange.using("snippets", function() {
      createEditor();
      });
      }
      else {
      createEditor();
      }
      });

      function createEditor() {
      StackExchange.prepareEditor({
      heartbeatType: 'answer',
      convertImagesToLinks: false,
      noModals: true,
      showLowRepImageUploadWarning: true,
      reputationToPostImages: null,
      bindNavPrevention: true,
      postfix: "",
      imageUploader: {
      brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
      contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
      allowUrls: true
      },
      onDemand: true,
      discardSelector: ".discard-answer"
      ,immediatelyShowMarkdownHelp:true
      });


      }
      });














       

      draft saved


      draft discarded


















      StackExchange.ready(
      function () {
      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f97493%2finvalid-signatures-when-running-apt-get-update%23new-answer', 'question_page');
      }
      );

      Post as a guest















      Required, but never shown

























      2 Answers
      2






      active

      oldest

      votes








      2 Answers
      2






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes








      up vote
      7
      down vote



      accepted










      As Gilles explained, most Linux repositories are signed with GPG encryption keys. apt then uses these keys to ensure the authenticity of the repositories. In order to safely use a repository, you need to add it's keys to the list that apt considers trusted.



      Each necessary key needs to be downloaded from a key server which is done with this command (I am using keyserver.ubuntu.com but you can use others):



      apt-key adv --recv-keys --keyserver keyserver.ubuntu.com KEY_NAME


      From man apt-key:



         adv
      Pass advanced options to gpg. With adv --recv-key you can download
      the public key.


      In your case, apt is complaining about keys 3EE67F3D0FF405B2,40976EAF437D05B5,40976EAF437D05B5 and 5A9A06AEF9CB8DB0, you can get all three of them by running:



      sudo apt-key adv --recv-keys --keyserver keyserver.ubuntu.com 3EE67F3D0FF405B2 40976EAF437D05B5 40976EAF437D05B5 5A9A06AEF9CB8DB0


      If all goes well you should see various lines of output including:



      gpg: Total number processed: 4
      gpg: imported: 4 (RSA: 1)
      gpg: unchanged: 0
      gpg: new signatures: 4





      share|improve this answer

























        up vote
        7
        down vote



        accepted










        As Gilles explained, most Linux repositories are signed with GPG encryption keys. apt then uses these keys to ensure the authenticity of the repositories. In order to safely use a repository, you need to add it's keys to the list that apt considers trusted.



        Each necessary key needs to be downloaded from a key server which is done with this command (I am using keyserver.ubuntu.com but you can use others):



        apt-key adv --recv-keys --keyserver keyserver.ubuntu.com KEY_NAME


        From man apt-key:



           adv
        Pass advanced options to gpg. With adv --recv-key you can download
        the public key.


        In your case, apt is complaining about keys 3EE67F3D0FF405B2,40976EAF437D05B5,40976EAF437D05B5 and 5A9A06AEF9CB8DB0, you can get all three of them by running:



        sudo apt-key adv --recv-keys --keyserver keyserver.ubuntu.com 3EE67F3D0FF405B2 40976EAF437D05B5 40976EAF437D05B5 5A9A06AEF9CB8DB0


        If all goes well you should see various lines of output including:



        gpg: Total number processed: 4
        gpg: imported: 4 (RSA: 1)
        gpg: unchanged: 0
        gpg: new signatures: 4





        share|improve this answer























          up vote
          7
          down vote



          accepted







          up vote
          7
          down vote



          accepted






          As Gilles explained, most Linux repositories are signed with GPG encryption keys. apt then uses these keys to ensure the authenticity of the repositories. In order to safely use a repository, you need to add it's keys to the list that apt considers trusted.



          Each necessary key needs to be downloaded from a key server which is done with this command (I am using keyserver.ubuntu.com but you can use others):



          apt-key adv --recv-keys --keyserver keyserver.ubuntu.com KEY_NAME


          From man apt-key:



             adv
          Pass advanced options to gpg. With adv --recv-key you can download
          the public key.


          In your case, apt is complaining about keys 3EE67F3D0FF405B2,40976EAF437D05B5,40976EAF437D05B5 and 5A9A06AEF9CB8DB0, you can get all three of them by running:



          sudo apt-key adv --recv-keys --keyserver keyserver.ubuntu.com 3EE67F3D0FF405B2 40976EAF437D05B5 40976EAF437D05B5 5A9A06AEF9CB8DB0


          If all goes well you should see various lines of output including:



          gpg: Total number processed: 4
          gpg: imported: 4 (RSA: 1)
          gpg: unchanged: 0
          gpg: new signatures: 4





          share|improve this answer












          As Gilles explained, most Linux repositories are signed with GPG encryption keys. apt then uses these keys to ensure the authenticity of the repositories. In order to safely use a repository, you need to add it's keys to the list that apt considers trusted.



          Each necessary key needs to be downloaded from a key server which is done with this command (I am using keyserver.ubuntu.com but you can use others):



          apt-key adv --recv-keys --keyserver keyserver.ubuntu.com KEY_NAME


          From man apt-key:



             adv
          Pass advanced options to gpg. With adv --recv-key you can download
          the public key.


          In your case, apt is complaining about keys 3EE67F3D0FF405B2,40976EAF437D05B5,40976EAF437D05B5 and 5A9A06AEF9CB8DB0, you can get all three of them by running:



          sudo apt-key adv --recv-keys --keyserver keyserver.ubuntu.com 3EE67F3D0FF405B2 40976EAF437D05B5 40976EAF437D05B5 5A9A06AEF9CB8DB0


          If all goes well you should see various lines of output including:



          gpg: Total number processed: 4
          gpg: imported: 4 (RSA: 1)
          gpg: unchanged: 0
          gpg: new signatures: 4






          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Oct 25 '13 at 1:05









          terdon

          126k31243419




          126k31243419
























              up vote
              1
              down vote













              Alternate possibility, if your apt-get/aptitude has been found in an unusual state recently, is that its internal lists are damaged and incompatible with the true keys. Cleaning the cache and restarting on fresh basis can help:



                 sudo rm -r /var/lib/apt/lists
              sudo mkdir -p /var/lib/apt/lists/partial
              sudo aptitude update


              (op: http://ubuntuforums.org/showthread.php?t=802156&p=9697234#post9697234 )






              share|improve this answer

























                up vote
                1
                down vote













                Alternate possibility, if your apt-get/aptitude has been found in an unusual state recently, is that its internal lists are damaged and incompatible with the true keys. Cleaning the cache and restarting on fresh basis can help:



                   sudo rm -r /var/lib/apt/lists
                sudo mkdir -p /var/lib/apt/lists/partial
                sudo aptitude update


                (op: http://ubuntuforums.org/showthread.php?t=802156&p=9697234#post9697234 )






                share|improve this answer























                  up vote
                  1
                  down vote










                  up vote
                  1
                  down vote









                  Alternate possibility, if your apt-get/aptitude has been found in an unusual state recently, is that its internal lists are damaged and incompatible with the true keys. Cleaning the cache and restarting on fresh basis can help:



                     sudo rm -r /var/lib/apt/lists
                  sudo mkdir -p /var/lib/apt/lists/partial
                  sudo aptitude update


                  (op: http://ubuntuforums.org/showthread.php?t=802156&p=9697234#post9697234 )






                  share|improve this answer












                  Alternate possibility, if your apt-get/aptitude has been found in an unusual state recently, is that its internal lists are damaged and incompatible with the true keys. Cleaning the cache and restarting on fresh basis can help:



                     sudo rm -r /var/lib/apt/lists
                  sudo mkdir -p /var/lib/apt/lists/partial
                  sudo aptitude update


                  (op: http://ubuntuforums.org/showthread.php?t=802156&p=9697234#post9697234 )







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Jan 22 '15 at 9:04









                  PypeBros

                  1314




                  1314






























                       

                      draft saved


                      draft discarded



















































                       


                      draft saved


                      draft discarded














                      StackExchange.ready(
                      function () {
                      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f97493%2finvalid-signatures-when-running-apt-get-update%23new-answer', 'question_page');
                      }
                      );

                      Post as a guest















                      Required, but never shown





















































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown

































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown







                      Popular posts from this blog

                      サソリ

                      広島県道265号伴広島線

                      Accessing regular linux commands in Huawei's Dopra Linux