Finding Chrome vuln. means setting up VM, install VS, depot_tools, etc. Check out source, build from source. Takes a day to get started.
Day 2 of trying to build Chromium from source... maybe I should just report the vuln as-is and not bother trying to analyze?
-
-
Finally got to the point where I can start building... but now I'm getting missing include file errors... sigh
-
The instructions worked well for me: https://chromium.googlesource.com/chromium/src/+/master/docs/windows_build_instructions.md …
-
I'm building it by the book.
-
...but the book is ambiguous, presumes some knowledge of the build process I don't have and doesn't help with this error.
-
I did a build 2 weeks ago and worked fine for me
-
That's great! I don't see how that helps me though :)
-
true:) DM?
End of conversation
New conversation -
-
-
well, recently when analysing Firefox Mobile (Fennec) bug, didn't built it at all, too... Too much time to set it up.
-
Since open-source projects don't buy contributors by definition, you'd expect them to lower the bar to help as much as possible.
-
...but this is obviously not the case for the majority of such projects.
End of conversation
New conversation -
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.