Subject: Re: Termcap in $TERMCAP broken?
To: None <email@example.com>
From: Christos Zoulas <firstname.lastname@example.org>
Date: 02/15/2002 16:58:53
In article <200202150827.DAA05096@Sparkle.Rodents.Montreal.QC.CA>,
der Mouse <mouse@Rodents.Montreal.QC.CA> wrote:
>I have a guest login on a 1.5.3_ALPHA machine (according to uname; vax,
>if it matters).
>On my 1.4T machines, even my VAX, if I put a termcap entry in $TERMCAP
>and put that entry's name in $TERM, everything works. On the
>1.5.3_ALPHA machine, it works only partially; one of my own programs
>that uses -ltermcap works fine, but top goes into its dumb-terminal
>mode, printing one "update" and exiting.
>Setting $TERMCAP to the name of a file which contains the termcap entry
>(among others) works fine.
>Now, this may prove non-reproducible, in which case it's probably some
>quirk of the machine I have the guest login on. But if it's
>reproducible, it seems to me that a useful bit of functionality has
>been lost somewhere along the line....
suid/sgid programs should and do ignore env variables to prevent buffer
overflows. top was still setgid at 1.5.3 IIRC.