SSH keys undeletable?
Reported by 20man | June 26th, 2008 @ 07:43 PM
our repo:
git@github.com:mtwentyman/kluster.git
will not accept our ssl keys that were used on a previous repo
git@github.com:giraffesoft/kluster.git
we did not fork.
james can not delete from the former giraffesoft repo.
any ideas?
Comments and changes to this ticket
-
Tom Preston-Werner July 13th, 2008 @ 02:14 PM
- → State changed from “new” to “open”
- → Assigned user changed from “” to “Tom Preston-Werner”
Are you talking about deploy keys? Right now deploy keys must be unique for every repo. Until we allow duplicate deploy keys you can simply generate a new key on the server and then use that as your deploy key.
-
20man July 13th, 2008 @ 03:26 PM
we ended up doing just that... but the issue was that we couldn't remove them from one repo and then use them with the other.
-
Tom Preston-Werner July 26th, 2008 @ 01:31 PM
- → State changed from “open” to “waiting”
Is this resolved for you, or were you still seeing a problem with the key deletion?
-
20man July 26th, 2008 @ 02:47 PM
Yes, i was just able to add and delete a deploy key. however, i can't verify that the key isn't still stored on your system and then used to check against future inputs (acting as paranoid or some such). deleted at approximately 17:44 EST.
-
Tom Preston-Werner July 26th, 2008 @ 04:13 PM
- → State changed from “waiting” to “resolved”
We do not store keys once they're deleted. You should be good to go.
Please Login or create a free account to add a new comment.
You can update this ticket by sending an email to from your email client. (help)
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
