I can only accept it as a fact that my successful Pwn2Own participation attracted scrutiny to certain arguable and potentially outdated points in the contest rules. In the real world there is no such thing as an “arguable point”. An exploit either breaks the target system or not
-
Show this thread
-
By the way, the Microsoft Bug Bounty program used to have a similar point in the rules: to factor in whatever *private and internal* knowledge of an 0day bug to the vendor. Guess it raised similar concerns as it was quietly removed later. A solid precedent to think about it
6 replies 6 retweets 135 likesShow this thread -
Replying to @alisaesage
The WIP bounty removed the overlap exclusion for collisions with internal cases. Since finders can’t know what’s already been found, the exclusion did nothing to positively shape behavior.
2 replies 3 retweets 15 likes -
Replying to @metr0 @alisaesage
Quite the opposite: it caused finders to submit partial reports and then follow up with details to maximize their chance of being first, rather than waiting until they had an understanding of the bug and could help us meaningfully judge impact and root cause.
1 reply 3 retweets 13 likes -
Replying to @metr0 @alisaesage
The current WIP rules are a lot more fair and transparent. And everyone gets a better outcome.
1 reply 0 retweets 6 likes -
Replying to @metr0 @alisaesage
On the flip side the bounty rules ended up making MS pay bounties for bugs way past the level of usefulness to understand root cause. The rules were then update to remove those categories, justified by a still not shipping mitigation which will fix the issues once and for all.
2 replies 0 retweets 5 likes -
You really think that opt-in beta NTFS junction mitigation will fix the issues “once and for all”?
2 replies 0 retweets 1 like
where do I optin for that? I wanna test my bypass idea
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.