Earlier quoted context omitted.
In his earlier work at least, he's seemed like a loose cannon.
I don't think that is a fair assessment of him, even then. At any case, I hired him fairly recently for a security audit and he worked quickly, and was very effective (he found several important vulnerabilities and reported them in a crystal clear manner). He was also a pleasure to deal with (no bullshit stance, something I find enjoyable). The 4000 USD for ~20 hours of work were definitely well spent!
How I hacked Github again
181–190 of 202 posts
Re: How I hacked Github again
#182Earlier quoted context omitted.
It's actually a good strategy to price high hourly but over-deliver (doing lots of free work behind the scenes, or speculative unpaid work, etc.) -- rather than the market-clearing rate of ~100-150/hr, at least when you're trying to build a brand. At $400, he's clearly a specialist, and will get more interesting work; at $100/hr, you could hire him and just treat him like another developer, have him do cookie-cutter…
Personally, I think he'd make more money at $400-600/hr if he could also get some kind of manager to handle the interactions with clients; it doesn't seem to be what he enjoys, or is particularly good at. Completely agree. I'm not doing security, but my hourly is similar, and it was a game changer for me to have someone in a manager-like role working with me. Client relations are a huge time suck, but are also absolu…
Re: How I hacked Github again
#183Earlier quoted context omitted.
Personally, I think he'd make more money at $400-600/hr if he could also get some kind of manager to handle the interactions with clients; it doesn't seem to be what he enjoys, or is particularly good at. Completely agree. I'm not doing security, but my hourly is similar, and it was a game changer for me to have someone in a manager-like role working with me. Client relations are a huge time suck, but are also absolu…
It seems your manager is more an agent than a manager.
Re: How I hacked Github again
#184Earlier quoted context omitted.
///host.com bug is not well documented. It's "0day" for most of websites.
How did you find out about it?
Re: How I hacked Github again
#185WTF is up with Firefox and Chrome not fixing their /// bug. They're prioritising neither user security nor standards-compliance.
Re: How I hacked Github again
#186One thing that I didn't get from the post: > Oh my, another OAuth anti-pattern! Clients should never reveal actual access_token to the user agent. From what I understood by reading the OAuth RFC is that front-end intensive applications (a.k.a. public client) should have short lifespan access tokens (~ 2 hours) and the back-end takes care of reissuing a new access token when expired. Can someone clarify on how to make…
Re: How I hacked Github again
#187Earlier quoted context omitted.
It seems your manager is more an agent than a manager.
I meant manager in the sense of a band's manager. It's more than just introducing you to deals; it's handling the communications back and forth with the client on an ongoing basis; not merely the negotiation to set up the deal but the actual work-product communications as well.
Re: How I hacked Github again
#188Re: How I hacked Github again
#189Earlier quoted context omitted.
he gets paid $400/hr doing consulting for YC Companies and other startups and companies, he is from Russia, and now lives in Bangkok, when he becomes rich he wants to live in Hong Kong, pretty nice for a 20 year old, I don't see any glaring reasons to work for Github http://egorhomakov.com/
$400/hr is meaningless if comes from an one-off gig.
Re: How I hacked Github again
#190Earlier quoted context omitted.
Completely agree, GitHub private repos are a huge target. Even if you use 2FA, after login it's just a cookie that separates the good from the bad. How could GH improve that? Client-side SSL Certs?
If you're talking about for company projects, the enterprise version of Github is self-hosted (e.g. on a VPN): https://enterprise.github.com/