[2856] in Kerberos-V5-bugs
krb5-appl/527: Size of pibuf[] in krlogind.c too small
daemon@ATHENA.MIT.EDU (hmkash@ARL.MIL)
Thu Jan 15 16:54:17 1998
Resent-From: gnats@rt-11.MIT.EDU (GNATS Management)
Resent-To: krb5-unassigned@RT-11.MIT.EDU
Resent-Reply-To: krb5-bugs@MIT.EDU, hmkash@ARL.MIL
Date: Thu, 15 Jan 98 16:45:41 EST
From: hmkash@ARL.MIL
Reply-To: hmkash@ARL.MIL
To: krb5-bugs@MIT.EDU
Cc: jamesf@ARL.MIL, kenh@cmf.nrl.navy.mil
>Number: 527
>Category: krb5-appl
>Synopsis: Size of pibuf[] in krlogind.c too small
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: krb5-unassigned
>State: open
>Class: sw-bug
>Submitter-Id: unknown
>Arrival-Date: Thu Jan 15 16:54:00 EST 1998
>Last-Modified:
>Originator: James Fielding, Howard Kash
>Organization:
U.S. Army Research Lab
>Release: krb5-1.0.4
>Environment:
System: IRIX64 raven 6.2 03131016 IP19
Pine 3.95
>Description:
After upgrading from krb5b3 to krb5-1.0.4 the pine email reader would
only display partial screen updates. Using the IRIX par utility, it
was found that pine was displaying the screen with one write() call.
The number of characters in the write() would depend on the screen
size but was usually greater than 1024. Looking through krlogind.c
it was found that pipuf[] and fibuf[] were both of size 1024. In
the krb5b3 source, pibuf was allocated as pibuf[16*1024+1] and
fibuf as fibuf[1024]. Changing pibuf[] in the krb5-1.0.4 source
fixed the problem with pine. A Solaris 2.5.1 host did not have
the problems with pine prior to the modification. Using telnet
into the IRIX 6.2 host also did not have the problem.
>How-To-Repeat:
Rlogin to an IRIX 6.x host with an 80x24 size screen or larger and run
pine.
>Fix:
Increase size of pibuf[] in krlogind.c.
>Audit-Trail:
>Unformatted:
