Hi,
I started to fiddle around with the Debian package for NessusClient.
Found out that with nessus-mkrand we have a similar problem as we
we had for nessus-mkcert.
I propose the same solution (rename nessus-mkdrand to nessusclient-mkrand).
Any concerns or comments?
Best
Jan
--
Jan-Oliver Wagner: www.intevation.de/~jan | GISpatcher: www.gispatcher.de
Kolab Konsortium : www.kolab-konsortium.de | Thuban : thuban.intevation.org
Intevation GmbH : www.intevation.de | Kolab : www.kolab.org
FreeGIS : www.freegis.org | GAV : www.grass-verein.de
_______________________________________________
Nessus-devel mailing list
Nessus-devel@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus-devel
I started to fiddle around with the Debian package for NessusClient.
Found out that with nessus-mkrand we have a similar problem as we
we had for nessus-mkcert.
I propose the same solution (rename nessus-mkdrand to nessusclient-mkrand).
Any concerns or comments?
Best
Jan
--
Jan-Oliver Wagner: www.intevation.de/~jan | GISpatcher: www.gispatcher.de
Kolab Konsortium : www.kolab-konsortium.de | Thuban : thuban.intevation.org
Intevation GmbH : www.intevation.de | Kolab : www.kolab.org
FreeGIS : www.freegis.org | GAV : www.grass-verein.de
_______________________________________________
Nessus-devel mailing list
Nessus-devel@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus-devel