GPG invalid signature on self-signed repository
Clash Royale CLAN TAG#URR8PPP up vote
0
down vote
favorite
Foreword: we are using Spacewalk to distribute some internal packages to Ubuntu systems via a private repository, thus necessitating the self-signing. Unfortunately Spacewalk doesn't handle the signing portion of this yet, so it has to be done manually.
We are having issues with apt stating that signatures are invalid for the Release files::
# apt update
Apt-Spacewalk: Updating sources.list
Ign:1 spacewalk://spacewalk.server extras-ubuntu InRelease
[...]
Reading package lists... Done
W: GPG error: spacewalk://spacewalk.server extras-ubuntu Release:
The following signatures were invalid: 41CDF527725B5CD68EA405AA27D22AF72385D175
The key is imported to apt-key
# apt-key list
/etc/apt/trusted.gpg
--------------------
pub rsa2048 2018-03-23 [SC]
41CD F527 725B 5CD6 8EA4 05AA 27D2 2AF7 2385 D175
uid [ unknown] Spacewalk (For GPG signing APT repos) <nobody@nowhere>
And the Release file is, in fact, signed with the correct key:
# gpg -k
/root/.gnupg/pubring.gpg
------------------------
pub 2048R/2385D175 2018-03-23
uid Spacewalk (For GPG signing APT repos) <nobody@nowhere>
# gpg ./Release.gpg
Detached signature.
Please enter name of data file: Release
gpg: Signature made Fri 23 Mar 2018 10:43:50 AM EDT using RSA key ID 2385D175
gpg: Good signature from "Spacewalk (For GPG signing APT repos) <nobody@nowhere>"
What is the cause of this invalid signature error and how can we fix it? We strictly followed the instructions on http://www.devops-blog.net/spacewalk/gpg-signing-apt-repository-in-spacewalk so everything seems like it should work, but it doesn't.
apt gnupg
asked Mar 23 at 15:06
ngst
11
add a comment |Â
up vote
0
down vote
favorite
Foreword: we are using Spacewalk to distribute some internal packages to Ubuntu systems via a private repository, thus necessitating the self-signing. Unfortunately Spacewalk doesn't handle the signing portion of this yet, so it has to be done manually.
We are having issues with apt stating that signatures are invalid for the Release files::
# apt update
Apt-Spacewalk: Updating sources.list
Ign:1 spacewalk://spacewalk.server extras-ubuntu InRelease
[...]
Reading package lists... Done
W: GPG error: spacewalk://spacewalk.server extras-ubuntu Release:
The following signatures were invalid: 41CDF527725B5CD68EA405AA27D22AF72385D175
The key is imported to apt-key
# apt-key list
/etc/apt/trusted.gpg
--------------------
pub rsa2048 2018-03-23 [SC]
41CD F527 725B 5CD6 8EA4 05AA 27D2 2AF7 2385 D175
uid [ unknown] Spacewalk (For GPG signing APT repos) <nobody@nowhere>
And the Release file is, in fact, signed with the correct key:
# gpg -k
/root/.gnupg/pubring.gpg
------------------------
pub 2048R/2385D175 2018-03-23
uid Spacewalk (For GPG signing APT repos) <nobody@nowhere>
# gpg ./Release.gpg
Detached signature.
Please enter name of data file: Release
gpg: Signature made Fri 23 Mar 2018 10:43:50 AM EDT using RSA key ID 2385D175
gpg: Good signature from "Spacewalk (For GPG signing APT repos) <nobody@nowhere>"
What is the cause of this invalid signature error and how can we fix it? We strictly followed the instructions on http://www.devops-blog.net/spacewalk/gpg-signing-apt-repository-in-spacewalk so everything seems like it should work, but it doesn't.
apt gnupg
asked Mar 23 at 15:06
ngst
11
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
Foreword: we are using Spacewalk to distribute some internal packages to Ubuntu systems via a private repository, thus necessitating the self-signing. Unfortunately Spacewalk doesn't handle the signing portion of this yet, so it has to be done manually.
We are having issues with apt stating that signatures are invalid for the Release files::
# apt update
Apt-Spacewalk: Updating sources.list
Ign:1 spacewalk://spacewalk.server extras-ubuntu InRelease
[...]
Reading package lists... Done
W: GPG error: spacewalk://spacewalk.server extras-ubuntu Release:
The following signatures were invalid: 41CDF527725B5CD68EA405AA27D22AF72385D175
The key is imported to apt-key
# apt-key list
/etc/apt/trusted.gpg
--------------------
pub rsa2048 2018-03-23 [SC]
41CD F527 725B 5CD6 8EA4 05AA 27D2 2AF7 2385 D175
uid [ unknown] Spacewalk (For GPG signing APT repos) <nobody@nowhere>
And the Release file is, in fact, signed with the correct key:
# gpg -k
/root/.gnupg/pubring.gpg
------------------------
pub 2048R/2385D175 2018-03-23
uid Spacewalk (For GPG signing APT repos) <nobody@nowhere>
# gpg ./Release.gpg
Detached signature.
Please enter name of data file: Release
gpg: Signature made Fri 23 Mar 2018 10:43:50 AM EDT using RSA key ID 2385D175
gpg: Good signature from "Spacewalk (For GPG signing APT repos) <nobody@nowhere>"
What is the cause of this invalid signature error and how can we fix it? We strictly followed the instructions on http://www.devops-blog.net/spacewalk/gpg-signing-apt-repository-in-spacewalk so everything seems like it should work, but it doesn't.
apt gnupg
asked Mar 23 at 15:06
ngst
11
Foreword: we are using Spacewalk to distribute some internal packages to Ubuntu systems via a private repository, thus necessitating the self-signing. Unfortunately Spacewalk doesn't handle the signing portion of this yet, so it has to be done manually.
We are having issues with apt stating that signatures are invalid for the Release files::
# apt update
Apt-Spacewalk: Updating sources.list
Ign:1 spacewalk://spacewalk.server extras-ubuntu InRelease
[...]
Reading package lists... Done
W: GPG error: spacewalk://spacewalk.server extras-ubuntu Release:
The following signatures were invalid: 41CDF527725B5CD68EA405AA27D22AF72385D175
The key is imported to apt-key
# apt-key list
/etc/apt/trusted.gpg
--------------------
pub rsa2048 2018-03-23 [SC]
41CD F527 725B 5CD6 8EA4 05AA 27D2 2AF7 2385 D175
uid [ unknown] Spacewalk (For GPG signing APT repos) <nobody@nowhere>
And the Release file is, in fact, signed with the correct key:
# gpg -k
/root/.gnupg/pubring.gpg
------------------------
pub 2048R/2385D175 2018-03-23
uid Spacewalk (For GPG signing APT repos) <nobody@nowhere>
# gpg ./Release.gpg
Detached signature.
Please enter name of data file: Release
gpg: Signature made Fri 23 Mar 2018 10:43:50 AM EDT using RSA key ID 2385D175
gpg: Good signature from "Spacewalk (For GPG signing APT repos) <nobody@nowhere>"
What is the cause of this invalid signature error and how can we fix it? We strictly followed the instructions on http://www.devops-blog.net/spacewalk/gpg-signing-apt-repository-in-spacewalk so everything seems like it should work, but it doesn't.
apt gnupg
apt gnupg
asked Mar 23 at 15:06
ngst
11
asked Mar 23 at 15:06
ngst
11
asked Mar 23 at 15:06
ngst
11
asked Mar 23 at 15:06
ngst
11
asked Mar 23 at 15:06
ngst
11
11
add a comment |Â
add a comment |Â
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
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%2faskubuntu.com%2fquestions%2f1018585%2fgpg-invalid-signature-on-self-signed-repository%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
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');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
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');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
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