11–20 of 25 posts
How exactly does this happen? I can understand that some people don't understand the need to keep their private key offline, but I would have thought those people aren't really aware of the existence of the private key...so how does it end up in a github repo?
$ git add .ssh $ git commit
$ git add .
$ git commithttps://www.google.com/search?q=site%3Agithub.com+inurl%3A.s...
Same thing, right?
I almost can't believe someone would commit their .ssh directory to a public GitHub repo. Seriously - why? Your public key, sure, but the entire directory?
But of course you also want to be real careful about authenticating them (a signed tag in Git can serve that purpose).
How exactly does this happen? I can understand that some people don't understand the need to keep their private key offline, but I would have thought those people aren't really aware of the existence of the private key...so how does it end up in a github repo?
$ git add .ssh $ git commit
How exactly does this happen? I can understand that some people don't understand the need to keep their private key offline, but I would have thought those people aren't really aware of the existence of the private key...so how does it end up in a github repo?
$ git add .ssh $ git commit
We need a cross reference between this and Facebook graph search. For science. (I flagged, also, because this should be told to the guys at Github, not out in the open.) Oh, and of course, Google indexes them. Fantastic.
I almost can't believe someone would commit their .ssh directory to a public GitHub repo. Seriously - why? Your public key, sure, but the entire directory?
I almost can't believe someone would commit their .ssh directory to a public GitHub repo. Seriously - why? Your public key, sure, but the entire directory?
I purpose a corollary to Hanlon's razor: Never attribute to stupidity that which is adequately explained by ignorance?