Closed
Bug 812230
Opened 12 years ago
Closed 12 years ago
SecReview Item: Review WebAppSec Secure coding checklist
Categories
(Release Engineering :: Release Automation: Other, defect)
Release Engineering
Release Automation: Other
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: curtisk, Assigned: bhearsum)
References
Details
(Whiteboard: [shipit])
SecReview tracking bug
Actions regarding the review of the dependent bug should be tracked here.
----
review web secuirty checklist https://wiki.mozilla.org/WebAppSec/Secure_Coding_QA_Checklist ::before testing
Assignee | ||
Updated•12 years ago
|
Whiteboard: [kickoff]
Assignee | ||
Comment 1•12 years ago
|
||
I think I've addressed everything on here (most of it was taken care of for free by sqlalchemy/wtforms/flask, though). We're currently in the process of getting a dev environment set-up. I think it'll be easier to do the review once that's done.
Depends on: 810461
Summary: SecReview Item: Review WebAppSec Secure coding checklis → SecReview Item: Review WebAppSec Secure coding checklist
Assignee | ||
Comment 2•12 years ago
|
||
The dev environment is now set up @ https://ship-it-dev.allizom.org/, and it's got the latest and greatest input validation. As far as I know, it addresses everything on the checklist at this point. I think Stefan was going to do the review?
Flags: needinfo?(sarentz)
Comment 3•12 years ago
|
||
Ben did you see https://bugzilla.mozilla.org/show_bug.cgi?id=812234#c6
Flags: needinfo?(sarentz)
Assignee | ||
Comment 4•12 years ago
|
||
(In reply to Stefan Arentz [:st3fan] from comment #3)
> Ben did you see https://bugzilla.mozilla.org/show_bug.cgi?id=812234#c6
Whoops, I lost track of that bug. Since that's tracked over there, is there anything else to do here?
Comment 5•12 years ago
|
||
No i don't think so.
Assignee | ||
Updated•12 years ago
|
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•12 years ago
|
Whiteboard: [kickoff] → [shipit]
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•