Live data from Hacker News

How I hacked Github again

homakov.blogspot.com

111–120 of 202 posts

Re: How I hacked Github again

#111
post #106
post #101

Earlier quoted context omitted.

I don't get why Github just hasn't hired the guy already.

In his earlier work at least, he's seemed like a loose cannon.

He was also very young then I believe, now he's realised he can make a lot of money by acting cool and professional so he does.

Re: How I hacked Github again

#112
It would be great for educational purposes if a sample app was setup so this vulnerability could be tried on it. Most of the white hack vulnerabilities are fixed by the time white hat blog posts come out so there is no way to actually try them out.

Re: How I hacked Github again

#113
post #85

Earlier quoted context omitted.

As briefly as possible? Infosec is hard. Most companies have virtually no security policies. Nobody listens. Black hats are ahead in the arms race and anyone who has decent knowledge (doesn't even have to be anywhere near on a level like Homakov or Zalewski) can pull off all sorts of exploits. Even if they don't strike the application itself, they'll get you through infrastructure that your application relies on. Loo…

> Infosec is hard. In computer security, you have to get it right every single time. The bad guys only need to get it right once.

No one gets it right every single time. No one. That's a completely unrealistic expectation. What you do is establish a bar, which you share with everyone who will use your software. Then you evaluate your efforts against that bar.

One of the keys to developing good software is hiring third-parties to conduct audits. A bug bounty program is one way to incentivize people who are already probing your software to take the next step and tell you about the bugs they find.

Re: How I hacked Github again

#114
post #105
post #29

Earlier quoted context omitted.

There's a number of people who would like donate but not interested in consulting.. There were always people complaining "Add a donate address" Now "why you added a donate address". Oh, Internet.

Is there a way to guarantee you will spend donations on alcohol and not waste them on things like rent or food?

Send him an e-mail saying, "Hey, I sent you $100. I would deeply appreciate it if you spent it on your beverage of choice, or a nice dinner with a friend, rather than on necessities."

It's no guarantee, of course. :)

Re: How I hacked Github again

#115
post #111
post #106

Earlier quoted context omitted.

In his earlier work at least, he's seemed like a loose cannon.

He was also very young then I believe, now he's realised he can make a lot of money by acting cool and professional so he does.

And that could be why he might now be considered, but why he wasn't before.

Re: How I hacked Github again

#116
post #22
post #15

Earlier quoted context omitted.

"nothing" never happened IRL. I either work extra for free trying to find more, and punch myself until I find something.

There are always n+1 bugs. I presume the same could be said for security holes- especially considering they are sometimes the result of bugs.

True, there are always bugs and security issues, but security issues tend to ramp even quicker than general bugs up from trivial to find to very, very difficult to find, so finding bug n+1 may be substantially harder than finding bug n.

Given a reasonably competent development team, you can usually make a first pass and find quite a number of low-hanging fruit security issues. Everyone makes mistakes, especially when under pressure to get a product out. Once those are gone you can use fuzzing and/or static analysis type techniques to find another set, but after that you get to the point where the bugs start getting quite obscure and require a fairly deep knowledge of how the system works so you can start stringing multiple problems together to get to a real security issue.

Of course this can be offset somewhat by the fact that software is usually a moving target, so if you're security testing a live, active codebase the developers are likely introducing new issues all the time, though hopefully at a reduced rate as they learn from their previous errors.

Re: How I hacked Github again

#118
I'm the only that thinks that $4000 was very cheap on part of Github? a security hole like this on the wrong hands would have bring severe consequences to github, consequences so big that they would probably pay $1,000,000 USD for it to never happen. So maybe something in the $50-100K would sound more reasonable. Egor is a great hacker with no business sense? On the other hand, the publicity his service gets for this its probably worth more than $50-100K.

Re: How I hacked Github again

#119
post #105
post #29

Earlier quoted context omitted.

There's a number of people who would like donate but not interested in consulting.. There were always people complaining "Add a donate address" Now "why you added a donate address". Oh, Internet.

Is there a way to guarantee you will spend donations on alcohol and not waste them on things like rent or food?

yes. donate to someone who makes $400/hour.

Re: How I hacked Github again

#120

Earlier quoted context omitted.

Really great attitude. I would make this your tagline in some way - "I will find vulnerabilities. If I don't, I will become a vulnerability to my own body and attack myself until I do!"

Did we really just make an "In Soviet Russia" joke? That was appropriate? Man, I love this place.

Not getting you. And no not my intent. What he said was funny and I found it funny. Nothing to do with Russia at all.
Post reply on HN