Bug 1199290 - Unable to unlock the Gnome2 Key Storage
Summary: Unable to unlock the Gnome2 Key Storage
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: seahorse
Version: 21
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-03-05 20:47 UTC by Bill C. Riemers
Modified: 2015-12-02 17:36 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-12-02 09:48:27 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Bill C. Riemers 2015-03-05 20:47:51 UTC
Description of problem:

The following post for ubuntu describes the problem perfectly.
http://askubuntu.com.80bola.com/questions/586330/certificates-gnome2-key-storage-folder-cannot-unlock

Basically what happens is if in Konversation I click on a link such as

http://password.corp.redhat.com/newca.crt

I'll be prompted to import the CA.   But when I attempt to import it I get a message the GNOME2 Keyring is locked.  No matter what password I try, it remains locked.

In seahorse, it will even tell me what the password is supposed to be.  But cutting and pasting that password still won't unlock it.


Version-Release number of selected component (if applicable):

seahorse-3.14.0-3.fc21.x86_64

How reproducible:

100%.

Steps to Reproduce:
1. Open seahorse
2. Attempt to enter unlock GNOME 2 Keyring
3. Enter any password.

Actual results:

No password can unlock it.

Expected results:

I should be able to unlock this with say my login password, or have a way to delete and recreate with a password I know.


Additional info:

Note: I use LDAP kerberos login.

Comment 1 Tim Hughes 2015-05-07 15:16:42 UTC
I removed $HOME/.pki/nssdb and then logged out and back in again and it recreated the certificate database with my login password

Comment 2 Fedora End Of Life 2015-11-04 10:01:45 UTC
This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '21'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 21 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 3 Fedora End Of Life 2015-12-02 09:48:31 UTC
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.