153

Found this in our repo…

Comments
  • 30
    How... How do people end up committing their private SSH key!?
  • 5
    cat id_rsa < /dev/null | git commit -am "y'all st00pid" (or something like that)
  • 7
    @xewl git history though..

    However I think you might be able to go to that exact commit, change the key and --amend it to overwrite the history? Not sure....
  • 1
    @incognito I recall reading about that too
  • 14
    @incognito actually he should generate a new key and remove the old one from wherever he was using it, replacing with a new one. This one is already exposed anyway, so it's maybe pointless removing from the history.
  • 0
    @lucaspar well yeah duhh, I didn't mean to save his hold key from being leaked, I ment for cleaning up the git history 😉
  • 2
    I wonder if there were previous merge conflicts 😀
  • 2
    Make whoever committed that lose their job and change the keypair first. This behaviour is just ridiculous.
  • 5
    @Condor It’s his company though...
  • 1
    @Condor @dermetfan Well.. Yippee ki-yay! xD
    Mistakes happen, just make sure you don't use it anywhere anymore..
  • 0
    Now thats what I call security
  • 2
    Please tell me this is a private repo
  • 2
    I see a fellow ranger user!
  • 0
    How is this even possible??
  • 0
    @GodlikeBlock git add ssh; git commit -m ''; git push origin branch
  • 0
    @lucaspar how do you not die while typing those commands?
  • 0
    Much security ... many ssh.. wow
  • 0
    Why showing just the file name, show what you did with that.
Add Comment