How do I get deboostrap (via live-build) to use Raspbian's release keyring?

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











up vote
3
down vote

favorite












I am trying to use live-build 5.0 on Debian squeeze to build a Raspbian live image. The sudo lb build command fails during the debootstrap phase, at the step:



I: Checking Release signature
E: Release signed by unknown key (key id 9165938D90FDDD2E)


I have tried (on the build system):



  • installing the Raspbian repo key using sudo apt-key add

  • manually installing raspbian-archive-keyring_20120528.2_all.deb

  • adding the Raspbian key to config/archives/raspbian.key.(binary|chroot) (ie. from /usr/share/keyrings/raspbian-archive-keyring.gpg)

  • prepending DEBOOTSTRAP_OPTIONS="--keyring=/usr/share/keyrings/raspbian-archive-keyring.gpg" to lb config and lb build

  • same, but for /etc/apt/trusted.gpg

  • including --keyring-packages "raspbian-archive-keyring" in my auto/config

None of it worked. What do I need to do to tell debootstrap to use a different keyring? I don't want to tell it not to verify anything at all.






debian raspbian







share|improve this question





















  • Try wget https://archive.raspbian.org/raspbian.public.key gpg --import raspbian.public.key debootstrap --keyring /root/.gnupg/pubring.gpg If the above fails then birchroad.wordpress.com/2012/06/09/… may be of use to you.
    – ChrisK
    Feb 8 '16 at 15:31














up vote
3
down vote

favorite












I am trying to use live-build 5.0 on Debian squeeze to build a Raspbian live image. The sudo lb build command fails during the debootstrap phase, at the step:



I: Checking Release signature
E: Release signed by unknown key (key id 9165938D90FDDD2E)


I have tried (on the build system):



  • installing the Raspbian repo key using sudo apt-key add

  • manually installing raspbian-archive-keyring_20120528.2_all.deb

  • adding the Raspbian key to config/archives/raspbian.key.(binary|chroot) (ie. from /usr/share/keyrings/raspbian-archive-keyring.gpg)

  • prepending DEBOOTSTRAP_OPTIONS="--keyring=/usr/share/keyrings/raspbian-archive-keyring.gpg" to lb config and lb build

  • same, but for /etc/apt/trusted.gpg

  • including --keyring-packages "raspbian-archive-keyring" in my auto/config

None of it worked. What do I need to do to tell debootstrap to use a different keyring? I don't want to tell it not to verify anything at all.






debian raspbian







share|improve this question





















  • Try wget https://archive.raspbian.org/raspbian.public.key gpg --import raspbian.public.key debootstrap --keyring /root/.gnupg/pubring.gpg If the above fails then birchroad.wordpress.com/2012/06/09/… may be of use to you.
    – ChrisK
    Feb 8 '16 at 15:31












up vote
3
down vote

favorite









up vote
3
down vote

favorite











I am trying to use live-build 5.0 on Debian squeeze to build a Raspbian live image. The sudo lb build command fails during the debootstrap phase, at the step:



I: Checking Release signature
E: Release signed by unknown key (key id 9165938D90FDDD2E)


I have tried (on the build system):



  • installing the Raspbian repo key using sudo apt-key add

  • manually installing raspbian-archive-keyring_20120528.2_all.deb

  • adding the Raspbian key to config/archives/raspbian.key.(binary|chroot) (ie. from /usr/share/keyrings/raspbian-archive-keyring.gpg)

  • prepending DEBOOTSTRAP_OPTIONS="--keyring=/usr/share/keyrings/raspbian-archive-keyring.gpg" to lb config and lb build

  • same, but for /etc/apt/trusted.gpg

  • including --keyring-packages "raspbian-archive-keyring" in my auto/config

None of it worked. What do I need to do to tell debootstrap to use a different keyring? I don't want to tell it not to verify anything at all.






debian raspbian







share|improve this question













I am trying to use live-build 5.0 on Debian squeeze to build a Raspbian live image. The sudo lb build command fails during the debootstrap phase, at the step:



I: Checking Release signature
E: Release signed by unknown key (key id 9165938D90FDDD2E)


I have tried (on the build system):



  • installing the Raspbian repo key using sudo apt-key add

  • manually installing raspbian-archive-keyring_20120528.2_all.deb

  • adding the Raspbian key to config/archives/raspbian.key.(binary|chroot) (ie. from /usr/share/keyrings/raspbian-archive-keyring.gpg)

  • prepending DEBOOTSTRAP_OPTIONS="--keyring=/usr/share/keyrings/raspbian-archive-keyring.gpg" to lb config and lb build

  • same, but for /etc/apt/trusted.gpg

  • including --keyring-packages "raspbian-archive-keyring" in my auto/config

None of it worked. What do I need to do to tell debootstrap to use a different keyring? I don't want to tell it not to verify anything at all.






debian raspbian




debian raspbian






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Jan 21 '16 at 3:30









detly

1,36341424




1,36341424











  • Try wget https://archive.raspbian.org/raspbian.public.key gpg --import raspbian.public.key debootstrap --keyring /root/.gnupg/pubring.gpg If the above fails then birchroad.wordpress.com/2012/06/09/… may be of use to you.
    – ChrisK
    Feb 8 '16 at 15:31
















  • Try wget https://archive.raspbian.org/raspbian.public.key gpg --import raspbian.public.key debootstrap --keyring /root/.gnupg/pubring.gpg If the above fails then birchroad.wordpress.com/2012/06/09/… may be of use to you.
    – ChrisK
    Feb 8 '16 at 15:31















Try wget https://archive.raspbian.org/raspbian.public.key gpg --import raspbian.public.key debootstrap --keyring /root/.gnupg/pubring.gpg If the above fails then birchroad.wordpress.com/2012/06/09/… may be of use to you.
– ChrisK
Feb 8 '16 at 15:31




Try wget https://archive.raspbian.org/raspbian.public.key gpg --import raspbian.public.key debootstrap --keyring /root/.gnupg/pubring.gpg If the above fails then birchroad.wordpress.com/2012/06/09/… may be of use to you.
– ChrisK
Feb 8 '16 at 15:31










2 Answers
2






active

oldest

votes

















up vote
2
down vote



accepted










This was a very basic mistake. I was prepending DEBOOTSTRAP_OPTIONS="--keyring=/usr/share/keyrings/raspbian-archive-keyring.gpg" to lb config && sudo lb build, not realising that sudo does not allow environment variables through (because of the Defaults env_reset line in sudoers).



When I invoked with sudo DEBOOTSTRAP_OPTIONS="--keyring=/usr/share/keyrings/raspbian-archive-keyring.gpg" lb build, it was successful.






share|improve this answer



























    up vote
    0
    down vote













    As root run:



    wget -qO - https://archive.raspbian.org/raspbian.public.key | gpg --import -
    debootstrap --keyring /root/.gnupg/pubring.kbx ...





    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: false,
      showLowRepImageUploadWarning: true,
      reputationToPostImages: null,
      bindNavPrevention: true,
      postfix: "",
      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%2f256702%2fhow-do-i-get-deboostrap-via-live-build-to-use-raspbians-release-keyring%23new-answer', 'question_page');

      );

      Post as a guest

















      2 Answers
      2






      active

      oldest

      votes








      2 Answers
      2






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes








      up vote
      2
      down vote



      accepted










      This was a very basic mistake. I was prepending DEBOOTSTRAP_OPTIONS="--keyring=/usr/share/keyrings/raspbian-archive-keyring.gpg" to lb config && sudo lb build, not realising that sudo does not allow environment variables through (because of the Defaults env_reset line in sudoers).



      When I invoked with sudo DEBOOTSTRAP_OPTIONS="--keyring=/usr/share/keyrings/raspbian-archive-keyring.gpg" lb build, it was successful.






      share|improve this answer
























        up vote
        2
        down vote



        accepted










        This was a very basic mistake. I was prepending DEBOOTSTRAP_OPTIONS="--keyring=/usr/share/keyrings/raspbian-archive-keyring.gpg" to lb config && sudo lb build, not realising that sudo does not allow environment variables through (because of the Defaults env_reset line in sudoers).



        When I invoked with sudo DEBOOTSTRAP_OPTIONS="--keyring=/usr/share/keyrings/raspbian-archive-keyring.gpg" lb build, it was successful.






        share|improve this answer






















          up vote
          2
          down vote



          accepted







          up vote
          2
          down vote



          accepted






          This was a very basic mistake. I was prepending DEBOOTSTRAP_OPTIONS="--keyring=/usr/share/keyrings/raspbian-archive-keyring.gpg" to lb config && sudo lb build, not realising that sudo does not allow environment variables through (because of the Defaults env_reset line in sudoers).



          When I invoked with sudo DEBOOTSTRAP_OPTIONS="--keyring=/usr/share/keyrings/raspbian-archive-keyring.gpg" lb build, it was successful.






          share|improve this answer












          This was a very basic mistake. I was prepending DEBOOTSTRAP_OPTIONS="--keyring=/usr/share/keyrings/raspbian-archive-keyring.gpg" to lb config && sudo lb build, not realising that sudo does not allow environment variables through (because of the Defaults env_reset line in sudoers).



          When I invoked with sudo DEBOOTSTRAP_OPTIONS="--keyring=/usr/share/keyrings/raspbian-archive-keyring.gpg" lb build, it was successful.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Feb 7 '16 at 19:12









          detly

          1,36341424




          1,36341424






















              up vote
              0
              down vote













              As root run:



              wget -qO - https://archive.raspbian.org/raspbian.public.key | gpg --import -
              debootstrap --keyring /root/.gnupg/pubring.kbx ...





              share|improve this answer
























                up vote
                0
                down vote













                As root run:



                wget -qO - https://archive.raspbian.org/raspbian.public.key | gpg --import -
                debootstrap --keyring /root/.gnupg/pubring.kbx ...





                share|improve this answer






















                  up vote
                  0
                  down vote










                  up vote
                  0
                  down vote









                  As root run:



                  wget -qO - https://archive.raspbian.org/raspbian.public.key | gpg --import -
                  debootstrap --keyring /root/.gnupg/pubring.kbx ...





                  share|improve this answer












                  As root run:



                  wget -qO - https://archive.raspbian.org/raspbian.public.key | gpg --import -
                  debootstrap --keyring /root/.gnupg/pubring.kbx ...






                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Aug 17 at 8:49









                  dimir

                  1413




                  1413



























                       

                      draft saved


                      draft discarded















































                       


                      draft saved


                      draft discarded














                      StackExchange.ready(
                      function ()
                      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f256702%2fhow-do-i-get-deboostrap-via-live-build-to-use-raspbians-release-keyring%23new-answer', 'question_page');

                      );

                      Post as a guest
































































                      -

                      Popular posts from this blog

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

                      Image
                      Clash Royale CLAN TAG #URR8PPP up vote 1 down vote favorite I'm using WordPress 4.9.8, CiviCRM to 5.5.1, I usually send email to contact by Search> Find contacts View contact details Action> Send email Send email ok, Contact received mail ok like picture But status only Email sent though contact read email or not. So, can CiviCRM can change status to Email read when contact read email? wordpress email share | improve this question asked Sep 26 at 0:12 ToanLuong 49 9 add a comment  |  up vote 1 down vote favorite I'm using WordPress 4.9.8, CiviCRM to 5.5.1, I usually send email to contact by Search> Find contacts View contact details Action> Send email Send email ok, Contact received mail ok like picture But status only Email sent though contact read email or not. So, can CiviCRM can change status to Email read when contact read email? wordpress email share | improve this question asked Se
                      Read more

                      Bahrain

                      Image
                      For other uses, see Bahrain (disambiguation). Sovereign island state in the Persian Gulf Kingdom of Bahrain مملكة البحرين   (Arabic) Mamlakat al-Baḥrayn Flag Coat of arms Anthem:  نشيد البحرين الوطني Bahrainona Our Bahrain Location of   Bahrain    (circled in red) Capital and largest city Manama 26°13′N 50°35′E  /  26.217°N 50.583°E  / 26.217; 50.583 Official languages Arabic Ethnic groups (2010 [1] ) 50.7% Arab (46% Bahrani, 4.7% other Arabs) 45.5% Asian 1% European 1.2% Others Religion Islam Demonym(s) Bahraini Government Unitary constitutional monarchy • King Hamad bin Isa Al Khalifa • Crown Prince Salman bin Hamad bin Isa Al Khalifa • Prime Minister Khalifa bin Salman Al Khalifa Legislature National Assembly • Upper house Consultative Council • Lower house Council of Representatives Independence • Declared Independence [2] 14 August 1971 • from United Kingdom [1] 15 August 1971 • Admitted to the United Nations 21 September 1971 • Kingdom of Bahrain 14 February 2002
                      Read more

                      Postfix configuration issue with fips on centos 7; mailgun relay

                      Image
                      Clash Royale CLAN TAG #URR8PPP up vote 0 down vote favorite I am trying to setup postfix to relay all mail generated on the local machine via SMTP to a mailgun relay. I have used the mailgun relay before with success on an ubuntu server, but I am migrating to a Centos 7 server which I will be running in FIPS mode. There error log is below, slightly sanitized. I have a small enough network that I choose to have each machine reach out to mailgun individually (this the loopback-only, 127.0.0.0/8 restrictions) and no firewall open port allowing smtp in to the machine. I assume the FIPS mode (and with it disabling of MD5) is causing problems, but I don't know how to overcome it or if it is even possible for tls_fprint to use some supported hash such as sha256 or sha512. However, the relay=none is slightly concerning since I have relayhost set, but perhaps that is because the smtp process is failing? Any help would be appreciated! postconf -n: alias_database = hash:/etc/alia
                      Read more