7 ms·

Or SSH private keys. https://github.com/search?q=path%3A.ssh%2Fid_rsa&type=Code&ref=searchresults https://github.com/search?q=path%3A.ssh%2Fid_rsa&type=Co...

• donretag 14y ago
  That is not the only disturbing part. SSH private key by itself is not much of a threat, but bundled together with known_hosts is a recipe for disaster.
  • graywh 14y ago
    https://github.com/gomachan/dotfiles/tree/master/.ssh https://github.com/gomachan/dotfiles/tree/master/.ssh
    • barkingcat 14y ago
      Why would people put dotfiles like ssh keys up on public github? This kind of thing is best suited for a private repo (github is still ok, just make it private) - cause it's most likely of no use to anyone but that single user.
      • jcoder 14y ago
        I would not suggest that it's okay even for a private repo. Never let your private keys leave your machine or its dedicated, encrypted backup.
        • conradev 14y ago
          Although I would never do this myself, if the keys themselves are encrypted with a password and then uploaded, it's not nearly as bad.
          • deleted 14y ago
            [deleted]
          • qznc 14y ago
            In the case of ssh keys, you usually should use a different key per device/home directory and let your server accept all the keys.
    • enneff 14y ago
      At least now someone can push to his GitHub account to remove it for him. :-)
      • ibrahima 14y ago
        Not if he has a passphrase, right?
        • enneff 14y ago
          Correct.
    • graywh 14y ago
      And that was just the one on the first page of results I got.
• jrochkind1 14y ago
  Nothing new about that, you didn't need github's improved search to do it. https://www.google.com/search?q=site%3Agithub.com+inurl%3A.ssh%2Fid_rsa&oq=site%3Agithub.com+inurl%3A.ssh%2Fid_rsa&aqs=chrome.0.57j58.2645&sourceid=chrome&ie=UTF-8 https://www.google.com/search?q=site%3Agithub.com+inurl%3A.s...
• cryowaffle 14y ago
  Or Bitcoin RPC password!