SUSE Linux Signature verification failed
Clash Royale CLAN TAG#URR8PPP
up vote
1
down vote
favorite
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
New contributor
add a comment |Â
up vote
1
down vote
favorite
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
New contributor
add a comment |Â
up vote
1
down vote
favorite
up vote
1
down vote
favorite
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
New contributor
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
rpm gpg suse signature
New contributor
New contributor
edited 14 hours ago
Jeff Schaller
33.6k851113
33.6k851113
New contributor
asked Oct 4 at 4:07
Cuong Huynh
61
61
New contributor
New contributor
add a comment |Â
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
0
down vote
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.
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
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.
add a comment |Â
up vote
0
down vote
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.
add a comment |Â
up vote
0
down vote
up vote
0
down vote
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.
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.
answered 9 hours ago
msuchy
79135
79135
add a comment |Â
add a comment |Â
Cuong Huynh is a new contributor. Be nice, and check out our Code of Conduct.
Cuong Huynh is a new contributor. Be nice, and check out our Code of Conduct.
Cuong Huynh is a new contributor. Be nice, and check out our Code of Conduct.
Cuong Huynh is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
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
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password