Difference between revisions of "ORG (Owasp Report Generator) - Change Log"

From OWASP
Jump to: navigation, search
 
Line 1: Line 1:
 
This page contains the Change log for the ORG's version v0.85  
 
This page contains the Change log for the ORG's version v0.85  
 
'''Priority Medium'''
 
  
 
{|class="wikitable"  
 
{|class="wikitable"  
 
|-
 
|-
|
+
! ID !! Date !! !! Issue !! Comment  
! Date !! !! ID !! Type !! Task !! Comment !!
+
 
|-
 
|-
 
!  
 
!  
| 25-Nov || || Bug || When a project is loaded in the findings tab the list of available findings was not cleared || this showed it self in new projects which had no targets (and if the user had the findings tab open)
+
| 25-Nov || Bug || Race condition on new altova component locks the directory so that it cannot be used twice || The issue seems to be related to a directory handle that exists on the ORG process (created by the Altova component) that prevents the directory from being completely deleted and means that when the same finding is opened again an error is thrown. The current solution is based on saving the temporary files in a folder named after a unique GUID. This solves the problem in the short term. but we still need to figure out how to close the handle properly (since at the moment not all directories are properly deleted)
 +
|-
 +
!
 +
| 25-Nov || Bug || When a project is loaded in the findings tab the list of available findings was not cleared || this showed it self in new projects which had no targets (and if the user had the findings tab open)
 
|}
 
|}

Revision as of 07:06, 25 October 2006

This page contains the Change log for the ORG's version v0.85

ID Date Issue Comment
25-Nov Bug Race condition on new altova component locks the directory so that it cannot be used twice The issue seems to be related to a directory handle that exists on the ORG process (created by the Altova component) that prevents the directory from being completely deleted and means that when the same finding is opened again an error is thrown. The current solution is based on saving the temporary files in a folder named after a unique GUID. This solves the problem in the short term. but we still need to figure out how to close the handle properly (since at the moment not all directories are properly deleted)
25-Nov Bug When a project is loaded in the findings tab the list of available findings was not cleared this showed it self in new projects which had no targets (and if the user had the findings tab open)