<div dir="ltr">
<p class="MsoNormal"><span lang="EN-US">Hi Tom,</span></p>
<p class="MsoNormal"><span lang="EN-US"><br>Thank you
for the response!<br><br></span></p>
<p class="MsoNormal"><span lang="EN-US">I’ve
started to dive in process, collecting information about BreakPad and<span> </span>Socorro. Also I created the blog for project
- <a href="https://torcrashreporter.wordpress.com">https://torcrashreporter.wordpress.com</a>. In few days I'll try to send draft of proposal.<br><br></span></p><p class="MsoNormal"><span lang="EN-US">Regards<br></span></p><p class="MsoNormal"><span lang="EN-US">Nur-Magomed<br></span></p>
</div><div class="gmail_extra"><br><div class="gmail_quote">2017-03-20 18:18 GMT+03:00 Tom Ritter <span dir="ltr"><<a href="mailto:tom@ritter.vg" target="_blank">tom@ritter.vg</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Nur-Magomed,<br>
<br>
Great to have you interested in this!<br>
<br>
So we would want to use the Crash Reporter that's built into Mozilla<br>
Firefox (which is called Breakpad, and is adapted from Chromium). At<br>
a high level, I would break down the project into the following<br>
sections:<br>
<br>
1) Get the crash reporter built (at all) in our toolchain. We<br>
currently disable it and I know there will be at least one or two<br>
hurdles to overcome here as we've never tried to built this on<br>
Linux-for-Windows. If you wish you could focus on a single platform<br>
for this at a time (e.g. Linux) so you can move onto the next step.<br>
<br>
2) Audit the crash reporter data and see what it is that gets<br>
reported, when, and how. We'd want to err on the side of caution about<br>
what we report in a dump. So we'd need to enumerate each field that<br>
gets reported, get some samples of the data, and review if we'd want<br>
to include it or not. We'd also want to review what prefs govern crash<br>
submissions, how crashes get stored (which I think is on-disk next to<br>
Tor Browser), and when they get reported.<br>
<br>
3) Change the way they get reported. We absolutely cannot have crashes<br>
sitting around on disk next to Tor Browser for the next time the user<br>
starts the browser - no matter how much data we strip out of them. So<br>
we'll need to brainstorm how we might try submitting them immediately<br>
upon crash instead of next startup.<br>
<br>
4) Get a submission server running. Mozilla has a ton of tools to<br>
analyze crashes (<a href="https://crash-stats.mozilla.org/home/product/Firefox" rel="noreferrer" target="_blank">https://crash-stats.mozilla.<wbr>org/home/product/Firefox</a><br>
is one and <a href="https://github.com/mozilla/socorro" rel="noreferrer" target="_blank">https://github.com/mozilla/<wbr>socorro</a> is the general backend).<br>
We should look at Socorro and probably adapt it for use by Tor rather<br>
than building our own.<br>
<br>
5) Circle back and get the crash reporter built reproducibly, and for<br>
all platforms. I put this one last because it may be the case that<br>
there are annoying time-sinks here, and I think by doing this last<br>
you'll be able to make the most headway on things that will take the<br>
most time - like enumerating, documenting, and evaluating the fields;<br>
and fiddling with Socorro.<br>
<br>
<br>
This is my take on it - Georg may have additional thoughts.<br>
<br>
-tom<br>
<div><div class="h5"><br>
On 20 March 2017 at 09:01, teor <<a href="mailto:teor2345@gmail.com">teor2345@gmail.com</a>> wrote:<br>
><br>
><br>
>> On 19 Mar 2017, at 19:02, Nur-Magomed <<a href="mailto:nmagoru@gmail.com">nmagoru@gmail.com</a>> wrote:<br>
>><br>
>> Hi!<br>
>> I'm interesred with project "Crash Reporter for Tor Browser".<br>
>> I'm working on that idea, but I need some specifications about how it should work, what kind of crash information we have to get and what technologies I can use on server side (for collect information).<br>
>> ...<br>
><br>
> Hi Nur-Magomed,<br>
><br>
> I've cc'd the mentors for the Crash Reporter project on this email.<br>
><br>
> Please be aware that we have a meeting this week and next week, so some<br>
> of us are busy travelling and working together in person.<br>
><br>
> T<br>
><br>
> --<br>
> Tim Wilson-Brown (teor)<br>
><br>
> teor2345 at gmail dot com<br>
> PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B<br>
> ricochet:ekmygaiu4rzgsk6n<br>
> xmpp: teor at torproject dot org<br>
> ------------------------------<wbr>------------------------------<wbr>------------<br>
><br>
</div></div>______________________________<wbr>_________________<br>
tor-dev mailing list<br>
<a href="mailto:tor-dev@lists.torproject.org">tor-dev@lists.torproject.org</a><br>
<a href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev" rel="noreferrer" target="_blank">https://lists.torproject.org/<wbr>cgi-bin/mailman/listinfo/tor-<wbr>dev</a><br>
</blockquote></div><br></div>