[gnutls-dev] [charlesduffy at isgenesis.com: Bug#210358: gnutls-bin: client fails out on supposedly non-fatal errors (regression)]
nmav at gnutls.org
Thu Sep 11 15:08:02 CEST 2003
On Thu, Sep 11, 2003 at 10:00:35AM +0200, Ivo Timmermans wrote:
I've just fixed that in the 0.9.x branch.
> `Contrariwise,' continued Tweedledee, `if it was so, it might be; and
> if it were so, it would be; but as it isn't, it ain't. That's logic.'
> - Lewis Carroll, `Through the Looking-Glass'
> From: Charles Duffy <charlesduffy at isgenesis.com>
> To: Debian Bug Tracking System <submit at bugs.debian.org>
> Subject: Bug#210358: gnutls-bin: client fails out on supposedly non-fatal errors (regression)
> Reply-To: Charles Duffy <charlesduffy at isgenesis.com>,
> 210358 at bugs.debian.org
> X-Mailer: Ximian Evolution 1.4.4
> Date: Wed, 10 Sep 2003 18:55:27 -0500
> X-Spam-Status: No, hits=-1.9 required=5.0
> Subject: gnutls-bin: client fails out on supposedly non-fatal errors (regression)
> Package: gnutls-bin
> Version: 0.8.9-2
> Severity: normal
> The gnutls-cli from 0.8.9-2 doesn't handle incoming alerts except during the
> handshake process -- unlike the 0.3.5 release which, despite its other
> failings, has proper error handling for said case.
> Most particularly, cli.c includes no gnutls_error_is_fatal call (in "simple
> client mode" after the handshake) to check the fatality of any negative return
> values from gnutls_read; rather, all errors are assumed to be fatal.
> Correspondingly, there is no support except during the handshake for printing
> alerts received to the user -- which also existed in 0.3.5 code.
> This is additionally an issue for developers writing code based off the
> included sample client, who may be lead to believe that all error codes are
> necessarily fatal at this point.
More information about the Gnutls-devel