I add myself to this question... Id like to know as well what is the reason for the command-line interface to be so far behind in functionalities compared to the GUI... usually its the opposite. Is it because of a "windows" approach, where the interface seems to be as (more?) important as the real application?
rgds Cristobal Jay wrote: > > I normally generate a .nessusrc file with the GTK GUI, then use the > command-line client for all my scans. The GUI-created .nessusrc file seems > to put a static list of the plugins at the end of the file (I assume this > is the list pulled from the server) with either a "yes" or "no" after each > - indicating which plugins to use for a test. > > If the plugins on the server are updated almost daily, how do the new > plugins get into the client's .nessusrc file? Do I have to manually create > a .nessusrc file *every day* with the GUI? That seems awfully troublesome. > There must be a better way to do this. Any thoughts? How are other people > doing this? > > Instead of listing *every* plugin statically in the .nessusrc file, can > they be specified by families instead? How about wildcards (maybe putting > "*" in the .nessusrc file to indicate "use all possible plugins")? > > Thanks! > > -- > ~Jay -- Cristobal Soto Y. ICSA.cl - The e-risk security company - http://www.icsa.cl
