Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site cepu.UUCP
Path: utzoo!watmath!clyde!akgua!sdcsvax!bmcg!cepu!scw
From: scw@cepu.UUCP
Newsgroups: net.bugs.uucp,net.bugs.v7,net.bugs.2bsd
Subject: uuxqt bug (long command lines) v7 + others
Message-ID: <264@cepu.UUCP>
Date: Thu, 24-May-84 17:13:16 EDT
Article-I.D.: cepu.264
Posted: Thu May 24 17:13:16 1984
Date-Received: Thu, 31-May-84 19:39:45 EDT
Organization: VA Wadsworth Med. Center; LA CA
Lines: 37

There is a bug in uuxqt.c involving *LONG* mail paths, or long command lines;

    SYSTEMS Affected:
	v7, v7m, Ultrix-11(??), 2.8BSD, 2.9BSD(??); Anyone with v7 derived
	uucp (?probably);
    Symptoms:
	uuxqt (UUXQT) vanishes leaving LCK.XQT and  a 0 length core in
	/usr/spool/uucp or a real core file (depending on who actually invoked
	it and the permisions on /usr/lib/uuxqt) that has the C back frames
	scrogged.
    Cause:
	While parsing the command line the mail path (argument to rmail)
	tramples on the stack. Actually it gets copied to a char[] that is
	too short.
    Repeat by:
	Send a message with more that MAXFULLNAME (uucp.h) characters in the
	path. A system with this problem will be unable to pass the message on.
	  -or-
	Generate a bogus X.system1234 file with a long (>MAXFULLNAME) X line
	in it.  then manually invoke uuxqt with -x4 to watch it die with a
	segementation violation.
    Fix:
	change line ~~40 from:
	char xcmd[100];
	to:
	char xcmd[BUFSIZ];

	Change line ~~50 from:
	char *cmdp, prm[MAXFULLLNAME],*ptr;
	to:
	char *cmdp, prm[BUFSIZ],*ptr;

	This fix will allow command lines to be up to 511 char long.
-- 
Stephen C. Woods (VA Wadsworth Med Ctr./UCLA Dept. of Neurology)
uucp:	{ {ihnp4, uiucdcs}!bradley, hao, trwrb, sdcsvax!bmcg}!cepu!scw
ARPA: cepu!scw@ucla-locus       location: N 34 06'37" W 118 25'43"