Live data from Hacker News

A look inside Facebook's source code

sintheticlabs.com

21–30 of 53 posts

Re: A look inside Facebook's source code

#21

fascinating stuff. I'm still amazed at how many username/passwords are freely available via github search: https://github.com/search?p=96&q=gmail+password&ref=searchre... even if they have 2-step auth setup, people choose "complete the email address" as a form of authentication which you can most likely get from their github profile. the moral of the story here is - if you do not want someone to find it - do not publ…

Im not a hacker/cracker or whatever but I am curious would it be illegal to use one of those usernames and passwords to see if it actually worked for an account? edit: I know that it is not ethical and I am only slightly tempted to do it but is it actually illegal to use open source code in that way?

Depends on the jurisdiction, but generally yes it'd be illegal.

You can compare it to opening someone's home because he left his key in a public place unbeknownst to him.

You generally couldn't make the argument that 'he may have wanted people to have the key, that's why he left it in a public/open source place'. Firstly, one can't assume that, so we must hear it explicitly before it's true. And secondly, if universal open-source access was provided, there wouldn't be a key to find as there wouldn't be a lock in the first place to allow specific access. The whole point of a password or key means you do not want fully open access to all, meaning any password or key in an open-source project is likely unintentional, a mistake, and thus you'd be entering without permission which is illegal in most jurisdictions.

Re: A look inside Facebook's source code

#22

fascinating stuff. I'm still amazed at how many username/passwords are freely available via github search: https://github.com/search?p=96&q=gmail+password&ref=searchre... even if they have 2-step auth setup, people choose "complete the email address" as a form of authentication which you can most likely get from their github profile. the moral of the story here is - if you do not want someone to find it - do not publ…

Im not a hacker/cracker or whatever but I am curious would it be illegal to use one of those usernames and passwords to see if it actually worked for an account? edit: I know that it is not ethical and I am only slightly tempted to do it but is it actually illegal to use open source code in that way?

I'd say this crosses the line, in a day and age where using CURL can land jail time (e.g. AT&T "leak"). Guessing a password doesn't legally grant you the right to enter a server, either. That'd be like saying you had a right to trespass because someone left the gate open or didn't build it high enough. It doesn't work that way. I really think Github needs better protections for this. Consider a search for "export GITHUB_SECRET" ;-)

Re: A look inside Facebook's source code

#23

fascinating stuff. I'm still amazed at how many username/passwords are freely available via github search: https://github.com/search?p=96&q=gmail+password&ref=searchre... even if they have 2-step auth setup, people choose "complete the email address" as a form of authentication which you can most likely get from their github profile. the moral of the story here is - if you do not want someone to find it - do not publ…

Yeah it's crazy. Just last week I caught myself just in time. I was developing an API for this website and was testing the user login with my own credentials which I saved in a variable so I wouldn't have to retype it all the time as I tested API login functions. I finished some things and pressed the 'commit' button (commit plugin in Brackets ftw) but cancelled it when I realized I was committing an admin credential…

what company was that ?

Re: A look inside Facebook's source code

#24
post #15

fascinating stuff. I'm still amazed at how many username/passwords are freely available via github search: https://github.com/search?p=96&q=gmail+password&ref=searchre... even if they have 2-step auth setup, people choose "complete the email address" as a form of authentication which you can most likely get from their github profile. the moral of the story here is - if you do not want someone to find it - do not publ…

I understand you're just showing how easy it is to find email/password combinations, but maybe it isn't the best idea to post an example link on how to do it?

all i did was search "gmail password" in github search and paste the url here - this is not rocket science

Re: A look inside Facebook's source code

#25
post #3

Interesting. It's also interesting that Facebook developers are using Pastebin for things such as this. I would assume that they'd have an internal wiki, or gist-like app. It's also noteworthy to see how they set up their accounts: first initial, full lastname—same standard as many other companies. But seeing it laid out can help in the guessing of other names (or common name occurances, as you don't even need a full…

Speaking of the TODO, I particularly liked how the diff suggests removing it ;-) That said, it did appear to be some kind of "enterprise" version maybe?

The diff suggests removing the TODO because it adds the privacy checks. See the added canSeeFriends call.

Re: A look inside Facebook's source code

#26

fascinating stuff. I'm still amazed at how many username/passwords are freely available via github search: https://github.com/search?p=96&q=gmail+password&ref=searchre... even if they have 2-step auth setup, people choose "complete the email address" as a form of authentication which you can most likely get from their github profile. the moral of the story here is - if you do not want someone to find it - do not publ…

Equally interesting/appalling: private keys on github

https://github.com/search?p=4&q=extension%3A.key+BEGIN+RSA+P...

Re: A look inside Facebook's source code

#28

Earlier quoted context omitted.

Yeah it's crazy. Just last week I caught myself just in time. I was developing an API for this website and was testing the user login with my own credentials which I saved in a variable so I wouldn't have to retype it all the time as I tested API login functions. I finished some things and pressed the 'commit' button (commit plugin in Brackets ftw) but cancelled it when I realized I was committing an admin credential…

what company was that ?

http://bitcoinmagazine.com/1805/bitcoinica-stolen-from-again...

Re: A look inside Facebook's source code

#29

Earlier quoted context omitted.

Yeah it's crazy. Just last week I caught myself just in time. I was developing an API for this website and was testing the user login with my own credentials which I saved in a variable so I wouldn't have to retype it all the time as I tested API login functions. I finished some things and pressed the 'commit' button (commit plugin in Brackets ftw) but cancelled it when I realized I was committing an admin credential…

what company was that ?

Sounds like Bitcoinica (https://en.bitcoin.it/wiki/Bitcoinica)

Re: A look inside Facebook's source code

#30
post #3

Interesting. It's also interesting that Facebook developers are using Pastebin for things such as this. I would assume that they'd have an internal wiki, or gist-like app. It's also noteworthy to see how they set up their accounts: first initial, full lastname—same standard as many other companies. But seeing it laid out can help in the guessing of other names (or common name occurances, as you don't even need a full…

We have an internal pastebin, it's built into Phabricator.

There is no preset format for unixnames. Most people use their names but I've seen many pseudonyms. One intern famously broke some internal tools by requesting her initials, which were "www".

Post reply on HN