Results 1 to 4 of 4

Thread: Expired key trouble. Need help.

  1. #1

    Default Expired key trouble. Need help.

    I looked around a bit, but couldn't get a solution. I hope this is the correct forum to post this.




    • Key: E3A5C360307E3D54

      • Name: SuSE Package Signing Key <build@suse.de>
      • Finger Print: 4E98E67519D98DC7362A5990E3A5C360307E3D54
      • Created: 04/05/10
      • Expires: 03/05/14 (The key is expired.)

    • I am kind of new to this, and can't seem to find a location to remedy this. I imagine that the update error message I get in notifications could be related.

    Thanks in advance to anyone that can help.

  2. #2
    Join Date
    Aug 2010
    Location
    Chicago suburbs
    Posts
    12,756
    Blog Entries
    3

    Default Re: Expired key trouble. Need help.

    Try (at the command line):
    Code:
    gpg --recv-keys 307E3D54
    There's a newer signature in the key servers. Or, if you prefer, select that key in "kgpg" or similar graphic interface, then update it from the keyservers.
    openSUSE Leap 15.1; KDE Plasma 5;
    testing Leap 15.2Alpha

  3. #3
    Join Date
    Aug 2010
    Location
    Chicago suburbs
    Posts
    12,756
    Blog Entries
    3

    Default Re: Expired key trouble. Need help.

    An additional comment.

    You have not explained where you are getting that message. If you are getting it when installing packages, then you might have to update that key. However, in my experience, it has usually updated automatically. I think you can force an update by first adding that key to your own keyring (see my previous post). Then export that to a file. Then import that key to the package manager with "rpmkeys --import filename".
    openSUSE Leap 15.1; KDE Plasma 5;
    testing Leap 15.2Alpha

  4. #4

    Default Re: Expired key trouble. Need help.

    Quote Originally Posted by nrickert View Post
    An additional comment.

    You have not explained where you are getting that message. If you are getting it when installing packages, then you might have to update that key. However, in my experience, it has usually updated automatically. I think you can force an update by first adding that key to your own keyring (see my previous post). Then export that to a file. Then import that key to the package manager with "rpmkeys --import filename".

    Sorry. It was presenting the error when I started Software Management. The error also presented itself as part of the automatic update notification.
    I will use your console based solution. Thanks.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •