* Cyril Bouthors: >> This sounds like an interesting application. If you find the output >> format too difficult to parse, I can add yet another one to >> accommodate your needs. > > The most important thing is the return code. After a quick overview, > it seems that debsecan is inconditionnally returning 0. Could you > please change that in order to return true (0) if no package is known > to be vulnerable and false (1) otherwise?
What about hard errors, such as a wrong command line argument, or a problem downloading the vulnerability information? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
