PROBLEM: (MCPMC0L3C QAR 50410) (Patch ID: OSF415-400144) ******** Problem - If you ftp to an IBM MVS system using the IP address, the IBM system will refuse the connection. This problem can be encountered on any system that validates TOS (Type Of Service) requests if the file /etc/iptos is not used on the client. How to recognize this problem: If you attempt to ftp to any system that validates TOS requests, you may see the following: ftp> open Connected to 220-FTPSERV1 IBM MVS V3R1 at SAC1, 12:08:49 on 1996/12/11 421 Service not available, remote server has closed connection but it may work if you give the hostname of the system instead of the ip address. If you were running tcpdump, tracing the connection, you would see 12:26:20.076128 irvingirving.cxo.dec.com.2296 > mvssac1.rac.mci.com.ftp: S 1419648000:1419648000(0) win 32768 (DF) 12:26:20.176656 mvssac1.rac.mci.com.ftp > irvingirving.cxo.dec.com.2296: S 447244900:447244900(0) ack 1419648001 win 65535 12:26:20.176656 irvingirving.cxo.dec.com.2296 > mvssac1.rac.mci.com.ftp: . ack 1 win 33580 (DF) 12:26:20.274256 mvssac1.rac.mci.com.ftp > irvingirving.cxo.dec.com.2296: P 1:60(59) ack 1 win 65535 12:26:20.366000 irvingirving.cxo.dec.com.2296 > mvssac1.rac.mci.com.ftp: . ack 60 win 33580 (DF) [tos 0xa6] <<<<<----NOTICE THIS!!! 12:26:20.461648 mvssac1.rac.mci.com.ftp > irvingirving.cxo.dec.com.2296: R 447244960:447244960(0) win 0 In the above trace, the connection is rejected because the TOS (Type Of Service) field contains an invalid value. This problem can be avoided by using a /etc/iptos file as noted in the man page. However, the TOS field should never have this invalid value and that is the reason for the patch. PROBLEM: (CLD SSRT0505U) (Patch ID: OSF415-400396) ******** A potential security vulnerability has been discovered, where under certain circumstances, system integrity may be compromised. This may be in the form of improper file or privilege management. Digital has corrected this potential vulnerability. PROBLEM: (FNO100131, QAR 43995) (Patch ID: OSF415-400150) ******** This patch fixes a problem where telnet dumps core if the USER environment variable is the last variable in the enviroment list. PROBLEM: (MCPM11J3X/MCPM6046A) (Patch ID: OSF415-405161) ******** This patch fixes hang conditions experienced with the following networking commands and utilities rsh(1) telnet(1) ftp(1) rdate(8) ping(8) and yppush(8). This problem is usually seen when these utilities are called from scripts. The commands appear to be "hung" but in fact are waiting for an event. A typical stack trace would look as follows: thread_block() mpsleep() event_wait() do_scan() select() syscall() _Xsyscall() Another problem this patch fixes is rsh not catching SIGPIPE. When SIGPIPE was received, rsh would immediately exit without cleaning up. Since rsh is implemented with a parent and its forked child process, the child was not getting cleaned up when the parent couldn't invoke it's normal exit code. PROBLEM: (QAR 59268) (Patch ID: OSF415-405188) ******** This patch corrects a regression problem with the rsh(1) command. PROBLEM: (QAR 61090) (Patch ID: OSF415-405279) ******** This patch corrects a problem with rsh(1) that is most visible with long-distance (slow) links where a packet might get dropped.