I was experiencing problems with updating nessus with 2.2.3. I updated to 2.2.5 and the problem went away. It appears that the SSL bug fixed in 2.2.4 did affect updating
On 9/6/05 7:21 AM, "Nordwall, Douglas J" <[EMAIL PROTECTED]> wrote:
Is this mentioned in the changelog somewhere? I notice a fix in 2.2.4 that mentioned SSL reads, but since that was in libnessus, I figured that it dealt with interactions with https when scanning, not with nessus-fetch. There is a mention of fixed proxy support for nessus-fetch, but we’re seeing such an error here (as well as another guy on the list) and we’re not using a proxy.
On 9/4/05 11:36 AM, "George A. Theall" <[EMAIL PROTECTED]> wrote:
On Sat, Sep 03, 2005 at 01:15:07AM -0300, Hugo Doria wrote:
> I just installed nessus on my Ubuntu, but when i try
> to register i get this error:
>
> $ sudo nessus-fetch --register
> EF20-2B17-1439-D35F-302A
> Unknown error while decoding HTTP response (http error
> code = -1208542450)
Which Nessus version are you using? If 2.2.3 or lower, upgrade - there
were several issues with those versions involving nessus-fetch and SSL
support.
> If i try again it says:
> The provided activation code
> (EF20-2B17-1439-D35F-302A) has already been used.
You will need to re-register once you fix the first problem.
> PS: My english is not so good...sorry
Nao se preocupe -- es melhor que meu portugues. :-)
George
--
[EMAIL PROTECTED]
_______________________________________________
Nessus mailing list
[email protected]
http://mail.nessus.org/mailman/listinfo/nessus
_______________________________________________
Nessus mailing list
[email protected]
http://mail.nessus.org/mailman/listinfo/nessus
_______________________________________________ Nessus mailing list [email protected] http://mail.nessus.org/mailman/listinfo/nessus
