That blows.  In previous versions I was able to use our proxy servers to get
out and get the plugins updated. So is this a problem that others are
experiencing as well? 


Matthew Puckett
Sr. Systems Engineer
Wintel Operational Services: Systems Management
HCA Information Technology & Services

2555 Park Plaza
Nashville, TN 37023
t: 615-344-6686
f: 615-344-7995
e: [EMAIL PROTECTED]
w: www.hcahealthcare.com

This email and any files transmitted with it may contain PRIVILEGED or
CONFIDENTIAL information and may be read or used only by the intended
recipient. If you are not the intended recipient of the email or any of its
attachments, please be advised that you have received this email in error
and that any use, dissemination, distribution, forwarding, printing, or
copying of this email or any attached files is strictly prohibited. If you
have received this email in error, please immediately purge it and all
attachments and notify the sender by reply email or contact the sender at
the number listed.

-----Original Message-----
From: Tim Slighter [mailto:[EMAIL PROTECTED] 
Sent: Monday, March 14, 2005 11:14 AM
To: Puckett Matthew
Cc: '[email protected]'
Subject: Re: Updating Plugins

In order to get that process to work, a firewall rule was implemented that
allows HTTPS to 66.240.11.107.  You might also want to let all the other
security folks know that when this does work, it will fire IDS signatures
for IIS-SSL-MS04-011 (Attempts to exploit know vulnerabilities within
Microsoft's SSL libraries).  If you are using a proxy then at this point,
there is no conclusive evidence that nessus-fetch works, even with the
nessus-fetch.rc file in place. 

Puckett Matthew wrote:

>Greetings!
>
>I have a Nessus 2.2.3 installation on a Redhat 8.0 platform.  Install 
>of Nessus went fine but I am unable to get neither the 
>nessus-update-plugins or nessus-fetch commands to work.  I receive the
following:
>
># nessus-fetch --check
>nessus-fetch is not configured to receive a direct plugin feed
>[EMAIL PROTECTED] bin]# nessus-fetch --register 
>7275-c782-6a3e-0b72-382e [15542] plug_set_key:internal_send(0)['3 
>/tmp/ConnectTimeout/TCP/443=1;
>']: Socket operation on non-socket
>could not connect to plugins.nessus.org - Socket operation on 
>non-socket
>
>I am not by any means a Linux wizard or even a newbie when it comes to 
>Unix clones.  Any assistance is much appreciated.  Oh, P.S.  I have 
>installed earlier brands of Nessus with no issues in the plugin updates
area before.
>This is a new one to me.
>
>Thanks,
>
>Matthew Puckett
>Sr. Systems Engineer
>Wintel Operational Services: Systems Management HCA Information 
>Technology & Services
>
>2555 Park Plaza
>Nashville, TN 37023
>t: 615-344-6686
>f: 615-344-7995
>e: [EMAIL PROTECTED]
>w: www.hcahealthcare.com <www.hcahealthcare.com>
>
>This email and any files transmitted with it may contain PRIVILEGED or 
>CONFIDENTIAL information and may be read or used only by the intended 
>recipient. If you are not the intended recipient of the email or any of 
>its attachments, please be advised that you have received this email in 
>error and that any use, dissemination, distribution, forwarding, 
>printing, or copying of this email or any attached files is strictly 
>prohibited. If you have received this email in error, please 
>immediately purge it and all attachments and notify the sender by reply 
>email or contact the sender at the number listed.
>
>
>  
>
>-----------------------------------------------------------------------
>-
>
>_______________________________________________
>Nessus mailing list
>[email protected]
>http://mail.nessus.org/mailman/listinfo/nessus
>

--
Tim Slighter
(970) 295-5565
[EMAIL PROTECTED]
Key fingerprint = A1DF A61C 0C25 E2C2 6D7F  559A 9A23 9538 A6A0 D7D3
_______________________________________________
Nessus mailing list
[email protected]
http://mail.nessus.org/mailman/listinfo/nessus

Reply via email to