Got mail, bounty from MS @ h1- checked window, no flying pigs.
But when trying to cash it:
Are you out of money or what is going on?
@msftsecuritypic.twitter.com/FcuTIoJE9p
You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
Split the submission into two- now it is again after rule change- so invalid, even though original submission was 100% before rule change.
I have not accepted any offers to make an article about your shamefull behavior because of the saying: "Never attribute to malice that which is adequately explained by stupidity" But how do you get dressed in the morning?
I think there is something very wrong internally: The missing payments The rule change that removes bounty because of "upcoming mitigation"- but its a lie, not even in internal yet. The lying, manipulation and general bad behavior. Always a fake reason for invalid submission
And thing is...you used to be cool. That is why I decided to take as chance and become full time bounty hunter. But I think you write checks you cannot cash- if people do it too well suddenly faults,errors and cheating happen. Unofficial rules, nobody talks about in public
How about next time before you mark as not in scope you just ask why you are wrong first? Because you are always wrong when rejecting my submissions and it takes 5-6 months for you to do anything when complaining apperently. Add 5-6 months before you investigate case, +4 for pay
Claim that two submissions are the same bug- though one bypassess needing symlink privelegie. The other enables creating any file in system32 with me as owner. Sure, my POC used a symlink dir to easy get shell, but not relevant at all. How bout asking?
Claim that submission is dupe- but hey, I know you also clamed that to the other submitter- with me as original submitter. Bet it works 99% of the time though.....
Claim that submission is dupe- but hey, I know you also clamed that to the other submitter- with me as original submitter. Bet it works 99% of the time though.....
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.