View Issue Details

IDProjectCategoryView StatusLast Update
0002851SUMoBugpublic2019-07-28 12:30
Reporterattackcenter Assigned ToKyle_Katarn  
PrioritynormalSeveritymajorReproducibilityhave not tried
Status confirmedResolutionopen 
PlatformPCOSWindows OS VersionWindows 8.1
Product Version3.13.8 
Target Version5.12.x 
Summary0002851: Update Permanently Ignored When Removed From Ignore List
DescriptionI put an update in the ignore list and it was successful. I chose to remove the update from the ignore list and now the update is missing from the software list (its been removed or permanently ignored).

Kyle Proposal : SUMo should call fora re-scan after ignore list removal or reset.
Steps To ReproducePut a software update in ignore list. Remove software from remove list and its permanently gone.
Additional InformationRemoving an item from the ignore list should make the software update show again and not remove it all together.
TagsNo tags attached.


related to 0004761 acknowledgedKyle_Katarn Programs removed from ignore list remain ignored 



2015-05-20 20:45

administrator   ~0001873

Does a "scan" then make it re-appear ?


2017-07-15 00:43

administrator   ~0002642

Same feature as now in DUMo 2.7+


2019-07-27 22:11

reporter   ~0003634

I can confirm that initiating a scan action after a removal resp. clearing of ignore list will make those ignored entries reappear in SUMo main report list, at least with SUMo version 5.9.4. So although the impression of permanent removal of any list (ignore list and report list) is right, it isn't permanently as it would then not reappear after a rescan.

As moving an entry of the SUMo main report list to its ignore list updates both lists immediately, the same expectation is raised for the other direction. So for small report lists, an automatic rescan would be fine, considering report lists of up to 100 entries as small. For advanced settings for advanced users, such a limit might make sense to become configurable. For cases with larger report lists, SUMo shall propose and recommend a re-scan similar to the case after it detects of being updated itself like SUMo auto-update of itself.


2019-07-28 12:30

administrator   ~0003639

Yes but since file path is not in the Ignore list, SUMo is not able to make it re-appear without a scan.
I'll propose a re-scan to user when the Ignore list is modified.

Issue History

Date Modified Username Field Change
2015-05-20 02:31 attackcenter New Issue
2015-05-20 20:45 Kyle_Katarn Note Added: 0001873
2015-05-20 20:45 Kyle_Katarn Assigned To => Kyle_Katarn
2015-05-20 20:45 Kyle_Katarn Status new => feedback
2015-12-16 20:50 Kyle_Katarn Target Version => 4.2.5
2015-12-16 20:50 Kyle_Katarn Description Updated
2015-12-16 20:50 Kyle_Katarn Status feedback => confirmed
2015-12-21 23:23 Kyle_Katarn Target Version 4.2.5 => 4.3.x
2015-12-22 15:31 Kyle_Katarn Target Version 4.3.x => 4.2.6
2015-12-28 11:57 Kyle_Katarn Target Version 4.2.6 => 4.2.7
2016-01-07 21:11 Kyle_Katarn Target Version 4.2.7 => 4.3
2016-01-17 14:51 Kyle_Katarn Target Version 4.3 => 4.3.x
2016-05-06 18:01 Kyle_Katarn Target Version 4.3.x => Short term
2017-07-15 00:43 Kyle_Katarn Target Version Short term => 5.3.1
2017-07-15 00:43 Kyle_Katarn Note Added: 0002642
2017-07-24 20:46 Kyle_Katarn Target Version 5.3.1 => 5.12.x
2018-03-17 11:39 Kyle_Katarn Relationship added related to 0004761
2019-07-27 22:11 wolf Note Added: 0003634
2019-07-28 12:30 Kyle_Katarn Note Added: 0003639