ssl connection issues

[Michael Blumenkrantz]

On Wed, 29 Sep 2010 16:36:19 +0200
Nikos Mavrogiannopoulos <nmav at gnutls.org> wrote:

> On 09/29/2010 04:22 PM, Michael Blumenkrantz wrote:
> 
> > This is a log of the handshake failure while attempting to connect to
> > verisign.com:443 using gnutls log level 2.  Additionally there is some
> > debug info from my code which is prefixed by DBG.  Let me know if there is
> > more information that I can provide. ERR:EcoreCon ecore_con_ssl.c:499
> > _ecore_con_ssl_server_init_gnutls() Error at
> > ecore_con_ssl.c:_ecore_con_ssl_server_init_gnutls:499! ERR:EcoreCon
> > ecore_con_ssl.c:52 _gnutls_print_errors() gnutls returned with error:
> > GNUTLS_E_FATAL_ALERT_RECEIVED - A TLS fatal alert has been received.
> > ERR:EcoreCon ecore_con_ssl.c:551 _ecore_con_ssl_server_init_gnutls() Also
> > received alert: Decrypt error ERR:EcoreCon ecore_con_ssl.c:554
> > _ecore_con_ssl_server_init_gnutls() last out: Finished ERR:EcoreCon
> > ecore_con_ssl.c:555 _ecore_con_ssl_server_init_gnutls() last in: Server
> > hello done |<2>| ASSERT: gnutls_record.c:262
> 
> I cannot see any problem here. The peer is sending a fatal alert because
> something he received was in error. Could it be an issue in your send
> function?
> 
> regards,
> Nikos
> 
> 
If that were the case, wouldn't it also fail when I have paused execution as I
described previously?  Additionally, the only function that is sending data on
that socket during that time is gnutls_handshake.

-- 
Mike Blumenkrantz
Zentific: Our boolean values are huge.