Announcing the Windows Bounty Program
101–110 of 121 posts
Re: Announcing the Windows Bounty Program
#102Earlier quoted context omitted.
To begin with, some OSS doesn't even know how to treat people who report bugs.
The average OSS project probably is better about that than the average software company though - at least with OSS projects you can be reasonably secure that they won't send lawyers or the police after you for finding bugs.
I had a bug using NLTK to display parse trees in Jupyter notebooks. NLTK uses tkinter to render the parse trees to PostScript and GhostScript to produce a png image. The chain broke when the PostScript output had a font size of 0.
If this had been a bug in a closed-source program, all I could have put in a bug report would have been "doesn't work, pls fix".
Instead, I could submit a workaround to NLTK and start looking for the reason tkinter generated malformed PostScript output. This turned out to be because Tcl/Tk's font handling used Xft, which used FontConfig, and used an integer for the font size where FontConfig expected a double. Everything worked fine until FontConfig started doing floating point math on the font size. The Tk maintainer who triaged my bug report couldn't even reproduce it on his system, because his version of FontConfig only ever copied the value.
Only because every component of the chain was open source, was it possible to track the bug down and fix it.
Re: Announcing the Windows Bounty Program
#103I've come to feel that a Windows 10 machine is more secure than an OSX machine, all else being equal.
Re: Announcing the Windows Bounty Program
#104Earlier quoted context omitted.
Yes, with some effort: https://github.com/drduh/macOS-Security-and-Privacy-Guide You probably could with the same amount of effort for Windows, but at least Windows makes it more clear that it is happening.
As far as telemetry goes, there is a simple on or off checkbox in the Security and Privacy control panel.
Re: Announcing the Windows Bounty Program
#105> If a researcher reports a qualifying vulnerability already found internally by Microsoft, a payment will be made to the first finder at a maximum of 10% of the highest amount they could’ve received (example: $1,500 for a RCE in Edge, $25,000 for RCE in Hyper-V) Wow. I guess this kind of functions as hush money? To make sure they don't reveal the issue before MS patches it. But still, this seems like a good move.
It also encourages researchers to do research, by making it less likely they'll do a pile of research only to be told "sorry, we already found this, you get nothing". Right now, pursuing a bounty is a risky proposition; this makes it less risky.
Re: Announcing the Windows Bounty Program
#106I still consider these fees way too low. I understand there are not too many legal buyers for Windows bugs, but wonder whether it is more profitable from a financial pov to just disclose bugs as an upfront investment and wait for a PR disaster to have some actual leverage to negotiate fair prices.
Re: Announcing the Windows Bounty Program
#107Bounties for Edge? Isn't it less than 5% in browser market share? I like the fact they're offering a bounty program, I'm just surprised Edge was included I guess.
Re: Announcing the Windows Bounty Program
#108Re: Announcing the Windows Bounty Program
#109Earlier quoted context omitted.
On the other side, e.g. Egor Homakov hacked GitHub a few times through vulnerabilities in Rails. GitHub paid him bounties anyway. I'm no expert, but it appears to me that at times it does work, just not always.
Is github itself open source tho?
Re: Announcing the Windows Bounty Program
#110I still consider these fees way too low. I understand there are not too many legal buyers for Windows bugs, but wonder whether it is more profitable from a financial pov to just disclose bugs as an upfront investment and wait for a PR disaster to have some actual leverage to negotiate fair prices.
If the PR disaster already happened why would they pay you? Makes no sense.