Joe
At 00:00 08/03/2003, Johan Brunius wrote:
I wonder , when yoi sent the cert from unix to windows, did you use bin or ascii?
[EMAIL PROTECTED] writes: >On Fri, Feb 28, 2003 at 03:51:21PM +0000, Joe Dauncey wrote: > >> I can create users on the server and connect remotely with NessusWX >using >> passwords. >> >> However, when I try and do it with certificates I get an error from >> NessusWX - >> 'Invalid username or password supplied' > >From my testing, NessusWX doesn't seem to care about the line endings of >the certificate file; ie, it works fine with either the DOS or unix line >endings. Also, if I use a totally bogus certificate (like >C:\AUTOEXEC.BAT), NessusWX installs it fine but complains with the error >"Cannot load client certificate" whenever I try to use it to connect. I >also get the same error if I don't select a client certificate while >trying to authenticate with a certificate. > >The only way I can reproduce your error has been to not use a >certificate at all and instead authenticate by password. And then, only >if the password stored by the Nessus daemon is missing or different from >what I enter and the nessusd.conf doesn't have force_pubkey_auth set to >yes. > >So, how are you authenticating with NessusWX? In the Connect (not Quick >Connect) dialog box, there's a set of radio buttons in the lower right >quadrant to select between authentication by password and by >certificate. > > >George >--
Joe Dauncey PGP Key ID: 0xEAA034D4
*** I am not a lawyer and my opinions are my own ***
