SSH Keys on GitHub • Hacker News Board

Re: SSH Keys on GitHub

#31

Post by netik » Tue, Aug 18, 2015, 5:59 PM UTC

I don't think they've blocked it. I can still search on id_rsa without issue.

However, The majority of the keys I'm seeing are either encrypted, test fixtures, or otherwise. There are many unencrypted keys available, though!

It's still surprising that people continue to check in private keys. No one learns.

Re: SSH Keys on GitHub

#32

Post by idunno246 » Tue, Aug 18, 2015, 6:03 PM UTC

for AWS...dont use access tokens/secrets, and just use instance profiles(theres a few mock metadata service projects). For other things, theres a bunch of services like hashicorp's vault or amazon kms that store passwords. kms + instance roles gets you fairly close, but its not really friendly to set up

Re: SSH Keys on GitHub

#33

Post by Nacraile » Tue, Aug 18, 2015, 6:07 PM UTC

FWIW, Amazon proactively scans GitHub for AWS key leaks, notifies the account holder, and flags the account (they will disable the account if they start seeing active abuse and can't get in touch with the actual owner to get keys rotated). So any keys you find are going to get invalidated in short order.

They're also pretty good about forgiving the charges for the fraudulent use.

> What is the best way to share things like API keys among a team of developers, anyway? I'm surprised this hasn't been solved already (perhaps it has and I just don't know about it). I know you can share passwords with tools like LastPass and 1Password, and I suppose you could use those for API keys as well?

Here, we have an IAM account for each dev. Permissions are basically read anything except a few sensitive things (billing, IAM), plus the write permissions we need as operators. We each have our own console login password, and keep our own access keys locally. It's pretty easy to add/remove accounts for new/departing devs, and the potential to individualize permissions is there.

Re: SSH Keys on GitHub

#34

Post by peterwwillis » Tue, Aug 18, 2015, 6:08 PM UTC

id_rsa is being blocked right now, but id_dsa and id_ecdsa still work.

Re: SSH Keys on GitHub

#35

Post by peterwwillis » Tue, Aug 18, 2015, 6:12 PM UTC

Ian Paul of PC World wrote that, "As its name suggests, LulzSec claims to be interested in mocking and embarrassing companies by exposing security flaws rather than stealing data for criminal purposes."[16] -- https://en.wikipedia.org/wiki/LulzSec

Re: SSH Keys on GitHub

#36

Post by Couto » Tue, Aug 18, 2015, 6:17 PM UTC

I'm not sure if there are other ways, better or not... but blackbox[1] can be used to store secrets.

And it might be possible to achieve some success with git filters[2], at least to avoid pushing secrets into the repository.

Still... just my two cents, I'm not exactly a pro-user of those two features

[1](https://github.com/StackExchange/blackbox)

[2](https://stackoverflow.com/questions/6557467/can-git-ignore-a...)

Re: SSH Keys on GitHub

#37

Post by admiun » Tue, Aug 18, 2015, 6:18 PM UTC

Like passwords, sharing API keys is usually a bad thing. For some sites it is overkill or simply not possible but for something like AWS there is no excuse not to make individual IAM users with their own passwords and keys.

Re: SSH Keys on GitHub

#38

Post by eykanal » Tue, Aug 18, 2015, 6:21 PM UTC

Not entirely, do the same search and only subset on "text" type (not Javascript, C++, PHP...). I was able to browse through quite a few id_rsa files.

Re: SSH Keys on GitHub

#39

Post by adelevie » Tue, Aug 18, 2015, 6:21 PM UTC

I like https://fugacio.us/ a lot.

Re: SSH Keys on GitHub

#40

Post by tg3 » Tue, Aug 18, 2015, 6:22 PM UTC

I worked on a project called Spore (http://spore.sh) to do this with a command-line tool. It works fairly well, although I've had a hard time communicating how it works to folks.