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

From OWASP
Jump to: navigation, search
Line 6: Line 6:
 
|-
 
|-
 
!  
 
!  
| 25-Nov || DC || 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-Oct || DC || 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 || DC || 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-Oct || DC || 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)
 +
|-
 +
| 09-Sep || MD || Bug || Access Violation when doing alt + f4 on splash screen || This was caused by the program not checking to see if the user wanted to continue or exit the program. 
 +
|-
 +
!
 +
| 07-Sep || MD || Upgrade || Update to .Net 2.0 || Upgraded to .NET 2.0 and got all of the compiler errors and most of the warnings cleared out.
 
|}
 
|}
  
 
-----
 
-----
 
back to [[ORG (Owasp Report Generator)]]
 
back to [[ORG (Owasp Report Generator)]]

Revision as of 07:39, 25 October 2006

This page contains the Change log for the ORG's version v0.85 (see ORG (Owasp Report Generator) - To Do for the current development focus)

ID Date By Type Issue Comment
25-Oct DC 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-Oct DC 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)
09-Sep MD Bug Access Violation when doing alt + f4 on splash screen This was caused by the program not checking to see if the user wanted to continue or exit the program.
07-Sep MD Upgrade Update to .Net 2.0 Upgraded to .NET 2.0 and got all of the compiler errors and most of the warnings cleared out.

back to ORG (Owasp Report Generator)