| You cherry-pick a one-off example (# of clients) and ignore the rest. Feel free to remove that one if you don't think it is pertinent, and address the remainder of my comment. You also cherry-picked the letter. Yes, 5 years after a history and pattern of security negligence, they are now able to repeat that pattern on H1. Hurray, positive delta. Even if all issues have been addressed, the fact that it has happened in the past (many times) means that Valve deserves skepticism going forward. You a big fan of Facebook now that they deleted those cleartext passwords? They are cool now and anything else that comes to light must just be an oopsie, deserving of no scrutiny? Or are you skeptical because Facebook has a proven pattern of dishonesty? The same thing applies to Valve. They have a proven pattern. >they responded constructively to public criticism
Uhh, you'll have to link me to a constructive response of public criticism. Since you cherry-picked one issue from the letter (which should still prove to show the pattern of bad behavior that, at the very least, used to exist), I will put a few others here: >A few members of the developer community, and no doubt members of the community at large, have received infractions against their accounts for the discovery and disclosure of bugs – a subset of which are similar to those that have been rewarded with economy items. >During this time we caught the occasional mention that Valve’s servers were indeed leaking sensitive information (such as partner session IDs, logins and cleartext passwords), however upon patching the bug Valve did not mandate a password reset. >As a result, an unknown user changed a different app’s name up to three days after the servers were patched[4] – proving that Steam Partner credentials were indeed exposed and abused during Heartbleed. I see bad security practices piled on bad practices piled onto a culture that spurns security. >I'm really at a loss as to why I'm supposed to see Valve as the villain here. I'm not telling you to look at them as a villain. I'm saying that perhaps, given a proven history of bad practices, it would be good to look at this situation with a skeptical eye (they are trying to save face, nothing else) rather than shrug it off as an "Oops! Haha, we didn't scope our bounty quite right!". Obviously we don't see eye to eye on the subject. I'll keep looking at Valve, with their repeated security blunders, with skepticism. Feel free to continue to chalk it all up to an oops. Remember the whole "Trust takes a lifetime to build, and a second to destroy"? That's the heart of where I am coming from. |
> You also cherry-picked the letter. Yes, 5 years after a history and pattern of security negligence, they are now able to repeat that pattern on H1. Hurray, positive delta.
Those were the only two arguments you made to support your claim that Valve's bug bounty program is not as good as it should be. You're accusing me of "cherry picking" because I responded the only two arguments you made. This is just laughable, and it eliminated the rest of my doubt as to whether or not you're participating in this conversation in good faith.
Let's recap your previous comment: Your first paragraph didn't make an argument, it was sharing your opinion that you think Valve's management of their bug bounty isn't up to par and that highlighting the fact that they have paid out hundreds of bounties amounts to "bragging". Your second paragraph is where you make the first actual argument, the claim that we should be able to hold them to a higher standard because of the ratio of their client install count and employees. And you added the link to the letter in an edit below that.
I respond to both of the claims you made (the client vs. employee count, and the letter) and now you're saying that I'm "cherry picking" because I'm responding to the two arguments that you brought up.