>It would save the community from re-doing the same analysis I vaguely disagree. Secure software is not a well defined state so security analysis is not a proc

>It would save the community from re-doing the same analysis I vaguely disagree. Secure software is not a well defined state so security analysis is not a process with an end condition, so theoretically, you can never stop looking. But documenting failed attempts and methods is still worthy because duplicate work may still teach a lessons.