918439 - Socorro exploitability section regression?

Status: VERIFIED FIXED

(Socorro :: General, task)

Description

[David Bolter [:davidb] (NeedInfo me for attention)]

I am not seeing the exploitability section filled out these days. We should see this for windows crash signatures (when logged in).

I think this is the most recent bug where this was implemented: bug 826564.

Note: in terms of priority, I'd put bug 497731 first.

Comment 1

[Benjamin Smedberg]

I don't think this needs to be a security-sensitive bug...

Comment 2

[Laura Thomson :laura]

Selena, can you take a look at this please?

Comment 3

[Selena Deckelmann :selenamarie :selena]

The Exploitability crontabber job dropped out of the config. Adding it back!

Comment 4

[[github robot]]

Commits pushed to master at https://github.com/mozilla/socorro

https://github.com/mozilla/socorro/commit/2d8c4d17d8526977d37ed03e9dd638eb5bd50f8c
Fixes bug 918439 - add exploitability to default crontabber jobs

https://github.com/mozilla/socorro/commit/bf7f953921c88632aa22ec475c874f1f101eda89
Merge pull request #1543 from selenamarie/bug918439-exploitability-crontabber-config

Fixes bug 918439 add Exploitability report to default report list

Comment 5

[Selena Deckelmann :selenamarie :selena]

So, this will go live on Monday. I'll run some backfills for the missing data for the last two weeks later on today.

Comment 6

[Matt Brandt [:mbrandt]]

Bumping to verified as [qa-] - if you'd like QA to spend some time reviewing this patch please bump the bug to [qa+] and add minimal steps to verify.

Comment 7

[Benjamin Smedberg]

This still is not fixed on https://crash-stats.mozilla.com/report/exploitability/ - the number is the same across all of high/medium/low/none.

Comment 8

[Robert Kaiser]

(In reply to Benjamin Smedberg  [:bsmedberg] from comment #7)
> This still is not fixed on
> https://crash-stats.mozilla.com/report/exploitability/ - the number is the
> same across all of high/medium/low/none.

I had filed bug 951825 for that, should we leave it to that bug or get the work done here?

Comment 9

[Benjamin Smedberg]

I just reopened the wrong bug.