101–110 of 113 posts
Earlier quoted context omitted.
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.
https://github.com/gomachan/dotfiles/tree/master/.ssh
Is anyone impressed else by how quickly and successfully* GitHub has been rolling out new features over the past few months? I think almost every one of their new features has in some way made my life a little easier. Kudos to the whole team. * Granted, uptime might have been a causality.
I think you mean "casualty". :)
Earlier quoted context omitted.
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.
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.
Interesting: https://github.com/search?p=4&q=gmail_password&ref=s... https://github.com/search?p=4&q=secret_token&ref=sea...
Such as when it is a key file, or is a known credential file -- "amazon_s3.yml" for example, they should send a warning to the committer.
And then show a big red flag on the website if the repo is public.
And of course, remove the results from search.
I know it's not github's responsibility, but it would help make the web a bit safer.
Nice. There are six C++ projects that use bool_t type.
> To ensure better relevancy, we're being conservative in what we add to the search index. Repository forks will not be searchable unless the fork has more stars than the parent repository, for example. This has a grandfathering problem when the maintainers switch. The new active branch of development is overshadowed by the previous branch. I've had someone takeover my project, but I still have 2 years of accumulated…
Earlier quoted context omitted.
That is terrifying, I just logged in with three separate accounts and they worked. Obviously I logged out without fucking around with anything; why mess with somebody's professional work. This is dangerous. But then again, is it Github's responsibility to keep these people from shooting themselves in the foot?
is it Github's responsibility to keep these people from shooting themselves in the foot? No.
Earlier quoted context omitted.
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.
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.
This just reminds me of Google code search and makes me miss it more. Searching by regex was pretty useful.