Ttgjyuk

Is domain driven design an anti-SQL pattern?

What to wear for invited talk in Canada

Where else does the Shulchan Aruch quote an authority by name?

Was there ever an axiom rendered a theorem?

Prime joint compound before latex paint?

Re-submission of rejected manuscript without informing co-authors

How can I plot a Farey diagram?

LWC and complex parameters

A poker game description that does not feel gimmicky

Where to refill my bottle in India?

How to move the player while also allowing forces to affect it

Typesetting a double Over Dot on top of a symbol

Denied boarding due to overcrowding, Sparpreis ticket. What are my rights?

Can the Produce Flame cantrip be used to grapple, or as an unarmed strike, in the right circumstances?

COUNT(*) or MAX(id) - which is faster?

What is the command to reset a PC without deleting any files

How would photo IDs work for shapeshifters?

How can I add custom success page

Is ipsum/ipsa/ipse a third person pronoun, or can it serve other functions?

Need help identifying/translating a plaque in Tangier, Morocco

How could a lack of term limits lead to a "dictatorship?"

Does the average primeness of natural numbers tend to zero?

Unbreakable Formation vs. Cry of the Carnarium

What do you call something that goes against the spirit of the law, but is legal when interpreting the law to the letter?

“GPG error:The following signatures were invalid: KEYEXPIRED”

Why MySQL Repository Key suddenly expired?“no public key available” on apt-get updateUbuntu 16.04 - Can't run software update or apt-get-updatei got error after sudo apt-get updateCannot upgrade to MySQL 8 from 5.7What is “dist-upgrade” and why does it upgrade more than “upgrade”?How can I fix a 404 Error when using a PPA or updating my package lists?“GPG error: Release: The following signatures were invalid: BADSIG”Errors on apt-get update: Ubuntu 16.04What is the easiest way to resolve apt-get BADSIG GPG errors?Update Manager Error - Authentication Errorproblem in software updaterWARNING: The following packages cannot be authenticated. `apt-key update` doesn't workofficial nginx trusty ppa gives KEYEXPIRED gpg errorUbuntu 14.04 LTS apt-get update error : Some index files failed to download. They have been ignored, or old ones used insteadGPG invalid signature on self-signed repositoryprivate repo : The following signatures were invalidunable to locate package and updation problemopenprinting key for ubuntu 18

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;

27

6

The error I am having when trying to update my package list.

W: GPG error: http://download.opensuse.org ./ Release: The following signatures were invalid: KEYEXPIRED 1436387333
E: Some index files failed to download. They have been ignored, or old ones used instead.

apt

share|improve this question

edited Jul 20 '15 at 21:21

Braiam

52.6k20138223

asked Jul 18 '15 at 23:02

mr_azadmr_azad

81051838

add a comment | 

27

6

The error I am having when trying to update my package list.

W: GPG error: http://download.opensuse.org ./ Release: The following signatures were invalid: KEYEXPIRED 1436387333
E: Some index files failed to download. They have been ignored, or old ones used instead.

apt

share|improve this question

edited Jul 20 '15 at 21:21

Braiam

52.6k20138223

asked Jul 18 '15 at 23:02

mr_azadmr_azad

81051838

add a comment | 

The error I am having when trying to update my package list.

W: GPG error: http://download.opensuse.org ./ Release: The following signatures were invalid: KEYEXPIRED 1436387333
E: Some index files failed to download. They have been ignored, or old ones used instead.

apt

share|improve this question

edited Jul 20 '15 at 21:21

Braiam

52.6k20138223

asked Jul 18 '15 at 23:02

mr_azadmr_azad

81051838

W: GPG error: http://download.opensuse.org ./ Release: The following signatures were invalid: KEYEXPIRED 1436387333
E: Some index files failed to download. They have been ignored, or old ones used instead.

share|improve this question

edited Jul 20 '15 at 21:21

Braiam

52.6k20138223

asked Jul 18 '15 at 23:02

mr_azadmr_azad

81051838

share|improve this question

edited Jul 20 '15 at 21:21

Braiam

52.6k20138223

asked Jul 18 '15 at 23:02

mr_azadmr_azad

81051838

edited Jul 20 '15 at 21:21

Braiam

52.6k20138223

edited Jul 20 '15 at 21:21

Braiam

52.6k20138223

asked Jul 18 '15 at 23:02

mr_azadmr_azad

81051838

asked Jul 18 '15 at 23:02

mr_azadmr_azad

81051838

5 Answers
5

active

oldest

votes

9

GPG error: http://download.opensuse.org ./ Release: The following signatures were invalid: KEYEXPIRED 1436387333

This says that your GPG key for that repository has expired, which means one of two things, either your system has the wrong date or the key really expired. For the later, you need to contact the repository maintainer and import the new key (removing the old one, probably), once the repository updates their keys to sign the files.

You can safely ignore these messages if you aren't using packages of these repositories. The message can be removed if you remove the repository from your source.list file/directory.

share|improve this answer

edited Jun 19 '18 at 10:34

answered Jul 19 '15 at 0:14

BraiamBraiam

52.6k20138223

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  ... suggest adding in confirming that the system clock is at least reasonably correct. If the system thinks its 2020, I bet that'd lead to key expired errors.
  
  – derobert
  Jul 21 '15 at 17:04
  

  
  
  
  

add a comment | 

29

I don't get the answers above, my system clock was fine.
The following worked for me:

sudo apt-key list | grep "expired: "
sudo apt-key adv --keyserver keys.gnupg.net --recv-keys [KEY]

The key being the the part behind the slash: 0000X/<this part is the key>

Or use this one liner:

sudo apt-key list | grep "expired: " | sed -ne 's|pub .*/([^ ]*) .*|1|gp' | xargs -n1 sudo apt-key adv --keyserver keys.gnupg.net --recv-keys 

share|improve this answer

edited Aug 7 '17 at 17:32

rzr

32639

answered Oct 14 '16 at 13:45

PeterPeter

39132

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  Thanks, fixed the problem for me with MySQL but used --keyserver pgp.mit.edu. Source: bugs.mysql.com/bug.php?id=85029
  
  – Craig van Tonder
  Mar 16 '17 at 20:42
  

  
  
  
  

add a comment | 

7

That ppa has been removed and no longer exists. You must find a different source for the packages installed through the samrog131 ppa.

In the meantime, run the following commands to resolve the situation.

First, to delete the expired key:

sudo apt-key del 1436387333

Then, to delete the ppa:

sudo rm /etc/apt/sources.list.d/samrog131*
sudo apt-get clean
sudo apt-get update

If you need to add a key see here.

sudo apt-get upgrade

You may want to run:

sudo apt-get dist-upgrade

depending on your situation. If you are not sure, see here.

share|improve this answer

edited Apr 13 '17 at 12:24

Community♦

1

answered Jul 18 '15 at 23:38

mchidmchid

23.6k25287

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  This wont solve anything. APT would try to fetch the packages from the PPA again, and fail at it again
  
  – Braiam
  Jul 19 '15 at 0:09
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @Braiam Actually, it does solve the problem of the 404 error for the missing samrog131 ppa, the one you deleted from the question.
  
  – mchid
  Jul 20 '15 at 21:04
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  We have duplicates that covers that issue already, you didn't answered the question fully, since you ignored the most important part which was the GPG error. Please, do not edit the question again.
  
  – Braiam
  Jul 20 '15 at 21:24
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @Braiam why not, just to make it look like my answer doesn't solve anything?
  
  – mchid
  Jul 20 '15 at 21:33
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  1) If the user added the ppa in the sources.list directly, your answer will fail, actually it will fail if add-ppa-repository wasn't used and the OP just named the file differently. 2) If you remove the key, now the warning will be replaced with an error, since the key wasn't found, therefore making more problems.
  
  – Braiam
  Jul 21 '15 at 11:25
  

  
  
  
  

 | 
show 7 more comments

2

As displayed earlier
First, to delete the expired key:

sudo apt-key del 1436387333
Then go to the site:

http://download.opensuse.org/repositories/home:/sarimkhan/xUbuntu_14.04/

and download "Release.key"
Then import the key using the ubuntu14.04 software updater or synaptic package manager.

share|improve this answer

answered Nov 29 '15 at 5:40

Anirban DasAnirban Das

211

add a comment | 

0

As simple as this should work:

apt-key adv --refresh-keys

Why use sed and xargs if gpg can sort things for itself?

share|improve this answer

answered 4 hours ago

sanmaisanmai

1314

add a comment | 

Your Answer

StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "89"
;
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: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
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

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

Name

Email

Required, but never shown

StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f650032%2fgpg-errorthe-following-signatures-were-invalid-keyexpired%23new-answer', 'question_page');

);

Post as a guest

Name

Email

Required, but never shown

9

GPG error: http://download.opensuse.org ./ Release: The following signatures were invalid: KEYEXPIRED 1436387333

This says that your GPG key for that repository has expired, which means one of two things, either your system has the wrong date or the key really expired. For the later, you need to contact the repository maintainer and import the new key (removing the old one, probably), once the repository updates their keys to sign the files.

You can safely ignore these messages if you aren't using packages of these repositories. The message can be removed if you remove the repository from your source.list file/directory.

share|improve this answer

edited Jun 19 '18 at 10:34

answered Jul 19 '15 at 0:14

BraiamBraiam

52.6k20138223

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  ... suggest adding in confirming that the system clock is at least reasonably correct. If the system thinks its 2020, I bet that'd lead to key expired errors.
  
  – derobert
  Jul 21 '15 at 17:04
  

  
  
  
  

add a comment | 

9

GPG error: http://download.opensuse.org ./ Release: The following signatures were invalid: KEYEXPIRED 1436387333

This says that your GPG key for that repository has expired, which means one of two things, either your system has the wrong date or the key really expired. For the later, you need to contact the repository maintainer and import the new key (removing the old one, probably), once the repository updates their keys to sign the files.

You can safely ignore these messages if you aren't using packages of these repositories. The message can be removed if you remove the repository from your source.list file/directory.

share|improve this answer

edited Jun 19 '18 at 10:34

answered Jul 19 '15 at 0:14

BraiamBraiam

52.6k20138223

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  ... suggest adding in confirming that the system clock is at least reasonably correct. If the system thinks its 2020, I bet that'd lead to key expired errors.
  
  – derobert
  Jul 21 '15 at 17:04
  

  
  
  
  

add a comment | 

GPG error: http://download.opensuse.org ./ Release: The following signatures were invalid: KEYEXPIRED 1436387333

This says that your GPG key for that repository has expired, which means one of two things, either your system has the wrong date or the key really expired. For the later, you need to contact the repository maintainer and import the new key (removing the old one, probably), once the repository updates their keys to sign the files.

You can safely ignore these messages if you aren't using packages of these repositories. The message can be removed if you remove the repository from your source.list file/directory.

share|improve this answer

edited Jun 19 '18 at 10:34

answered Jul 19 '15 at 0:14

BraiamBraiam

52.6k20138223

GPG error: http://download.opensuse.org ./ Release: The following signatures were invalid: KEYEXPIRED 1436387333

share|improve this answer

edited Jun 19 '18 at 10:34

answered Jul 19 '15 at 0:14

BraiamBraiam

52.6k20138223

answered Jul 19 '15 at 0:14

BraiamBraiam

52.6k20138223

answered Jul 19 '15 at 0:14

BraiamBraiam

52.6k20138223

29

I don't get the answers above, my system clock was fine.
The following worked for me:

sudo apt-key list | grep "expired: "
sudo apt-key adv --keyserver keys.gnupg.net --recv-keys [KEY]

The key being the the part behind the slash: 0000X/<this part is the key>

Or use this one liner:

sudo apt-key list | grep "expired: " | sed -ne 's|pub .*/([^ ]*) .*|1|gp' | xargs -n1 sudo apt-key adv --keyserver keys.gnupg.net --recv-keys 

share|improve this answer

edited Aug 7 '17 at 17:32

rzr

32639

answered Oct 14 '16 at 13:45

PeterPeter

39132

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  Thanks, fixed the problem for me with MySQL but used --keyserver pgp.mit.edu. Source: bugs.mysql.com/bug.php?id=85029
  
  – Craig van Tonder
  Mar 16 '17 at 20:42
  

  
  
  
  

add a comment | 

29

I don't get the answers above, my system clock was fine.
The following worked for me:

sudo apt-key list | grep "expired: "
sudo apt-key adv --keyserver keys.gnupg.net --recv-keys [KEY]

The key being the the part behind the slash: 0000X/<this part is the key>

Or use this one liner:

sudo apt-key list | grep "expired: " | sed -ne 's|pub .*/([^ ]*) .*|1|gp' | xargs -n1 sudo apt-key adv --keyserver keys.gnupg.net --recv-keys 

share|improve this answer

edited Aug 7 '17 at 17:32

rzr

32639

answered Oct 14 '16 at 13:45

PeterPeter

39132

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  Thanks, fixed the problem for me with MySQL but used --keyserver pgp.mit.edu. Source: bugs.mysql.com/bug.php?id=85029
  
  – Craig van Tonder
  Mar 16 '17 at 20:42
  

  
  
  
  

add a comment | 

I don't get the answers above, my system clock was fine.
The following worked for me:

sudo apt-key list | grep "expired: "
sudo apt-key adv --keyserver keys.gnupg.net --recv-keys [KEY]

The key being the the part behind the slash: 0000X/<this part is the key>

Or use this one liner:

sudo apt-key list | grep "expired: " | sed -ne 's|pub .*/([^ ]*) .*|1|gp' | xargs -n1 sudo apt-key adv --keyserver keys.gnupg.net --recv-keys 

share|improve this answer

edited Aug 7 '17 at 17:32

rzr

32639

answered Oct 14 '16 at 13:45

PeterPeter

39132

sudo apt-key list | grep "expired: "
sudo apt-key adv --keyserver keys.gnupg.net --recv-keys [KEY]

sudo apt-key list | grep "expired: " | sed -ne 's|pub .*/([^ ]*) .*|1|gp' | xargs -n1 sudo apt-key adv --keyserver keys.gnupg.net --recv-keys 

share|improve this answer

edited Aug 7 '17 at 17:32

rzr

32639

answered Oct 14 '16 at 13:45

PeterPeter

39132

edited Aug 7 '17 at 17:32

rzr

32639

edited Aug 7 '17 at 17:32

rzr

32639

answered Oct 14 '16 at 13:45

PeterPeter

39132

answered Oct 14 '16 at 13:45

PeterPeter

39132

7

That ppa has been removed and no longer exists. You must find a different source for the packages installed through the samrog131 ppa.

In the meantime, run the following commands to resolve the situation.

First, to delete the expired key:

sudo apt-key del 1436387333

Then, to delete the ppa:

sudo rm /etc/apt/sources.list.d/samrog131*
sudo apt-get clean
sudo apt-get update

If you need to add a key see here.

sudo apt-get upgrade

You may want to run:

sudo apt-get dist-upgrade

depending on your situation. If you are not sure, see here.

share|improve this answer

edited Apr 13 '17 at 12:24

Community♦

1

answered Jul 18 '15 at 23:38

mchidmchid

23.6k25287

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  This wont solve anything. APT would try to fetch the packages from the PPA again, and fail at it again
  
  – Braiam
  Jul 19 '15 at 0:09
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @Braiam Actually, it does solve the problem of the 404 error for the missing samrog131 ppa, the one you deleted from the question.
  
  – mchid
  Jul 20 '15 at 21:04
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  We have duplicates that covers that issue already, you didn't answered the question fully, since you ignored the most important part which was the GPG error. Please, do not edit the question again.
  
  – Braiam
  Jul 20 '15 at 21:24
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @Braiam why not, just to make it look like my answer doesn't solve anything?
  
  – mchid
  Jul 20 '15 at 21:33
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  1) If the user added the ppa in the sources.list directly, your answer will fail, actually it will fail if add-ppa-repository wasn't used and the OP just named the file differently. 2) If you remove the key, now the warning will be replaced with an error, since the key wasn't found, therefore making more problems.
  
  – Braiam
  Jul 21 '15 at 11:25
  

  
  
  
  

 | 
show 7 more comments

7

That ppa has been removed and no longer exists. You must find a different source for the packages installed through the samrog131 ppa.

In the meantime, run the following commands to resolve the situation.

First, to delete the expired key:

sudo apt-key del 1436387333

Then, to delete the ppa:

sudo rm /etc/apt/sources.list.d/samrog131*
sudo apt-get clean
sudo apt-get update

If you need to add a key see here.

sudo apt-get upgrade

You may want to run:

sudo apt-get dist-upgrade

depending on your situation. If you are not sure, see here.

share|improve this answer

edited Apr 13 '17 at 12:24

Community♦

1

answered Jul 18 '15 at 23:38

mchidmchid

23.6k25287

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  This wont solve anything. APT would try to fetch the packages from the PPA again, and fail at it again
  
  – Braiam
  Jul 19 '15 at 0:09
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @Braiam Actually, it does solve the problem of the 404 error for the missing samrog131 ppa, the one you deleted from the question.
  
  – mchid
  Jul 20 '15 at 21:04
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  We have duplicates that covers that issue already, you didn't answered the question fully, since you ignored the most important part which was the GPG error. Please, do not edit the question again.
  
  – Braiam
  Jul 20 '15 at 21:24
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @Braiam why not, just to make it look like my answer doesn't solve anything?
  
  – mchid
  Jul 20 '15 at 21:33
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  1) If the user added the ppa in the sources.list directly, your answer will fail, actually it will fail if add-ppa-repository wasn't used and the OP just named the file differently. 2) If you remove the key, now the warning will be replaced with an error, since the key wasn't found, therefore making more problems.
  
  – Braiam
  Jul 21 '15 at 11:25
  

  
  
  
  

 | 
show 7 more comments

That ppa has been removed and no longer exists. You must find a different source for the packages installed through the samrog131 ppa.

In the meantime, run the following commands to resolve the situation.

First, to delete the expired key:

sudo apt-key del 1436387333

Then, to delete the ppa:

sudo rm /etc/apt/sources.list.d/samrog131*
sudo apt-get clean
sudo apt-get update

If you need to add a key see here.

sudo apt-get upgrade

You may want to run:

sudo apt-get dist-upgrade

depending on your situation. If you are not sure, see here.

share|improve this answer

edited Apr 13 '17 at 12:24

Community♦

1

answered Jul 18 '15 at 23:38

mchidmchid

23.6k25287

sudo apt-key del 1436387333

sudo rm /etc/apt/sources.list.d/samrog131*
sudo apt-get clean
sudo apt-get update

sudo apt-get upgrade

sudo apt-get dist-upgrade

share|improve this answer

edited Apr 13 '17 at 12:24

Community♦

1

answered Jul 18 '15 at 23:38

mchidmchid

23.6k25287

edited Apr 13 '17 at 12:24

Community♦

1

edited Apr 13 '17 at 12:24

Community♦

1

answered Jul 18 '15 at 23:38

mchidmchid

23.6k25287

answered Jul 18 '15 at 23:38

mchidmchid

23.6k25287

2

As displayed earlier
First, to delete the expired key:

sudo apt-key del 1436387333
Then go to the site:

http://download.opensuse.org/repositories/home:/sarimkhan/xUbuntu_14.04/

and download "Release.key"
Then import the key using the ubuntu14.04 software updater or synaptic package manager.

share|improve this answer

answered Nov 29 '15 at 5:40

Anirban DasAnirban Das

211

add a comment | 

2

As displayed earlier
First, to delete the expired key:

sudo apt-key del 1436387333
Then go to the site:

http://download.opensuse.org/repositories/home:/sarimkhan/xUbuntu_14.04/

and download "Release.key"
Then import the key using the ubuntu14.04 software updater or synaptic package manager.

share|improve this answer

answered Nov 29 '15 at 5:40

Anirban DasAnirban Das

211

add a comment | 

As displayed earlier
First, to delete the expired key:

sudo apt-key del 1436387333
Then go to the site:

http://download.opensuse.org/repositories/home:/sarimkhan/xUbuntu_14.04/

and download "Release.key"
Then import the key using the ubuntu14.04 software updater or synaptic package manager.

share|improve this answer

answered Nov 29 '15 at 5:40

Anirban DasAnirban Das

211

share|improve this answer

answered Nov 29 '15 at 5:40

Anirban DasAnirban Das

211

answered Nov 29 '15 at 5:40

Anirban DasAnirban Das

211

answered Nov 29 '15 at 5:40

Anirban DasAnirban Das

211

0

As simple as this should work:

apt-key adv --refresh-keys

Why use sed and xargs if gpg can sort things for itself?

share|improve this answer

answered 4 hours ago

sanmaisanmai

1314

add a comment | 

0

As simple as this should work:

apt-key adv --refresh-keys

Why use sed and xargs if gpg can sort things for itself?

share|improve this answer

answered 4 hours ago

sanmaisanmai

1314

add a comment | 

As simple as this should work:

apt-key adv --refresh-keys

Why use sed and xargs if gpg can sort things for itself?

share|improve this answer

answered 4 hours ago

sanmaisanmai

1314

apt-key adv --refresh-keys

share|improve this answer

answered 4 hours ago

sanmaisanmai

1314

answered 4 hours ago

sanmaisanmai

1314

answered 4 hours ago

sanmaisanmai

1314