On Thu Aug 12 2004 at 18:29, Thomas Reinke wrote: > It would be really nice, given that we know that we are duplicating > functionality, and duplicating operations that take a LONG time to run, > if there was some automatic way making the transition to the NASL based > equivalents of .NES scripts a seamless one.
This has been fixed. Violently :) The NES plugins refused to run if NASL_LEVEL is high enough > to the daemon. The problem is that these preference descriptions are > subject to change (and have changed). Which forces every client > that preconfigures preferences to change everytime a preference string > is changed. This does not happen often. We try to keep the number of preferences low. > Another problem is anyone trying to build a client that operates > in a different language. In that case, the preference descriptions > cannot be displayed to a user directly, and must be mapped to > the corresponding foreign language counterpart. But this mapping > will not be reliable if the basis for a mapping is a descriptive > text string that keeps changing. If the string is new, display it in English. I see no other way. -- [EMAIL PROTECTED] http://arboi.da.ru FAQNOPI de fr.comp.securite http://faqnopi.da.ru/ NASL2 reference manual http://michel.arboi.free.fr/nasl2ref/ _______________________________________________ Nessus mailing list [EMAIL PROTECTED] http://mail.nessus.org/mailman/listinfo/nessus
