Failed to receive data: A TLS packet with unexpected length was received.

Started by dario_vet, November 06, 2013, 03:58:43 PM

Previous topic - Next topic

dario_vet

Ciao a tutti,

sto attualmente rannando in una macchina virtuale l'ultima versione di backbox 3.09 a 64bit. una volta installato, aggiornato il sistema e fatto pure update dei tool, provo a lanciare open vas, dal menu selezione restart, poi apro la finestra di firefox che mi chiede di dare conferma al certificato, dopo che ho fatto aggiungi eccezzione la firefox basta dice che non si puo piu collegare, ed appare il messaggio che ho messo come titolo:

Failed to receive data: A TLS packet with unexpected length was received.

quanlcuno mi sa aiutare?


Hi all,

I'm currently in using a virtual machine with the latest version of backbox 3.09 64bit. once installed, I update the system and the tools, I try to launch open vas from the menu ( I usually choose restart), then I open the firefox window that asks me to confirm the certificate, after I add the exception firefox just says that you can not connect more, and the message that I put as a title:

Failed to receive data: A TLS packet with unexpected length was received.

Can someone helps me?

ostendali

did you even checked or did any search before posting your simple question here?

I doubt it because all I did is copy and paste of your error on google and look what I got in the first place:
http://comments.gmane.org/gmane.comp.security.openvas.users/4815

dario_vet

I'm searching about one week to solve my problem befoure create this post and try to reinstall the machines, update install it in a machines and not on virtualmachines, I have solved something, then I rum openvas-check-setup
and I have this output:

http://pastebin.com/69eMgkVV

I think that isn't normal that I have to start openvas from terminal, but I do only what openvas-check-setup tell me.
My problem is that openvas-check-setup teel me that my openva6 installation seems ok, but when I open the firefox https://localhost:9392/ I
correctly accept the certificate but when it's time to continue he teels me Firefox can't establish a connection to the server at localhost:9392.
when a few seconds befouse it let me to accept the certificate.

P.S. Use pastebin for terminal outputs. Thanks !

b4d_bl0ck

Hi dario_vet,
If you searched on the forum you'd have seen other users get same behaviour, i.e. https://forum.backbox.org/software-support/openvas-does-not-working-on-backbox-3-09-i386

We are looking how to fix this, or at least to know if we can do something or it's an upstream issue.
Stay tuned...

Bye.
bool secure = check_paranoia() ? true : false;

ostendali

Quote from: dario_vet on November 11, 2013, 09:18:48 AM
I'm searching about one week to solve my problem befoure create this post and try to reinstall the machines, update install it in a machines and not on virtualmachines, I have solved something, then I rum openvas-check-setup
and I have this output:

http://pastebin.com/69eMgkVV

I think that isn't normal that I have to start openvas from terminal, but I do only what openvas-check-setup tell me.
My problem is that openvas-check-setup teel me that my openva6 installation seems ok, but when I open the firefox https://localhost:9392/ I
correctly accept the certificate but when it's time to continue he teels me Firefox can't establish a connection to the server at localhost:9392.
when a few seconds befouse it let me to accept the certificate.

P.S. Use pastebin for terminal outputs. Thanks !
yes it is normal to start manually the service for openvas from the terminal.
if you want it start in auto all you need to do is to put the script in initd to start during the boot.

however, I am not using openvas over ssl cert, just use http protocol and it is working perfectly.

It is working also over ssl but there is a bit of work behind to setup and it is not for newbies....

said that, i couldn't get your point, I mean, by checking the pastebin I see no issue, so what is your problem exactly?

sinflooddotnet

I had the exact same issue with 3.09 after a clean install + apt-get upgrade, but before syncing NVT updates. However, when retrying I was able to login to GSAD today.

The last time I only saw the notification in the shell after issuing 'sudo openvas-services stop'.

The startup commands I always use
$ sudo openvasmd --rebuild
$ sudo openvas-services start

and if it doesn't work
$ sudo openvas-services stop

$ sudo openvasmd -a 127.0.0.1 -p 9390
$ sudo openvasad -a 127.0.0.1 -p 9393
$ sudo gsad --http-only --listen=127.0.0.1 -p 9392

good luck