Closed
Bug 1223170
Opened 10 years ago
Closed 10 years ago
New SuperSearch based Exploitable Crashes report by default
Categories
(Socorro :: Webapp, task)
Socorro
Webapp
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1221048
People
(Reporter: peterbe, Unassigned)
References
Details
After https://bugzilla.mozilla.org/show_bug.cgi?id=1219960 we'll have two exploitable crashes reports.
The old one: https://crash-stats.mozilla.com/report/exploitability/products/Firefox
The new one: https://crash-stats.mozilla.com/exploitability/?product=Firefox
We should make the new one the default choice for the Reports drop-down.
Reporter | ||
Comment 1•10 years ago
|
||
Adrian, any reason to hold back on this one?
I'm thinking we do it next week or something.
Comment 2•10 years ago
|
||
Bug 1221172 should block this. But next week seems an appropriate time imo. We can probably do this and bug 1221048 at the same time, even.
Depends on: 1221172
![]() |
||
Comment 3•10 years ago
|
||
Also, did we test that the new report is restricted the same way as the old one (or is the overall report not restricted)?
Comment 4•10 years ago
|
||
It is correctly restricted. If you try to access it when not signed in, you will get an authentication request. If you try to access it without the view_exploitability permission, you will get a permission error.
To verify that: https://crash-stats.allizom.org/exploitability/?product=Firefox
![]() |
||
Comment 5•10 years ago
|
||
(In reply to Adrian Gaudebert [:adrian] from comment #4)
> It is correctly restricted. If you try to access it when not signed in, you
> will get an authentication request. If you try to access it without the
> view_exploitability permission, you will get a permission error.
Thanks. I have a busy week and can't look into details, just wanted to make sure that this was thought of and tested, which you awesomely did. ;-)
Reporter | ||
Updated•10 years ago
|
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•