On Mon, 2015-01-05 at 10:36 -0700, Kevin Fenzi wrote: > > > > - Replacing an SSH key takes almost a day. > > > That should definitely not be the case. It should take about > > > 20-30min to sync out. > > That's certainly not the case. I've uploaded my work key at morning > > and 6 hours later I still cannot commit in fedora repositories. > Can you send me the exact output you get when trying to commit? Yesterday: [nmavrogi@dhcp-2-127 ocserv]$ git push Permission denied (publickey). fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. Today: [nmavrogi@dhcp-2-127 ocserv]$ git push Counting objects: 4, done. Delta compression using up to 4 threads. Compressing objects: 100% (4/4), done. Writing objects: 100% (4/4), 515 bytes | 0 bytes/s, done. Total 4 (delta 3), reused 0 (delta 0) > Perhaps it's not your key, but that you are now in denyhosts for too > many attempts? No idea about that. How many is too many? I tried a couple of times over a span of 6 hours after the change of the key. > > That accounts page; it should provide some instructions or link to > > update the koji keys as well for the account. > I'm not sure it makes sense there... many people using the account > system have no need for koji access. Only people who are packagers > would need to worry about that. I think it is the same with the ssh key. Not everyone needs it, but the way to change it is via the account page. At least a reminder that there is yet an other key, has to be there. > I can bring it up to fas developers however, or you could file a ticket > on it... > https://github.com/fedora-infra/fas/issues I'll open a ticket. regards, Nikos -- websites mailing list websites@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/websites
