SUSE Linux Signature verification failed












1















When I code, build and sign .rpm file for SUSE Linux, it is signed successfully as follows:



rpm --checksig -v xxx.rpm



Header V4 RSA/SHA256 Signature, key ID 7936b039: OK
Header SHA1 digest: OK
Header SHA256 digest: OK
Payload SHA256 digest: OK
V4 RSA/SHA256 Signature, key ID 7936b039: OK
MD5 digest: OK


But when I copy this file to a SUSE Linux Enterprise 12 SP3 PC and recheck, the result is as follows:



rpm --checksig -v xxx.rpm



Header V4 RSA/SHA256 Signature, key ID 7936b039: NOKEY
Header SHA1 digest: OK (62415d048bc9e59e70037e94e41e54e1087a93af)
V4 RSA/SHA256 Signature, key ID 7936b039: NOKEY
MD5 digest: OK (bde2174905b9e9b05953b148385ed99a)


And then while installing, I get an error:



xxx.rpm:



Header V4 RSA/SHA256 Signature, key ID 7936b039: NOKEY
V4 RSA/SHA256 Signature, key ID 7936b039: NOKEY

xxx-15.4.2.1-0.x86_64 (Plain RPM files cache): Signature verification failed [4-Signatures public key is not available]
Abort, retry, ignore? [a/r/i] (a):


I researched some solutions on the Internet and I tried to re-import public key file (I created when signing RPM file) before installing:
sudo rpm --import RPM-GPG-KEY-faleman



But it's still failed.



What is the reason of this issue?



How can I sign my .RPM file to be able to install successfully on SUSE Linux without getting error messages?










share|improve this question





























    1















    When I code, build and sign .rpm file for SUSE Linux, it is signed successfully as follows:



    rpm --checksig -v xxx.rpm



    Header V4 RSA/SHA256 Signature, key ID 7936b039: OK
    Header SHA1 digest: OK
    Header SHA256 digest: OK
    Payload SHA256 digest: OK
    V4 RSA/SHA256 Signature, key ID 7936b039: OK
    MD5 digest: OK


    But when I copy this file to a SUSE Linux Enterprise 12 SP3 PC and recheck, the result is as follows:



    rpm --checksig -v xxx.rpm



    Header V4 RSA/SHA256 Signature, key ID 7936b039: NOKEY
    Header SHA1 digest: OK (62415d048bc9e59e70037e94e41e54e1087a93af)
    V4 RSA/SHA256 Signature, key ID 7936b039: NOKEY
    MD5 digest: OK (bde2174905b9e9b05953b148385ed99a)


    And then while installing, I get an error:



    xxx.rpm:



    Header V4 RSA/SHA256 Signature, key ID 7936b039: NOKEY
    V4 RSA/SHA256 Signature, key ID 7936b039: NOKEY

    xxx-15.4.2.1-0.x86_64 (Plain RPM files cache): Signature verification failed [4-Signatures public key is not available]
    Abort, retry, ignore? [a/r/i] (a):


    I researched some solutions on the Internet and I tried to re-import public key file (I created when signing RPM file) before installing:
    sudo rpm --import RPM-GPG-KEY-faleman



    But it's still failed.



    What is the reason of this issue?



    How can I sign my .RPM file to be able to install successfully on SUSE Linux without getting error messages?










    share|improve this question



























      1












      1








      1








      When I code, build and sign .rpm file for SUSE Linux, it is signed successfully as follows:



      rpm --checksig -v xxx.rpm



      Header V4 RSA/SHA256 Signature, key ID 7936b039: OK
      Header SHA1 digest: OK
      Header SHA256 digest: OK
      Payload SHA256 digest: OK
      V4 RSA/SHA256 Signature, key ID 7936b039: OK
      MD5 digest: OK


      But when I copy this file to a SUSE Linux Enterprise 12 SP3 PC and recheck, the result is as follows:



      rpm --checksig -v xxx.rpm



      Header V4 RSA/SHA256 Signature, key ID 7936b039: NOKEY
      Header SHA1 digest: OK (62415d048bc9e59e70037e94e41e54e1087a93af)
      V4 RSA/SHA256 Signature, key ID 7936b039: NOKEY
      MD5 digest: OK (bde2174905b9e9b05953b148385ed99a)


      And then while installing, I get an error:



      xxx.rpm:



      Header V4 RSA/SHA256 Signature, key ID 7936b039: NOKEY
      V4 RSA/SHA256 Signature, key ID 7936b039: NOKEY

      xxx-15.4.2.1-0.x86_64 (Plain RPM files cache): Signature verification failed [4-Signatures public key is not available]
      Abort, retry, ignore? [a/r/i] (a):


      I researched some solutions on the Internet and I tried to re-import public key file (I created when signing RPM file) before installing:
      sudo rpm --import RPM-GPG-KEY-faleman



      But it's still failed.



      What is the reason of this issue?



      How can I sign my .RPM file to be able to install successfully on SUSE Linux without getting error messages?










      share|improve this question
















      When I code, build and sign .rpm file for SUSE Linux, it is signed successfully as follows:



      rpm --checksig -v xxx.rpm



      Header V4 RSA/SHA256 Signature, key ID 7936b039: OK
      Header SHA1 digest: OK
      Header SHA256 digest: OK
      Payload SHA256 digest: OK
      V4 RSA/SHA256 Signature, key ID 7936b039: OK
      MD5 digest: OK


      But when I copy this file to a SUSE Linux Enterprise 12 SP3 PC and recheck, the result is as follows:



      rpm --checksig -v xxx.rpm



      Header V4 RSA/SHA256 Signature, key ID 7936b039: NOKEY
      Header SHA1 digest: OK (62415d048bc9e59e70037e94e41e54e1087a93af)
      V4 RSA/SHA256 Signature, key ID 7936b039: NOKEY
      MD5 digest: OK (bde2174905b9e9b05953b148385ed99a)


      And then while installing, I get an error:



      xxx.rpm:



      Header V4 RSA/SHA256 Signature, key ID 7936b039: NOKEY
      V4 RSA/SHA256 Signature, key ID 7936b039: NOKEY

      xxx-15.4.2.1-0.x86_64 (Plain RPM files cache): Signature verification failed [4-Signatures public key is not available]
      Abort, retry, ignore? [a/r/i] (a):


      I researched some solutions on the Internet and I tried to re-import public key file (I created when signing RPM file) before installing:
      sudo rpm --import RPM-GPG-KEY-faleman



      But it's still failed.



      What is the reason of this issue?



      How can I sign my .RPM file to be able to install successfully on SUSE Linux without getting error messages?







      rpm gpg suse signature






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Oct 7 '18 at 11:55









      Jeff Schaller

      41.5k1056132




      41.5k1056132










      asked Oct 4 '18 at 4:07









      Cuong HuynhCuong Huynh

      61




      61






















          2 Answers
          2






          active

          oldest

          votes


















          0














          You likely used incompatible GPG key (V4). Like this guy https://localsteve.wordpress.com/2013/02/06/signing-rpms-cause-unverifiable-v4-signatures-and-extreme-frustration/



          Try to create different key with different crypto algo.






          share|improve this answer































            0














            SLE12 has older version of RPM (4.11.2) which don't support V4 signatures. So change your build config to use V3 signatures:D



            some help can be found in this https://adminotes.blogspot.com/2011/12/centos-6-rpm-sign-problem-v4-signatures.html






            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',
              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%2f473132%2fsuse-linux-signature-verification-failed%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









              0














              You likely used incompatible GPG key (V4). Like this guy https://localsteve.wordpress.com/2013/02/06/signing-rpms-cause-unverifiable-v4-signatures-and-extreme-frustration/



              Try to create different key with different crypto algo.






              share|improve this answer




























                0














                You likely used incompatible GPG key (V4). Like this guy https://localsteve.wordpress.com/2013/02/06/signing-rpms-cause-unverifiable-v4-signatures-and-extreme-frustration/



                Try to create different key with different crypto algo.






                share|improve this answer


























                  0












                  0








                  0







                  You likely used incompatible GPG key (V4). Like this guy https://localsteve.wordpress.com/2013/02/06/signing-rpms-cause-unverifiable-v4-signatures-and-extreme-frustration/



                  Try to create different key with different crypto algo.






                  share|improve this answer













                  You likely used incompatible GPG key (V4). Like this guy https://localsteve.wordpress.com/2013/02/06/signing-rpms-cause-unverifiable-v4-signatures-and-extreme-frustration/



                  Try to create different key with different crypto algo.







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Oct 7 '18 at 17:48









                  msuchymsuchy

                  85655




                  85655

























                      0














                      SLE12 has older version of RPM (4.11.2) which don't support V4 signatures. So change your build config to use V3 signatures:D



                      some help can be found in this https://adminotes.blogspot.com/2011/12/centos-6-rpm-sign-problem-v4-signatures.html






                      share|improve this answer




























                        0














                        SLE12 has older version of RPM (4.11.2) which don't support V4 signatures. So change your build config to use V3 signatures:D



                        some help can be found in this https://adminotes.blogspot.com/2011/12/centos-6-rpm-sign-problem-v4-signatures.html






                        share|improve this answer


























                          0












                          0








                          0







                          SLE12 has older version of RPM (4.11.2) which don't support V4 signatures. So change your build config to use V3 signatures:D



                          some help can be found in this https://adminotes.blogspot.com/2011/12/centos-6-rpm-sign-problem-v4-signatures.html






                          share|improve this answer













                          SLE12 has older version of RPM (4.11.2) which don't support V4 signatures. So change your build config to use V3 signatures:D



                          some help can be found in this https://adminotes.blogspot.com/2011/12/centos-6-rpm-sign-problem-v4-signatures.html







                          share|improve this answer












                          share|improve this answer



                          share|improve this answer










                          answered Feb 5 at 13:09









                          mimi.vxmimi.vx

                          30917




                          30917






























                              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%2f473132%2fsuse-linux-signature-verification-failed%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 make a Squid Proxy server?

                              Is this a new Fibonacci Identity?

                              Touch on Surface Book