TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Facebook puts bounties on bugs in the D programming language implementation

158 点作者 andralex超过 11 年前

7 条评论

0x0超过 11 年前
The author of the post also had a Reddit AMA recently, related to Facebook&#x27;s usage of D: <a href="http://www.reddit.com/r/IAmA/comments/1nl9at/i_am_a_member_of_facebooks_hhvm_team_a_c_and_d/" rel="nofollow">http:&#x2F;&#x2F;www.reddit.com&#x2F;r&#x2F;IAmA&#x2F;comments&#x2F;1nl9at&#x2F;i_am_a_member_o...</a><p>Among other things, he wrote the book &quot;The D Programming Language&quot;.
评论 #6744668 未加载
评论 #6745434 未加载
thepumpkin1979超过 11 年前
Google supports Go. Mozilla supports Rust. Facebook should actively support D.
评论 #6741510 未加载
评论 #6742285 未加载
评论 #6741425 未加载
评论 #6744487 未加载
评论 #6742590 未加载
mixmastamyk超过 11 年前
Good for them. I was a bit surprised by the amounts though. Is it enough to motivate?<p>Also, I notice the BountySource site is blank without javascript on. I&#x27;m not one who demands that every site work w&#x2F;o it. But, they should at least show their banner and message that it needs to be turned on. The noscript tag is twenty years old, no?
评论 #6741502 未加载
评论 #6743324 未加载
yeldarb超过 11 年前
And when can we put bounties on Facebook bugs?
评论 #6743270 未加载
pera超过 11 年前
oh another of those bounties programs... but maybe this one is different from the rest?<p>If you ever find any security issue don&#x27;t expect to obtain a bounty from the big corps easily, and not even a &quot;thanks&quot;. Once, the co-founder of one of the most important security companies told me &quot;do not expect to receive a bounty without sending a minimum of 10 emails explaining the same thing in 10 different ways... average 20&quot;. It&#x27;s a sad truth, and I think this means that usually legit critical security issues reports will not be properly rewarded because most people get tired quickly.<p>One year ago I discovered a session hijacking vulnerability on Facebook, the guy who respond my messages didn&#x27;t even know what secure flag is. After asking me how to solve the bug (the solution was actually pretty simple) they never replied to me again.<p>With Google was the same thing: last year I found leakage of sensitive user information because of bad cookies configuration, 0 bounties 0 thanks.<p>Another bad experience I had with Google, but maybe a bit of topic (sorry): almost two years ago the gmail&#x27;s cert changed for apparent no reason using a new CA, and it seemed that nobody else was having this issue (ie no mentions of this new cert on the web, googling the fingerprint returned 0 results) except me. I accepted this new cert on my laptop in my home; but then the &quot;funniest&quot; thing happened: when I connected to gmail from my university the previous cert appeared again, &quot;it&#x27;s ok.. nothing strange is happening here&quot;, but then when I went back to my home the new cert showed up again! my paranoid level went to over 9000 and immediately I connected through Tor to gmail (yup, the old nice cert was there again) and sent an encrypted mail to google&#x27;s security team explaining everything, with the fingerprints and certs info, _including_ at the end of my message my pgp pubkey. One week and a half latter.. I received an email from the &quot;security team&quot;: they replied my message in plain text, my message was quoted unencrypted (!) and they asked me how I discovered this, I told them that my browser checks for every new cert. I also told them if it would be possible to not quote in plain text encrypted mails. Then, after two days I got a new email from them, again plain taxt, and it was pretty minimalistic &quot;We checked out and the new certificate is ok&quot; EOF no digital signature no nothing, wtf! oh well... at least on the next day I connected to gmail in my home and the old good cert was there again :) (and the strange new cert never appeared again). A late Halloween story.
评论 #6742189 未加载
mkramlich超过 11 年前
surface interpretation: they want them fixed<p>sneaky possible reason: recruitment strategy that&#x27;s more likely to suss out the more &quot;elite&quot; devs<p>likely: my bet, a mix of both
评论 #6741537 未加载
hawkharris超过 11 年前
Maybe they&#x27;ll put a bounty on getting 13-year-olds to make wall posts instead of sending self-destructing photographs.