apt, disable signature expiry checks

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP












1















I am trying to use apt with a repo that hasn't been touched in a long time. Unfortunately the gpg key for said repo is expired (I tried updating it from a variety of keyservers, no luck)



I would rather not disable signature checking completely, is there any way to tell apt to verify signatures against expired keys?










share|improve this question


























    1















    I am trying to use apt with a repo that hasn't been touched in a long time. Unfortunately the gpg key for said repo is expired (I tried updating it from a variety of keyservers, no luck)



    I would rather not disable signature checking completely, is there any way to tell apt to verify signatures against expired keys?










    share|improve this question
























      1












      1








      1


      1






      I am trying to use apt with a repo that hasn't been touched in a long time. Unfortunately the gpg key for said repo is expired (I tried updating it from a variety of keyservers, no luck)



      I would rather not disable signature checking completely, is there any way to tell apt to verify signatures against expired keys?










      share|improve this question














      I am trying to use apt with a repo that hasn't been touched in a long time. Unfortunately the gpg key for said repo is expired (I tried updating it from a variety of keyservers, no luck)



      I would rather not disable signature checking completely, is there any way to tell apt to verify signatures against expired keys?







      apt






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Feb 21 at 20:24









      plugwashplugwash

      1,876619




      1,876619




















          1 Answer
          1






          active

          oldest

          votes


















          2














          I have come to the conclusion that there is no way to disable this check in apt, the code that implements the check is the following in methods/gpgv.cc.



          if (strncmp(buffer, GNUPGKEYEXPIRED, sizeof(GNUPGKEYEXPIRED)-1) == 0)

          if (Debug == true)
          std::clog << "Got KEYEXPIRED! " << std::endl;
          WorthlessSigners.push_back(string(buffer+sizeof(GNUPGPREFIX)));



          And it doesn't seem to be be behind any form of conditional.



          However the check can be worked around by using faketime. e.g.



          faketime 2017-01-01 apt-get update





          share|improve this answer























          • Excellent answer for a seemingly poor question. +1

            – Rui F Ribeiro
            Feb 21 at 21:44










          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',
          autoActivateHeartbeat: false,
          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%2f502170%2fapt-disable-signature-expiry-checks%23new-answer', 'question_page');

          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          2














          I have come to the conclusion that there is no way to disable this check in apt, the code that implements the check is the following in methods/gpgv.cc.



          if (strncmp(buffer, GNUPGKEYEXPIRED, sizeof(GNUPGKEYEXPIRED)-1) == 0)

          if (Debug == true)
          std::clog << "Got KEYEXPIRED! " << std::endl;
          WorthlessSigners.push_back(string(buffer+sizeof(GNUPGPREFIX)));



          And it doesn't seem to be be behind any form of conditional.



          However the check can be worked around by using faketime. e.g.



          faketime 2017-01-01 apt-get update





          share|improve this answer























          • Excellent answer for a seemingly poor question. +1

            – Rui F Ribeiro
            Feb 21 at 21:44















          2














          I have come to the conclusion that there is no way to disable this check in apt, the code that implements the check is the following in methods/gpgv.cc.



          if (strncmp(buffer, GNUPGKEYEXPIRED, sizeof(GNUPGKEYEXPIRED)-1) == 0)

          if (Debug == true)
          std::clog << "Got KEYEXPIRED! " << std::endl;
          WorthlessSigners.push_back(string(buffer+sizeof(GNUPGPREFIX)));



          And it doesn't seem to be be behind any form of conditional.



          However the check can be worked around by using faketime. e.g.



          faketime 2017-01-01 apt-get update





          share|improve this answer























          • Excellent answer for a seemingly poor question. +1

            – Rui F Ribeiro
            Feb 21 at 21:44













          2












          2








          2







          I have come to the conclusion that there is no way to disable this check in apt, the code that implements the check is the following in methods/gpgv.cc.



          if (strncmp(buffer, GNUPGKEYEXPIRED, sizeof(GNUPGKEYEXPIRED)-1) == 0)

          if (Debug == true)
          std::clog << "Got KEYEXPIRED! " << std::endl;
          WorthlessSigners.push_back(string(buffer+sizeof(GNUPGPREFIX)));



          And it doesn't seem to be be behind any form of conditional.



          However the check can be worked around by using faketime. e.g.



          faketime 2017-01-01 apt-get update





          share|improve this answer













          I have come to the conclusion that there is no way to disable this check in apt, the code that implements the check is the following in methods/gpgv.cc.



          if (strncmp(buffer, GNUPGKEYEXPIRED, sizeof(GNUPGKEYEXPIRED)-1) == 0)

          if (Debug == true)
          std::clog << "Got KEYEXPIRED! " << std::endl;
          WorthlessSigners.push_back(string(buffer+sizeof(GNUPGPREFIX)));



          And it doesn't seem to be be behind any form of conditional.



          However the check can be worked around by using faketime. e.g.



          faketime 2017-01-01 apt-get update






          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Feb 21 at 21:11









          plugwashplugwash

          1,876619




          1,876619












          • Excellent answer for a seemingly poor question. +1

            – Rui F Ribeiro
            Feb 21 at 21:44

















          • Excellent answer for a seemingly poor question. +1

            – Rui F Ribeiro
            Feb 21 at 21:44
















          Excellent answer for a seemingly poor question. +1

          – Rui F Ribeiro
          Feb 21 at 21:44





          Excellent answer for a seemingly poor question. +1

          – Rui F Ribeiro
          Feb 21 at 21:44

















          draft saved

          draft discarded
















































          Thanks for contributing an answer to Unix & Linux Stack Exchange!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid


          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.

          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f502170%2fapt-disable-signature-expiry-checks%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

          How to check contact read email or not when send email to Individual?

          Bahrain

          Postfix configuration issue with fips on centos 7; mailgun relay