Live data from Hacker News

A Whole New Code Search

github.com

71–80 of 113 posts

Re: A Whole New Code Search

#71

Interesting: https://github.com/search?p=4&q=gmail_password&ref=s... https://github.com/search?p=4&q=secret_token&ref=sea...

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?

Re: A Whole New Code Search

#76

Interesting: https://github.com/search?p=4&q=gmail_password&ref=s... https://github.com/search?p=4&q=secret_token&ref=sea...

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.

Re: A Whole New Code Search

#77

Earlier quoted context omitted.

I did change the readme to point to the new mainline development. I still think there might be some utility in having the code as I left it around, so I didn't delete the repo.

Deleting your repo and recreating it as a fork of the new upstream may be a good idea, although it does break the links to all of the other repositories forked from yours. It really would be nice if Github handled this case better.

Deleting and recreating your repo isn't necessary. If there's a problem with your fork not showing up, let us know and we'll look into it.

Re: A Whole New Code Search

#78
post #46

Cudos to github. I am running http://searchco.de/ I know how hard this problem actually is and they have done a fantastic job of it.

Nice! impressed by speed and quality of the results + features. Definitively going to use this in the feature. Also enjoyed your blog post on how to create a search engine.

Thanks! It has been 2 years in the making to this point, straight after Google Code Search closed and I was feeling the pain of its loss.

Re: A Whole New Code Search

#79
post #63

Interesting: https://github.com/search?p=4&q=gmail_password&ref=s... https://github.com/search?p=4&q=secret_token&ref=sea...

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

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.s...

Re: A Whole New Code Search

#80
post #68

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

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.

Post reply on HN