Bug 858513

Created attachment 614167 [details]
yum history

Could you post the version of the gnome-keyring package? In addition, please post any messages in /var/log/messages that come from gnome-keyring-daemon.

gnome-keyring-3.4.1-3.fc17

Created attachment 614197 [details]
cat /var/log/messages | grep keyring

Did you change your unix login password recently? Not that that should be a problem, but will give clues.

I see this line in the logs: fixed login keyring password to match login password

No, I didnt change it since I installed fc17 (fresh install). Maybe this is the problem, maybe its thinking I change it.

I'm hitting this too.  It's only failing on one of my ssh keys, but that key works on other machines.

Hmm.  Downgrading gnome-keyring and gnome-keyring-pam doesn't fix this.

Now this is weird.  Here's my .ssh/config for this key:

HOST *.fedoraproject.org fedorapeople.org *.fedorahosted.org
     IdentityFile ~/.ssh/NAMEOFKEY

I can get to fedorapeople.org and git.fedorahosted.org, but not pkgs.fedoraproject.org.

Error is ssh_exchange_identification: Connection closed by remote host

With -vvv:

[limb@tycho ~]$ ssh pkgs.fedoraproject.org -vvv
OpenSSH_5.9p1, OpenSSL 1.0.0j-fips 10 May 2012
debug1: Reading configuration data /home/limb/.ssh/config
debug1: /home/limb/.ssh/config line 1: Applying options for *.fedoraproject.org
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 50: Applying options for *
debug2: ssh_connect: needpriv 0
debug1: Connecting to pkgs.fedoraproject.org [209.132.181.4] port 22.
debug1: Connection established.
debug3: Incorrect RSA1 identifier
debug3: Could not load "/home/limb/.ssh/NAMEOFKEY" as a RSA1 public key
debug1: identity file /home/limb/.ssh/NAMEOFKEY type 1
debug1: identity file /home/limb/.ssh/NAMEOFKEY-cert type -1
ssh_exchange_identification: Connection closed by remote host

This fails even if g-k-daemon isn't running.

My local mirror is messed up, and I can't install the new gcc update.  I updated everything else and can still ssh normally with the key above.  It's something in libgomp, libquadmath, or libstdc++ most likely.

Or not.  That didn't help.

Please ignore everything I've said, network error. <headdesk>

maybe because my password is too short? I use a 4 letters password

there is a way to redo my keyring while this bug isnt fixed? this is annoying

I had a coworker run into this recently.  This has to be a network error of some sort, possibly on pkgs.fedoraproject.org.  

If you try and telnet to port 22, you should get a SSH daemon identification.  Instead the connection closes.


Jeff

I am not sure my bug report goes here. Here is the scenario.
a) Using Dec 8 DVD Beta for Fedora 18, I do a full Gnome installation, selecting most options.
I am asked to reboot, which I do
I am asked to create a user, and a user password, which I do.
my password is  #password     where the first character is the octothorpe.
I am givn the logon screen. I enter the password as defined #password 
The password is refused.

I switch to logon as root.   Password is all lowercase alpha (until I am satisfied I can change root pwd.  I use root in terminal mode to reset the logon password of the user (also is the administrator)
The password is still refused.  

My keyboard in GUI is French(Canada). I am using terminal mode in Gnome. As terminal mode as ctl-alt-F2...ctl-alt-F6  does not work for either of the two keyboard layouts I chose (default is Canada (French) with 2nd keyboard English (USA) 

Currently via root logon, I am running yum -update.  Just to mention that when I did that with the Nov 20 beta rc1, that following the yum update, password recognition and depiction of the proper keyboard layout worked.

In my case the keyring problem was due to a mismatch between virtual console (tty1..ttyn), where the password was created with Canadian French keyboard and where the # (octothorpe) maps to a different key (English (USA)).

Need virtual consoles to match user default.

OK, I got it to.

I've change password some time ago (like 2 weeks) and keyring worked fine for some time but it stopped today.

Log messages I got:

fixed login keyring password to match login password
unsupported key algorithm in certificate: 1.2.840.10045.2.1
Gcr: the prepared data does not have the correct protocol prefix

Got it again:

Jan 16 12:24:55 jpliszka3 gnome-keyring-daemon[1996]: fixed login keyring password to match login password


And again I cannot login with my password.

This makes the whole gnome keyring unusable, please fix it.

This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. 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 WONTFIX if it remains open with a Fedora 
'version' of '17'.

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 prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 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 to Fedora 17's end of life.

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.

Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.

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