I think I missed something obvious, but now I am completly puzzled.
On my scanner, the user secadm was allowed to connect via certificate.
Everything was OK till yesterday : the key /certicates were send by the
NessusClient and granted by the server
This morning : SSH error !
Some investigations proved that the client certificate expired this night.
As I did not found the procedure to renew the certificate, I deleted the
user secadm ( with nessus-rmuser ) and I recreated
it via nessus-mkcert-client ( answered yes to the registration question )
I copied the new keys/certificates to the right place for NessusClient and
now I get "Login error"
The nessusd.message of the server says :
check_user: Bad DN for user secadm Given DN=/C=FR/ST=Ile de
France/L=Massy/O=Alcanet/OU=DC_SECURITY/CN=secadm/Email=patrice.arnal@alcatel.fr
Last tried DN=/C=FR/ST=Ile de
France/L=Massy/O=Alcanet/OU=DC_SECURITY/CN=secadm/emailAddress=patrice.arnal@alcatel.fr
Which is exactly what is in the .../secadm/auth/dname
Nessus Server 2.2.8 on Suse Linux Nessus Client NessusClientBeta for
windows
Where is the mistake ?
Thank you for any help
Cordialement / Mit freundlichen GrÃÃen / Best regards,
_____________________________________________
Patrice Arnal
ISS - DataCenter â E&S
Alcatel ICT Services
1rte Dr A.Schweitzer - 67408 - ILLKIRCH - FRANCE
Phone : +33 (0) 3 90 67 74 22 / 2187 74 22
Fax : +33 (0) 3 90 67 72 07
Mobile: +33 (0) 6 06 07 67 68 08
Mailto: patrice.arnal@alcatel.fr
_____________________________________________
_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus
