Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Nessus-Users
[Top] [All Lists]

Re: Certificates renewal

Subject: Re: Certificates renewal
Date: Thu, 24 Aug 2006 07:07:31 -0400
On Thu, Aug 24, 2006 at 11:12:28AM +0200, Patrice.Arnal@alcatel.fr wrote:

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

"Given" comes from the certificate passed by the client during the connection; "Last tried" reports what nessusd found in the dname file for the connecting user.


Where is the mistake ?

The issue likely arises because you have an older version of OpenSSL. Starting somewhere between versions 0.9.6h and 0.9.7b (I'm not sure exactly), OpenSSL changed its output format to use "emailAddress=" rather than "Email=". The nessus-mkcert-client script hardcodes emailAddress.


So, to solve your issue, edit the dname file for the user and change "emailAddress=" to "Email="; the change will become effectively immediately w/o needing to restart nessusd. And if you do someday upgrade OpenSSL, keep in mind you will need to make the reverse change or you'll have a similar issue for all your Nessus users.

George
--
theall@tenablesecurity.com
_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus

<Prev in Thread] Current Thread [Next in Thread>