| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] |
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0001691 | SUMo | Bug | public | 2012-08-13 14:11 | 2012-08-13 22:31 |
|
| Reporter | bytehead | |
| Assigned To | Kyle_Katarn | |
| Priority | high | Severity | tweak | Reproducibility | always |
| Status | resolved | Resolution | fixed | |
| Platform | | OS | | OS Version | |
| Product Version | 3.4.1 | |
| Target Version | | Fixed in Version | | |
|
| Summary | 0001691: Buggy JRE update info still present on the server |
| Description | Since issue 0001667 was recently resolved in SUMo client v3.4.1.168, some incorrect JRE data still present on the server DB and probably keeps being reported again from older unfixed clients (see attach.)
This needs to be cleaned up and stopped from reappearing, e.g.:
a) wrong entries should be erased or server DB should be reset;
b) put some rules in place to either filter out inexistant JRE versions 10.* (from any client)
OR
only accept new data from fixed SUMo clients (3.4.1.168+) if protocol allows to distinguish them. |
| Tags | No tags attached. |
|
| Attached Files |  JRE updates uncleaned.png [^] (64,761 bytes) 2012-08-13 14:11
 |
|
Relationships 
Relationships 