--- Begin Message ---
Subject: |
Bug#210358: gnutls-bin: client fails out on supposedly non-fatal errors (regression) |
Date: |
Wed, 10 Sep 2003 18:55:27 -0500 |
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.
-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux duffbox 2.4.22-rc1-dis7 #5 Sun Sep 7 09:51:13 CDT 2003 i686
Locale: LANG=C, LC_CTYPE=C
Versions of packages gnutls-bin depends on:
ii libc6 2.3.2-6 GNU C Library: Shared libraries an
ii libgcrypt1 1.1.12-3 LGPL Crypto library - runtime libr
ii libgnutls7 0.8.9-2 GNU TLS library - runtime library
ii liblzo1 1.08-1 A real-time data compression libra
ii libopencdk4 1:0.4.2-3 Open Crypto Development Kit (OpenC
ii libpopt0 1.7-2 lib for parsing cmdline parameters
ii libtasn1-0 0.1.2-1 Manage ASN.1 structures (runtime)
ii zlib1g 1:1.1.4-14 compression library - runtime
-- no debconf information
--- End Message ---