Activity log for bug #328445
Date | Who | What changed | Old value | New value | Message |
---|---|---|---|---|---|
2009-02-12 10:43:01 | Matt Zimmerman | bug | added bug | ||
2009-02-12 10:43:01 | Matt Zimmerman | bug | added attachment 'Dependencies.txt' (Dependencies.txt) | ||
2009-02-12 10:57:42 | Soren Hansen | openssh: status | New | Incomplete | |
2009-02-12 10:57:42 | Soren Hansen | openssh: statusexplanation | |||
2009-02-12 12:45:51 | Dustin Kirkland | openssh: status | Incomplete | Confirmed | |
2009-02-12 12:45:51 | Dustin Kirkland | openssh: importance | Undecided | High | |
2009-02-12 12:45:51 | Dustin Kirkland | openssh: statusexplanation | Thanks for opening the new bug. I'm marking confirmed, and high. I found that I could create a new key, and happily use that new keypair for public key authentication until I rebooted. Once I reboot, it's almost like that key is "blacklisted", and no longer usable per the error message in the title of the bug. I get the same issue with programs: ssh, scp, rsync, putty. Like Matt, I'm running ssh-agent. :-Dustin :-Dustin | ||
2009-02-12 17:22:37 | Dustin Kirkland | marked as duplicate | 328127 | ||
2009-05-04 11:21:34 | Matt Zimmerman | removed subscriber Matt Zimmerman | |||
2009-05-04 22:54:57 | Jeffrey Baker | removed subscriber Jeffrey Baker | |||
2009-05-12 14:24:16 | Joel Stanley | removed subscriber Joel Stanley | |||
2009-05-12 15:00:30 | Matthew Gregg | removed subscriber Matthew Gregg | |||
2010-03-31 16:07:54 | Mark McKibben | removed subscriber Manzabar |