**************************** ECO SUMMARY INFORMATION **************************** Release Date: 20-APR-2004 Kit Name: DEC-AXPVMS-TCPIPJA_ECO-V0504-151-4.PCSI Kit Applies To: OpenVMS ALPHA V7.3-2, V7.3-1 Approximate Kit Size: 64512 blocks Installation Rating: INSTALL_2 Superseded Kits: None. Mandatory Kit Dependencies: None. Optional Kit Dependencies: None. DEC-AXPVMS-TCPIPJA_ECO-V0504-151-4.PCSI-DCX_AXPEXE Checksum: 2768886315 ======================================================================= Hewlett-Packard OpenVMS ECO Cover Letter ======================================================================= ECO NUMBER: TCPIPJAALP_E01A54 PRODUCT: HP TCP/IP Services/Japanese for OpenVMS Alpha V5.4 UPDATE PRODUCT: HP TCP/IP Services/Japanese for OpenVMS Alpha V5.4 1 KIT NAME: DEC-AXPVMS-TCPIPJA_ECO-V0504-151-4 2 KIT DESCRIPTION: 2.1 Installation Rating: INSTALL_2 : This installation rating, based upon current CLD information, is provided to serve as a guide to which customers should apply this remedial kit. (Reference attached Disclaimer of Warranty and Limitation of Liability Statement) _____________________________ Note _____________________________ This ECO kit can be applied only to Japanese language variant of TCP/IP Services for OpenVMS V5.4. _________________________________________________________________ 2.2 Reboot Requirement: A reboot is necessary after installation of this kit. 2.3 Version(s) of OpenVMS to which this kit may be applied: OpenVMS Alpha V7.3-2, V7.3-1 2.4 New functionality or new hardware support provided: No. 3 KITS SUPERSEDED BY THIS KIT: - None. 4 KIT DEPENDENCIES: 4.1 The following remedial kit(s), or later, must be installed BEFORE installation of this, or any required kit: - None 4.2 In order to receive all the corrections listed in this kit, the following remedial kits, or later, should also be installed: - None. 5 FILES PATCHED OR REPLACED: File Name --------- [SYS$LDR]TCPIP$BGDRIVER.EXE [SYS$LDR]TCPIP$BGDRIVER_PERF.EXE [SYS$LDR]TCPIP$INETDRIVER.EXE [SYS$LDR]TCPIP$INTERNET_SERVICES.EXE [SYS$LDR]TCPIP$INTERNET_SERVICES_PERF.EXE [SYS$LDR]TCPIP$NFS_SERVICES.EXE [SYS$LDR]TCPIP$PWIPDRIVER.EXE [SYS$LDR]TCPIP$TNDRIVER.EXE [SYS$LDR]TCPIP$TNDRIVER_PERF.EXE [SYS$STARTUP]TCPIP$SHUTDOWN.COM [SYS$STARTUP]TCPIP$STARTUP.COM [SYSEXE]HOSTS.DAT [SYSEXE]NETWORKS.DAT [SYSEXE]PROTOCOLS.DAT [SYSEXE]RESOLV.CONF [SYSEXE]TCPIP$BGDRIVER.STB [SYSEXE]TCPIP$BGDRIVER_PERF.STB [SYSEXE]TCPIP$BIND_RUN.COM [SYSEXE]TCPIP$BOOTP_RUN.COM [SYSEXE]TCPIP$CONVERT.COM [SYSEXE]TCPIP$CONVERT.FDL [SYSEXE]TCPIP$DHCP_CLIENT_RUN.COM [SYSEXE]TCPIP$DHCP_RUN.COM [SYSEXE]TCPIP$FAILSAFE.EXE [SYSEXE]TCPIP$FAILSAFE_RUN.COM [SYSEXE]TCPIP$FINGER_SRVR_RUN.COM [SYSEXE]TCPIP$FTP_CHILD.EXE [SYSEXE]TCPIP$FTP_CLIENT.EXE [SYSEXE]TCPIP$FTP_RUN.COM [SYSEXE]TCPIP$FTP_SERVER.COM [SYSEXE]TCPIP$FTP_SERVER.EXE [SYSEXE]TCPIP$IMAP_RUN.COM [SYSEXE]TCPIP$INETACP.EXE [SYSEXE]TCPIP$INETACP.STB [SYSEXE]TCPIP$INETACP_PERF.EXE [SYSEXE]TCPIP$INETACP_PERF.STB [SYSEXE]TCPIP$INETDRIVER.STB [SYSEXE]TCPIP$INTERNET_SERVICES.STB [SYSEXE]TCPIP$INTERNET_SERVICES_PERF.STB [SYSEXE]TCPIP$IP6RTRD_RUN.COM [SYSEXE]TCPIP$IP6_TESTADDR.EXE [SYSEXE]TCPIP$IPTUNNEL.EXE [SYSEXE]TCPIP$LBROKER_RUN.COM [SYSEXE]TCPIP$LOCKD_RUN.COM [SYSEXE]TCPIP$LPD_RCV.EXE [SYSEXE]TCPIP$LPD_RECV_RUN.COM [SYSEXE]TCPIP$LPD_SMB.EXE [SYSEXE]TCPIP$LPD_UTILITIES.EXE [SYSEXE]TCPIP$LPQ.EXE [SYSEXE]TCPIP$LPRM.EXE [SYSEXE]TCPIP$LPRSETUP.EXE [SYSEXE]TCPIP$METRIC_RUN.COM [SYSEXE]TCPIP$MOUNTD_RUN.COM [SYSEXE]TCPIP$ND6HOST_RUN.COM [SYSEXE]TCPIP$NET_GLOBALS.STB [SYSEXE]TCPIP$NET_GLOBALS_PERF.STB [SYSEXE]TCPIP$NFSSTAT.EXE [SYSEXE]TCPIP$NFS_GLOBALS.STB [SYSEXE]TCPIP$NFS_RUN.COM [SYSEXE]TCPIP$NFS_SERVER.EXE [SYSEXE]TCPIP$NFS_SERVICES.STB [SYSEXE]TCPIP$NTP-GENKEYS.EXE [SYSEXE]TCPIP$NTP.EXE [SYSEXE]TCPIP$NTPDATE.EXE [SYSEXE]TCPIP$NTPDC.EXE [SYSEXE]TCPIP$NTPQ.EXE [SYSEXE]TCPIP$NTPTRACE.EXE [SYSEXE]TCPIP$NTP_RES_CHILD.EXE [SYSEXE]TCPIP$NTP_RUN.COM [SYSEXE]TCPIP$PCNFSD_RUN.COM [SYSEXE]TCPIP$PING.EXE [SYSEXE]TCPIP$POP_RUN.COM [SYSEXE]TCPIP$PORTM_RUN.COM [SYSEXE]TCPIP$PWIPACP.EXE [SYSEXE]TCPIP$PWIPACP.STB [SYSEXE]TCPIP$PWIPDRIVER.STB [SYSEXE]TCPIP$PWIPSHUT.EXE [SYSEXE]TCPIP$REXEC_RUN.COM [SYSEXE]TCPIP$ROUTE.EXE [SYSEXE]TCPIP$RSH_RUN.COM [SYSEXE]TCPIP$SMTP_RECEIVER.EXE [SYSEXE]TCPIP$SMTP_RECV_RUN.COM [SYSEXE]TCPIP$SMTP_SFF.EXE [SYSEXE]TCPIP$SMTP_SYMBIONT.EXE [SYSEXE]TCPIP$SNMP_RUN.COM [SYSEXE]TCPIP$SSH_RCMD.COM [SYSEXE]TCPIP$SSH_RUN.COM [SYSEXE]TCPIP$SSH_SCP2.EXE [SYSEXE]TCPIP$SSH_SFTP-SERVER2.EXE [SYSEXE]TCPIP$SSH_SFTP2.EXE [SYSEXE]TCPIP$SSH_SSH-ADD2.EXE [SYSEXE]TCPIP$SSH_SSH-AGENT2.EXE [SYSEXE]TCPIP$SSH_SSH-KEYGEN2.EXE [SYSEXE]TCPIP$SSH_SSH-SIGNER2.EXE [SYSEXE]TCPIP$SSH_SSH2.EXE [SYSEXE]TCPIP$SSH_SSHD2.EXE [SYSEXE]TCPIP$STATD_RUN.COM [SYSEXE]TCPIP$TELNET.EXE [SYSEXE]TCPIP$TELNETSYM.EXE [SYSEXE]TCPIP$TELNET_RUN.COM [SYSEXE]TCPIP$TELNET_SERVER.EXE [SYSEXE]TCPIP$TFTP_RUN.COM [SYSEXE]TCPIP$TNDRIVER.STB [SYSEXE]TCPIP$TNDRIVER_PERF.STB [SYSEXE]TCPIP$TN_GLOBALS.STB [SYSEXE]TCPIP$TRACEROUTE.EXE [SYSEXE]TCPIP$TTCP.EXE [SYSEXE]TCPIP$UCP.EXE [SYSEXE]TCPIP$UUDECODE.EXE [SYSEXE]TCPIP$UUENCODE.EXE [SYSEXE]TCPIP$VERSIONS.EXE [SYSEXE]TCPIP$XDM_RUN.COM [SYSEXE]TCPIP$XDM_XSESSION.COM [SYSEXE]UCX$LPD_SMB.EXE [SYSEXE]UCX$TELNETSYM.EXE [SYSEXE]UCX$UCP.EXE [SYSHLP.EXAMPLES.TCPIP.IPV6.BIND]IPV6.ARPA [SYSHLP.EXAMPLES.TCPIP.IPV6.BIND]IPV6.DB [SYSHLP.EXAMPLES.TCPIP.IPV6.BIND]IPV6.INT [SYSHLP.EXAMPLES.TCPIP.IPV6.BIND]TCPIP$BIND.CONF_IPV6 [SYSHLP.EXAMPLES.TCPIP]TCPIP$PROXY_RELOAD.COM [SYSHLP.EXAMPLES.TCPIP]TCPIP$RESTART_SMTPQ.COM [SYSHLP.EXAMPLES.TCPIP]TN3270DEF.MAR [SYSHLP]TCPIP$FTP_HELP.HLB [SYSHLP]TCPIP$TELNET_HELP.HLB [SYSHLP]TCPIP$UCP_HELP.HLB [SYSHLP]TCPIP.MSGHLP$DATA [SYSHLP]TCPIP54ECO01.RELEASE_NOTES [SYSLIB]TCPIP$CFS_SHR.EXE [SYSLIB]TCPIP$INETDEF.ADA [SYSLIB]TCPIP$INETDEF.BAS [SYSLIB]TCPIP$INETDEF.FOR [SYSLIB]TCPIP$INETDEF.H [SYSLIB]TCPIP$INETDEF.MAR [SYSLIB]TCPIP$INETDEF.PAS [SYSLIB]TCPIP$INETDEF.PLI [SYSLIB]TCPIP$INETDEF.R32 [SYSLIB]TCPIP$IPC_SHR.EXE [SYSLIB]TCPIP$LPD_SHR.EXE [SYSLIB]TCPIP$PPPD_CALLOUT.EXE [SYSLIB]TCPIP$SMTP_MAILSHR.EXE [SYSLIB]TCPIP$SMTP_PARSESHR_TV.EXE [SYSLIB]TCPIP$TEMPLATES.TLB [SYSLIB]TNIODEF.ADA [SYSLIB]TNIODEF.BAS [SYSLIB]TNIODEF.FOR [SYSLIB]TNIODEF.H [SYSLIB]TNIODEF.MAR [SYSLIB]TNIODEF.PAS [SYSLIB]TNIODEF.PLI [SYSLIB]TNIODEF.R32 [SYSLIB]UCX$INETDEF.ADA [SYSLIB]UCX$INETDEF.BAS [SYSLIB]UCX$INETDEF.FOR [SYSLIB]UCX$INETDEF.H [SYSLIB]UCX$INETDEF.MAR [SYSLIB]UCX$INETDEF.PAS [SYSLIB]UCX$INETDEF.PLI [SYSLIB]UCX$INETDEF.R32 [SYSLIB]UCX$IPC_SHR.EXE [SYSMGR]SYS$NET_SERVICES_TCPIP.COM [SYSMGR]TCPIP$BIND_SHUTDOWN.COM [SYSMGR]TCPIP$BIND_STARTUP.COM [SYSMGR]TCPIP$BOOTP_SHUTDOWN.COM [SYSMGR]TCPIP$BOOTP_STARTUP.COM [SYSMGR]TCPIP$CALLBACKS.COM [SYSMGR]TCPIP$CONFIG.COM [SYSMGR]TCPIP$CUSTOMER_SERVICE_SHUTDOWN.COM [SYSMGR]TCPIP$CUSTOMER_SERVICE_STARTUP.COM [SYSMGR]TCPIP$DEFINE_COMMANDS.COM [SYSMGR]TCPIP$DHCP_CLIENT_SHUTDOWN.COM [SYSMGR]TCPIP$DHCP_CLIENT_STARTUP.COM [SYSMGR]TCPIP$DHCP_SHUTDOWN.COM [SYSMGR]TCPIP$DHCP_STARTUP.COM [SYSMGR]TCPIP$FAILSAFE_SHUTDOWN.COM [SYSMGR]TCPIP$FAILSAFE_STARTUP.COM [SYSMGR]TCPIP$FINGER_SHUTDOWN.COM [SYSMGR]TCPIP$FINGER_STARTUP.COM [SYSMGR]TCPIP$FTP_CLIENT_SHUTDOWN.COM [SYSMGR]TCPIP$FTP_CLIENT_STARTUP.COM [SYSMGR]TCPIP$FTP_SHUTDOWN.COM [SYSMGR]TCPIP$FTP_STARTUP.COM [SYSMGR]TCPIP$IMAP_SHUTDOWN.COM [SYSMGR]TCPIP$IMAP_STARTUP.COM [SYSMGR]TCPIP$INET_DRIVER_SHUTDOWN.COM [SYSMGR]TCPIP$INET_DRIVER_STARTUP.COM [SYSMGR]TCPIP$INET_SHUTDOWN.COM [SYSMGR]TCPIP$INET_STARTUP.COM [SYSMGR]TCPIP$IP6_SETUP.COM [SYSMGR]TCPIP$LBROKER_SHUTDOWN.COM [SYSMGR]TCPIP$LBROKER_STARTUP.COM [SYSMGR]TCPIP$LOCKD_SHUTDOWN.COM [SYSMGR]TCPIP$LOCKD_STARTUP.COM [SYSMGR]TCPIP$LPD_SHUTDOWN.COM [SYSMGR]TCPIP$LPD_STARTUP.COM [SYSMGR]TCPIP$METRIC_SHUTDOWN.COM [SYSMGR]TCPIP$METRIC_STARTUP.COM [SYSMGR]TCPIP$NFS_CLIENT_SHUTDOWN.COM [SYSMGR]TCPIP$NFS_CLIENT_STARTUP.COM [SYSMGR]TCPIP$NFS_SHUTDOWN.COM [SYSMGR]TCPIP$NFS_STARTUP.COM [SYSMGR]TCPIP$NTP_SHUTDOWN.COM [SYSMGR]TCPIP$NTP_STARTUP.COM [SYSMGR]TCPIP$PCNFS_SHUTDOWN.COM [SYSMGR]TCPIP$PCNFS_STARTUP.COM [SYSMGR]TCPIP$POP_SHUTDOWN.COM [SYSMGR]TCPIP$POP_STARTUP.COM [SYSMGR]TCPIP$PORTMAPPER_SHUTDOWN.COM [SYSMGR]TCPIP$PORTMAPPER_STARTUP.COM [SYSMGR]TCPIP$PROXY_SHUTDOWN.COM [SYSMGR]TCPIP$PROXY_STARTUP.COM [SYSMGR]TCPIP$PWIP_DRIVER_SHUTDOWN.COM [SYSMGR]TCPIP$PWIP_DRIVER_STARTUP.COM [SYSMGR]TCPIP$REXEC_SHUTDOWN.COM [SYSMGR]TCPIP$REXEC_STARTUP.COM [SYSMGR]TCPIP$RLOGIN_SHUTDOWN.COM [SYSMGR]TCPIP$RLOGIN_STARTUP.COM [SYSMGR]TCPIP$RMT_CHECK_ACCESS.COM [SYSMGR]TCPIP$RMT_SHUTDOWN.COM [SYSMGR]TCPIP$RMT_STARTUP.COM [SYSMGR]TCPIP$RSH_SHUTDOWN.COM [SYSMGR]TCPIP$RSH_STARTUP.COM [SYSMGR]TCPIP$SMTP_SHUTDOWN.COM [SYSMGR]TCPIP$SMTP_STARTUP.COM [SYSMGR]TCPIP$SNMP_SHUTDOWN.COM [SYSMGR]TCPIP$SNMP_STARTUP.COM [SYSMGR]TCPIP$SSH_CLIENT_SHUTDOWN.COM [SYSMGR]TCPIP$SSH_CLIENT_STARTUP.COM [SYSMGR]TCPIP$SSH_SHUTDOWN.COM [SYSMGR]TCPIP$SSH_STARTUP.COM [SYSMGR]TCPIP$STATD_SHUTDOWN.COM [SYSMGR]TCPIP$STATD_STARTUP.COM [SYSMGR]TCPIP$SYMBOLS.COM [SYSMGR]TCPIP$TELNETSYM_SHUTDOWN.COM [SYSMGR]TCPIP$TELNETSYM_STARTUP.COM [SYSMGR]TCPIP$TELNET_SHUTDOWN.COM [SYSMGR]TCPIP$TELNET_STARTUP.COM [SYSMGR]TCPIP$TFTP_SHUTDOWN.COM [SYSMGR]TCPIP$TFTP_STARTUP.COM [SYSMGR]TCPIP$UCP_SHUTDOWN.COM [SYSMGR]TCPIP$UCP_STARTUP.COM [SYSMGR]TCPIP$V51_CONVERSION.COM [SYSMGR]TCPIP$XDM_SHUTDOWN.COM [SYSMGR]TCPIP$XDM_STARTUP.COM [SYSMGR]UCX$CONFIG.COM [SYSMGR]UCX$STARTUP.COM [SYSTEST]TCPIP$IVP.COM [SYSUPD]TCPIP$CLEANUP.COM [SYSUPD]TCPIP$PCSI_POST_INSTALL.COM [TCPIP$LIB]TCPIP$LIB.OLB 6 PROBLEMS ADDRESSED IN THIS KIT Release Notes for HP TCP/IP Services for OpenVMS V5.4 Update ECO 1 ________________________________________________________________ (C) Copyright 2004 Hewlett-Packard Development Company, L.P. UNIX[R] is a registered trademark of The Open Group. Microsoft[R] is a US registered trademark of Microsoft Corporation. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Proprietary computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The HP TCP/IP Services for OpenVMS documentation is available on CD-ROM. ------------------------------------------------------------------------------- PREVIOUSLY UNDOCUMENTED BEHAVIOR: ------------------------------------------------------------------------------- -------------------------------------------------------------- 1: Dependency for PPP on OpenVMS 7.2-2 and above -------------------------------------------------------------- IPCP negotiation of IP address between PC client and OpenVMS PPP server fails to assign client an IP address. Many problems were fixed in the OpenVMS PPPDRIVER. All customers running PPP on OpenVMS versions 7.3 and higher must install a patch for PPPDRIVER. Alpha OpenVMS kit (minimum version) ----- ----------------------------- 7.3 VMS73_PPPD-V0200 -------------------------------------------------------------- 2: SMTP dependency on OpenVMS Kits -------------------------------------------------------------- Problem: When you compose a mail message in OpenVMS mail and enter an SMTP address at the To: prompt and at the Cc: prompt, the address originally entered at the Cc: prompt is not put into a Cc: RFC header in the SMTP message but is instead put into the To: RFC header. Dependencies: For this fix to be effective the following OpenVMS kits must be installed. Alpha OpenVMS kit (minimum version) ----- ----------------------------- 7.3 VMS73_MAIL-V0100 -------------------------------------------------------------- 3: PTRs 30-10-194/30-10-174 IMAP Dependency on OpenVMS Kits -------------------------------------------------------------- The underlying OpenVMS problem has been fixed in OpenVMS versions 7.3-1 and later. For users running earlier versions of OpenVMS, the following two steps must be performed to enable IMAP upload support: 1) Install the following patch if running on VMS V7.3: Alpha OpenVMS kit (minimum version) ----- ----------------------------- 7.3 VMS73_SYSLOA-V0300 NOTE: This patch need only be installed on the system or systems that are running the IMAP server. Cluster nodes that are not running the IMAP server are not required to install the patch. 2) Add this line to your TCPIP$IMAP.CONF file: Upload-Supported: TRUE WARNING: Do not set the Upload-Supported configuration parameter on an unpatched system running an OpenVMS version prior to 7.3-1 -------------------------------------------------------------- 4: Inability of New IMAP Clients to Connect -------------------------------------------------------------- Problem: Inability of new IMAP clients to connect and of some connected clients to open additional folders. Problem detail: The IMAP server supports an application-specific limit on the number of connections an IMAP server process can handle before it forces the kernel to create a new IMAP server process. This value is set in the TCPIP$IMAP.CONF file to 25 (Max-Connections:25). The service limit default value (currently 16) should not be less than the application limit of 25. In fact it should be set much higher, or a server hang can result. As an example, Netscape uses five connections. Therefore, any more than 3 concurrently attached IMAP Netscape clients would exhaust the default 16-connection limit. Workaround: 1) Update the IMAP service limit from 16 to 1600: $ tcpip set service imap/limit=1600 $ tcpip show service imap/full/perm 2) Stop IMAP: $ @sys$startup:TCPIP$IMAP_SHUTDOWN 3) Wait until there are no more IMAP processes left. Keep entering the following command until all IMAP processes are gone. $ SHOW SYSTEM/PROCESS=*IMAP* 4) Start IMAP: $ @sys$startup:TCPIP$IMAP_STARTUP -------------------------------------------------------------- 5: PTR 75-86-140 nslookup via TELNET Fails on V7.3-1 -------------------------------------------------------------- This problem was reported on OpenVMS V7.3-1 with TCP/IP V5.3. The symptom is that nslookup in interactive mode failed when connected via telnet. Problem detail: For a system that is, for example, accessed via TELNET (rather than SET HOST) that also has set the SYSGEN parameter MAXBUF to greater than 32K, if a C program is executed that uses a C runtime call (such as getc or gets) to read data from the terminal, this problem can occur. The C program may return a generic user I/O error message rather than the specific errors returned by RMS. (The TT driver returns an SS$_IVBUFLEN error. RMS returns RMS-F-QIO in the RAB$L_STS, and SYS-F-IVBUFLEN in the RAB$L_STV to the caller.) Workaround: Reduce the MAXBUF SYSGEN parameter to 32K. This is a dynamic parameter so no reboot is required. After the remedial kit is installed, MAXBUF can be reset to some higher value. Solution: Install the remedial kit: OpenVMS kit VMS731_RMS-V0100 -------------------------------------------------------------- 6: PTR 70-5-2210 ARP Timeouts Not Tunable over 32767 -------------------------------------------------------------- The ARP timeouts arpkillc, arpkilli, and arprefresh are limited to 32767 seconds. This known problem was introduced in V5.3 SSB. -------------------------------------------------------------- 7: PTRs 70-5-2191 and 70-5-2194 SMTP Mail Hang -------------------------------------------------------------- 70-5-2191/CFS-96560: TCP/IP V5.3 ECO1 incoming SMTP mail job stalls during processing. This is because mail hangs on $BRKTHRU, which is called from MAILSHRP with VMS73-SYS patch. 70-5-2194/CFS-96677: SMTP mail hangs with AXPVMS VMS73_SYS V5.0. Solution: Alpha OpenVMS kit (minimum version) ----- ----------------------------- 7.3 VMS73_SYS-V0600 7.3-1 VMS731_SYS-V0300 -------------------------------------------------------------- 8: PTR 70-5-2259 NFS Client Restriction -------------------------------------------------------------- The MOUNT command used by the NFS client is restricted to 255 characters in total length. Depending on where the 255 character limit is reached in the command line, the command might generate an error message. Abbreviate some of the parameter names until the total length is less than or equal to 255 characters. -------------------------------------------------------------- 9: Changes to KERNEL parameter defaults -------------------------------------------------------------- The following sysconfig default settings were changed in previous releases but not documented in the V5.4 release notes: TCP/IP V5.1 changed the defaults that affect the ephemeral (non-privileged) port numbers assigned to sockets. The changes were made to match IANA recommendations. The following changes were carried over to V5.4: ipport_userreserved_min (1024 -> 49152) ipport_userreserved (5000 -> 65535) V5.4 changed the following default setting to comply with RFC 1122. It increases the initial keepalive probe from 75 seconds to 2 hours. tcp_keepidle (150 -> 14400) -------------------------------------------------------------- 10: SMTP receiver doesn't check recipient deliverability -------------------------------------------------------------- Problem: The SMTP receiver does not check to see if the recipient email address in the RCPT TO SMTP protocol command is deliverable (for example that the user account exists on the system). This check is instead deferred to the processing of the mail message in the SMTP queue by the SMTP symbiont process. By this time, the host has taken responsibility for the message and, if there is a problem delivering the message, must bounce the message itself. This behavior is more problematic when the system receives SPAM. SPAM arrives on the host for a non-existent user and is bounced by your host's symbiont process to the email address in the SPAM's Return-Path: header. The SPAM's Return-Path: header contains an invalid email address, so the bounced SPAM is in turn bounced back to your host's POSTMASTER account. The POSTMASTER account's mail is forwarded to the SYSTEM account, which means that the SYSTEM user must constantly separate these doubly bounced SPAMs from their valid email. Solution: The SMTP receiver has been changed to check to see if the recipient email address in the RCPT TO SMTP protocol command is deliverable. This solves the problem by not letting the SPAM for the unknown user onto the host in the first place. A configuration option now exists to turn this new feature on and off. The option is called Symbiont-Checks-Deliverability and is entered in the SMTP.CONFIG SMTP configuration file. Setting this option to TRUE preserves the old behavior - where the receiver does not check the deliverability of RCPT TO recipients, deferring to the symbiont. Setting Symbiont-Checks-Deliverability to FALSE turns on the new behavior, telling the receiver to check the deliverability of RCPT TO recipients itself. To preserve existing behavior, this option is set by default to TRUE for TCP/IP Services Version 5.4. For future versions it will default to FALSE. -------------------------------------------------------------- 11: CERT updates for OpenVMS TCP/IP Service V5.4 SSH: -------------------------------------------------------------- 1. SSRT3629A/B: Code checked; not vulnerable 2. CERT CA-2003-24: OpenSSH only; not vulnerable 3. CERT CA-2002-36: The worst case effect of the vulnerability is a denial of service (DoS) for a single connection of one of these types: - the server process that is handling a connection from a malicious client - the client process that is connecting to a malicious server In either case it is not possible for a malicious remote host to gain access to the OpenVMS host (e.g., to execute arbitrary code). The ability of an OpenVMS server to receive a new connection is not affected. 4. CERT CA-2001-35: Affects SSH version 1 only, which is not supported; not vulnerable 5. CERT CA-1999-15: RSAREF2 library not used; not vulnerable 6. CERT CA-1998-03: Old versions (1.2.17 through 1.2.21) referenced, current release based on much newer code; not vulnerable -------------------------------------------------------------- 12: IPv6 documentation changes (TCPIP_BUGS Note 3040): -------------------------------------------------------------- 1.a. Guide to IPv6, Section 2.5.1 Run TCPIP$IP6_SETUP to Configure Host Update IPv6 host configuration procedure as shown here: Configuring an IPv6 Host To configure your system as an IPv6 host, do the following: 1. Invoke the TCPIP$IP6_SETUP configuration procedure by entering the following command: $ @SYS$MANAGER:TCPIP$IP6_SETUP 2. Choose to configure the system as an IPv6 host by taking the default to the following prompt (press Return or enter NO): Configure this system as an IPv6 router? [NO]: 3. Indicate whether you want to configure a 6to4 interface by responding to the following prompt: Configure a 6to4 interface? [NO]: A 6to4 interface is needed if this host is connected to an IPv4-only network and needs to communicate with other 6to4 or native IPv6 sites. If this system is a host within a 6to4 site, do not create a 6to4 interface; a 6to4 address is automatically configured on this system using standard IPv6 mechanisms. If you do not want to configure a 6to4 interface, press Return. The configuration procedure goes to step 8. If you want to configure a 6to4 interface, enter YES. The configuration procedure then displays the 6to4 tunnel interface, as shown here: The 6to4 tunnel is: TN1 You will be prompted to enter information about the 6to4 interface in subsequent steps. 4. Enter this host's IPv4 address in response to the following prompt: Enter this node's IPv4 address to use when generating your site's 6to4 prefix: Enter the IPv4 address in dotted-decimal format (d.d.d.d). The configuration procedure automatically generates a 6to4 site prefix based on the IPv4 address entered, and displays the prefix as shown here: Your 6to4 site prefix is: 2002:x:x::/48 5. Enter the address prefix for the 6to4 tunnel in response to the following prompt: Enter an address prefix to use on interface TN1 [2002:x:x::/64]: You can accept the IPv6 address prefix generated in the previous step by taking the default. ________________________ Note ________________________ The high-order 48 bits of the 6to4 address prefix must be the same as your 6to4 site prefix. ______________________________________________________ 6. Indicate whether you want to configure a 6to4 relay router: Configure a 6to4 relay router? [NO]: A relay router is needed to connect your system to native IPv6 sites. If you do not configure a relay router, your system can connect to other 6to4 sites but not to native IPv6 sites. If you do not want to configure a 6to4 relay router, press Return. The configuration procedure goes to step 8. If you want to configure a 6to4 relay router, enter YES. 7. Specify the address of a relay router: Enter the 6to4 address of a 6to4 relay router [2002:C058:6301::]: The address of the default relay router is displayed. To use the default, press Return. Otherwise, enter the 6to4 unicast address of a 6to4 relay router. 8. For each network interface on your system, the configuration procedure asks whether you want to enable IPv6 on that interface, as shown below, where ddn is the internet interface name, such as WE0: Enable IPv6 on interface ddn? [YES]: If you want to enable IPv6 on this interface, press Return; if you do not, enter NO. If your system has multiple interfaces, the configuration procedure repeats this question for each interface. 9. Indicate whether you want to configure an automatic tunnel by responding to the following prompt: Configure an IPv6 over IPv4 automatic tunnel interface? [NO]: If you do not want to configure an automatic tunnel, press Return; the configuration procedure goes to step 11. If you want to configure an automatic tunnel, enter YES; the configuration procedure displays the automatic tunnel interface as shown here, and then prompts you for the tunnel's address in step 10. The automatic tunnel is: TN0 ________________________ Note ________________________ Because of potential IPv4-compatible address routing problems, HP recommends that you avoid using automatic tunnels. ______________________________________________________ 10. Enter the IPv4 address to use when constructing the automatic tunnel's endpoint. Enter this node's IPv4 address to use when creating your automatic tunnel: Enter the IPv4 address in dotted-decimal format (d.d.d.d). 11. Indicate whether you want to create an IPv6 over IPv4 configured tunnel, by responding to the following prompt: Create IPv6 over IPv4 configured tunnels? [NO]: If you want to create an IPv6 over IPv4 configured tunnel, enter YES and press Return. You will be prompted for information about this tunnel in subsequent steps. If you do not want to create an IPv6 over IPv4 configured tunnel, press Return; the procedure goes to step 16. 12. Enter the tunnel's source IPv4 address in response to the following prompt: Enter the source IPv4 address of tunnel ITn: Enter the tunnel's source IPv4 address in dotted-decimal format (d.d.d.d). 13. Enter the tunnel's destination IPv4 address in response to the following prompt: Enter the destination IPv4 address of tunnel ITn: Enter the tunnel's destination IPv4 address in dotted-decimal format (d.d.d.d). The tunnel's destination address must differ from the source address entered in the previous step. 14. Enter an address prefix to use on the tunnel interface in response to the following prompt: Enter an address prefix to use on interface ITn [DONE]: If a router is not advertising a global address prefix on this tunnel interface, enter a 64-bit address prefix. You can configure multiple address prefixes for this configured tunnel. You will be prompted for additional address prefixes until you enter DONE. If you do not want the host to use an IPv6 address prefix on the tunnel interface, press Return. 15. Indicate whether you want to create another IPv6 over IPv4 configured tunnel, by responding to the following prompt: Create another IPv6 over IPv4 configured tunnel? [NO]: If you want to create another IPv6 over IPv4 configured tunnel, enter YES and press Return. The configuration procedure repeats steps 12 through 14 for each additional configured tunnel you choose to create. If you do not want to create another IPv6 over IPv4 configured tunnel, press Return. 16. Indicate whether you want to create an IPv6 over IPv6 configured tunnel, by responding to the following prompt: Create IPv6 over IPv6 configured tunnels? [NO]: If you want to create an IPv6 over IPv6 configured tunnel, enter YES and press Return. You will be prompted for information about this tunnel in subsequent steps. If you do not want to create an IPv6 over IPv6 configured tunnel, press Return; the configuration procedure goes to step 21. 17. Enter the tunnel's source IPv6 address in response to the following prompt: Enter the source IPv6 address of tunnel ITn: Enter the source IPv6 address of the designated tunnel. 18. Enter the tunnel's destination IPv6 address in response to the following prompt: Enter the destination IPv6 address of tunnel ITn: Enter the destination IPv6 address of the designated tunnel. The tunnel's destination address must differ from the source address entered in the previous step. 19. Enter an address prefix to use on the tunnel interface in response to the following prompt: Enter an address prefix to use on interface ITn [DONE]: If a router is not advertising a global address prefix on this tunnel interface, enter a 64-bit address prefix. You can configure multiple address prefixes for this configured tunnel. You will be prompted for additional address prefixes until you enter DONE. If you do not want the host to use an IPv6 address prefix on the tunnel interface, press Return. 20. Indicate whether you want to create another IPv6 over IPv6 configured tunnel, by responding to the following prompt: Create another IPv6 over IPv6 configured tunnel? [NO]: If you want to create another IPv6 over IPv6 configured tunnel, enter YES and press Return. The configuration procedure repeats steps 17 through 19 for each additional configured tunnel you choose to create. If you do not want to create another IPv6 over IPv6 configured tunnel, press Return. 21. Indicate whether you want to define manual IPv6 routes by responding to the following prompt: Configure manual IPv6 routes? [NO]: If you want to define a manual IPv6 route to an adjacent router or remote IPv6 network, enter YES; subsequent prompts will ask you for information about the route. Otherwise, press Return; the configuration procedure goes to step 26. 22. Indicate the address prefix of a destination IPv6 network by responding to the following prompt: Enter the destination network address prefix: Enter the address prefix of the destination IPv6 network, or enter DEFAULT for the default route. 23. Enter the name of the interface through which you will send traffic to the remote IPv6 network and press Return. Enter interface to use when forwarding messages: 24. Enter the link-local IPv6 address of the first router in the path to the destination network. This address together with the IPv6 address prefix constitute the static routing table entry. Enter the next node's IPv6 address: If the next node is on the same link as this node or is reachable through a configured tunnel, enter the link- local address. If the next node is reachable through an automatic tunnel, enter the IPv4-compatible IPv6 address. For all other connections, enter the IPv6 address. 25. Indicate whether you want to define another manual IPv6 route to an adjacent router or remote IPv6 network by responding to the following prompt: Configure another manual IPv6 route? [NO]: If you want to define another manual IPv6 route, enter YES and press Return. The configuration procedure repeats steps 22 through 24 for each additional manual IPv6 route you choose to define. If you do not want to define another manual IPv6 route, press Return. 26. The configuration procedure displays a summary of your new IPv6 host configuration, as shown in the following example: You configured this node as a IPv6 host with the following: Daemons: ND6HOST Dynamic Updates Disabled Interfaces: WE0 Dynamic Address Configuration Enabled TN1 6to4 Tunneling Enabled using 5.6.7.8 Prefix 2002:506:708::/64 Relay Router 2002:90A:B0C:1::1 Manual Routes: 2002::/16 TN1 FE80::5.6.7.8 DEFAULT TN1 2002:90A:B0C:1::1 27. Indicate whether you want to create a new host configuration file based on the choices you have made, by responding to the following prompt: Create new IPv6 network configuration files? [YES]: If you are not satisfied with the configuration, enter NO; the configuration procedure will end immediately without changing the current IPv6 network configuration. If you are satisfied with the configuration, press Return. The configuration procedure creates new host configuration file and then displays the following message: A new IPv6 configuration file, SYS$SYSTEM:TCPIP$INET6_CONFIG.DAT, has been created. The previous configuration file (if any) has been renamed to SYS$SYSTEM:TCPIP$INET6_CONFIG.DAT_OLD. This new IPv6 network configuration will become active the next time TCP/IP Services for OpenVMS is started. 1.b. Guide to IPv6, Section 2.6.1 Running TCPIP$IP6_SETUP to Configure Router Update IPv6 router configuration procedure as shown here: Configuring an IPv6 Router To configure your system as an IPv6 router, do the following: 1. Invoke the TCPIP$IP6_SETUP configuration procedure by entering the following command: $ @SYS$MANAGER:TCPIP$IP6_SETUP 2. Choose to configure the system as an IPv6 router by entering YES and pressing Return at the following prompt: Configure this system as an IPv6 router? [NO]: 3. Indicate whether you want to configure a 6to4 interface by responding to the following prompt: Configure a 6to4 interface? [NO]: A 6to4 interface is needed to configure a border router. If you do not want to configure a 6to4 interface, press Return. The configuration procedure goes to step 7. If you want to configure a 6to4 interface, enter YES and press Return. The configuration procedure then displays the 6to4 tunnel interface, as shown here: The 6to4 tunnel is: TN1 You will be prompted to enter information about the 6to4 interface in subsequent steps. 4. Enter this router's IPv4 address in response to the following prompt: Enter this node's IPv4 address to use when generating your site's 6to4 prefix: The IPv4 address must be in dotted-decimal format (d.d.d.d). The configuration procedure automatically generates a 6to4 site prefix based on the IPv4 address entered, and displays the prefix as shown here: Your 6to4 site prefix is: 2002:x:x::/48 This site prefix is advertised to hosts on the interfaces attached to the IPv6 site. This address must be a valid, globally unique IPv4 address configured on the router's interface to the IPv4 network. 5. Indicate whether you want this system to function as a 6to4 relay router: Configure a 6to4 relay router? [NO]: If hosts in this border router's 6to4 site need to communicate with native IPv6 sites (IPv6 only), enter YES and press Return. If you do not want the system to function as a 6to4 relay router, press Return. The configuration procedure goes to step 7. 6. Specify the address of a relay router: Enter the 6to4 address of a 6to4 relay router [2002:C058:6301::]: The address of the default relay router is displayed. To use the default, press Return. Otherwise, enter the 6to4 unicast address of a 6to4 relay router. 7. For each network interface on your system, the configuration procedure asks whether you want to enable IPv6 on that interface, as shown below, where ddn is the internet interface name, such as WE0: Enable IPv6 on interface ddn? [YES]: If you want to enable IPv6 on this interface, press Return; if you do not, enter NO. For each interface, the configuration procedure repeats steps 7 through 9. 8. Indicate whether you want the router to run the RIPng protocol on the designated interface by responding to the following prompt: Enable RIPng on interface ddn? [YES]: If you want the router to run the RIPng protocol, press Return; otherwise, enter NO and press Return. The RIPng protocol allows this router to exhange IPv6 routes with other routers. 9. Indicate whether you want the router to advertise an IPv6 address prefix on the designated interface, by responding to the following prompt: Enter an address prefix to advertise on interface ddn [DONE]: If you want the router to advertise an IPv6 address prefix, enter a 64-bit address prefix for the interface and press Return. You can configure multiple address prefixes for this interface. You will be prompted for additional address prefixes until you enter DONE. If you do not want the router to advertise an IPv6 address prefix on the designated interface, enter DONE and press Return. 10. Indicate whether you want to configure an automatic tunnel by responding to the following prompt: Configure an IPv6 over IPv4 automatic tunnel interface? [NO]: If you do not want to configure an automatic tunnel, press Return; the configuration procedure goes to step 12. If you want to configure an automatic tunnel, enter YES; the configuration procedure displays the automatic tunnel interface as shown here, and then prompts you for the tunnel's address in step 11. The automatic tunnel is: TN0 ________________________ Note ________________________ Because of potential IPv4-compatible address routing problems, HP recommends that you avoid using automatic tunnels. ______________________________________________________ 11. Enter the IPv4 address to use when constructing the automatic tunnel's endpoint. Enter this node's IPv4 address to use when creating your automatic tunnel: Enter the IPv4 address in dotted-decimal format (d.d.d.d). 12. Indicate whether you want to create an IPv6 over IPv4 configured tunnel, by responding to the following prompt: Create IPv6 over IPv4 configured tunnels? [NO]: If you want to create an IPv6 over IPv4 configured tunnel, enter YES and press Return. You will be prompted for information about this tunnel in subsequent steps. If you do not want to create an IPv6 over IPv4 configured tunnel, press Return; the configuration procedure goes to step 18. 13. Enter the tunnel's source IPv4 address in response to the following prompt: Enter the source IPv4 address of tunnel ITn: Enter the tunnel's source IPv4 address in dotted-decimal format (d.d.d.d). 14. Enter the tunnel's destination IPv4 address in response to the following prompt: Enter the destination IPv4 address of tunnel ITn: Enter the tunnel's destination IPv4 address in dotted-decimal format (d.d.d.d). The tunnel's destination address must differ from the source address entered in the previous step. 15. Indicate whether you want to enable the RIPng protocol on the designated interface by responding to the following prompt: Enable RIPng on interface ITn? [YES]: Press Return if you want to enable the RIPng protocol on this interface; enter NO and press Return if you do not. The RIPng protocol allows this router to exhange IPv6 routes with other routers. 16. Indicate whether you want the router to advertise an IPv6 address prefix on the tunnel interface, by responding to the following prompt: Enter an address prefix to advertise on interface ITn? [DONE]: If you want the router to advertise an IPv6 address prefix, enter a 64-bit address prefix for the designated interface and press Return. You can configure multiple address prefixes for this interface. You will be prompted for additional address prefixes until you enter DONE. If you do not want the router to use an IPv6 address prefix on the tunnel interface, enter DONE. 17. Indicate whether you want to create another IPv6 over IPv4 configured tunnel, by responding to the following prompt: Create another IPv6 over IPv4 configured tunnel? [NO]: If you want to create another IPv6 over IPv4 configured tunnel, enter YES and press Return. The configuration procedure repeats steps 13 through 16 for each additional configured tunnel you choose to create. If you do not want to create another IPv6 over IPv4 configured tunnel, press Return. 18. Indicate whether you want to create an IPv6 over IPv6 configured tunnel, by responding to the following prompt: Create IPv6 over IPv6 configured tunnels? [NO]: If you want to create an IPv6 over IPv6 configured tunnel, enter YES and press Return. You will be prompted to enter information about this tunnel in subsequent steps. If you do not want to create an IPv6 over IPv6 configured tunnel, press Return; the configuration procedure goes to step 24. 19. Enter the tunnel's source IPv6 address in response to the following prompt: Enter the source IPv6 address of tunnel ITn: Enter the source IPv6 address of the designated tunnel. 20. Enter the tunnel's destination IPv6 address in response to the following prompt: Enter the destination IPv6 address of tunnel ITn: Enter the destination IPv6 address of the designated tunnel. The tunnel's destination address must differ from the source address entered in the previous step. 21. Indicate whether you want to enable the RIPng protocol on the interface by responding to the following prompt: Enable RIPng on interface ITn? [YES]: Press Return if you want to enable the RIPng protocol on this interface; enter NO and press Return if you do not. The RIPng protocol allows this router to exhange IPv6 routes with other routers. 22. Indicate whether you want the router to advertise an IPv6 address prefix on the tunnel interface, by responding to the following prompt: Enter an address prefix to advertise on interface ITn [DONE]: If you want the router to advertise an IPv6 address prefix, enter a 64-bit address prefix for the designated interface and press Return. You can configure multiple address prefixes for this interface. You will be prompted for additional address prefixes until you enter DONE. If you do not want the router to use an IPv6 address prefix on the tunnel interface, enter DONE. 23. Indicate whether you want to create another IPv6 over IPv6 configured tunnel, by responding to the following prompt: Create another IPv6 over IPv6 configured tunnel? [NO]: If you want to create another IPv6 over IPv6 configured tunnel, enter YES and press Return. The configuration procedure repeats steps 19 through 22 for each additional configured tunnel you choose to create. If you do not want to create another IPv6 over IPv6 configured tunnel, press Return. 24. Indicate whether you want to define manual IPv6 routes by responding to the following prompt: Configure manual IPv6 routes? [NO]: If you want to define a manual IPv6 route to an adjacent router or remote IPv6 network, enter YES; subsequent prompts will ask you for information about the route. Otherwise, press Return; the configuration procedure goes to step 29. 25. Indicate the address prefix of a destination IPv6 network by responding to the following prompt: Enter the destination network address prefix: Enter the address prefix of the destination IPv6 network, or enter DEFAULT for the default route. 26. Enter the name of the interface through which you will send traffic to the remote IPv6 network and press Return. Enter interface to use when forwarding messages: 27. Enter the link-local IPv6 address of the first router in the path to the destination network. This address together with the IPv6 address prefix constitute the static routing table entry. Enter the next node's IPv6 address: If the next node is on the same link as this node or is reachable through a configured tunnel, enter the link- local address. If the next node is reachable through an automatic tunnel, enter the IPv4-compatible IPv6 address. For all other connections, enter the IPv6 address. 28. Indicate whether you want to define another manual IPv6 route to an adjacent router or remote IPv6 network by responding to the following prompt: Configure another manual IPv6 route? [NO]: If you want to define another manual IPv6 route, enter YES and press Return. The configuration procedure repeats steps 25 through 27 for each additional manual IPv6 route you choose to define. If you do not want to define another manual IPv6 route, press Return. 29. The configuration procedure displays a summary of your new IPv6 router configuration, as shown in the following example: You configured this node as a IPv6 router with the following: Daemons: IP6RTRD Interfaces: WE0 RIP Enabled IT0 RIP Enabled Tunnel Source ::1 Tunnel Destination ::2 Prefix AAAA::/64 Prefix BBBB::/64 TN1 6to4 Tunneling Enabled using 1.2.3.4 Relay Router 2002:C058:6301:: Manual Routes: ::4/64 WE0 ::5 30. Indicate whether you want to create new router configuration files based on the choices you have made, by responding to the following prompt: Create new IPv6 network configuration files? [YES]: If you are not satisfied with the configuration, enter NO; the configuration procedure will end immediately without changing the current IPv6 network configuration. If you are satisfied with the configuration, press Return. The configuration procedure creates new router configuration files and then displays the following message: A new IPv6 configuration file, SYS$SYSTEM:TCPIP$INET6_CONFIG.DAT, has been created. The previous configuration file (if any) has been renamed to SYS$SYSTEM:TCPIP$INET6_CONFIG.DAT_OLD. A new IPv6 configuration file, SYS$SYSTEM:TCPIP$IP6RTRD.CONF, has been created. The previous configuration file (if any) has been renamed to SYS$SYSTEM:TCPIP$IP6RTRD.CONF_OLD. This new IPv6 network configuration will become active the next time TCP/IP Services for OpenVMS is started. -------------------------------------------------------------- 13: Updates for SSH release notes -------------------------------------------------------------- - When using TCPIP$CONFIG.COM to do a disable/re-enable for the SSH server, the following prompt is displayed: * Create a new default server host key? [YES]: Creating a new server host key can cause problems with clients which already have the existing key; enter "N" to override the default value. - If an user default directory in the sysuaf file uses the angle bracket (e.g., ) instead of square bracket ([USERNAME]) syntax, hostkey authentication fails. The workaround is to change the user entry to use square brackets. - For each SSH session, two processes are displayed in a SHOW SYSTEM. One process name has prefix "_FTA", for example: _FTA105: The other name has one of the following prefixes, depending on the number of digits in the TCP/IP Services network (BG) device: Number of digits Prefix Example in BG number less than 4 TCPIP$SSH_BG TCPIP$SSH_BG532 4 TCPIP$SS_BG TCPIP$SS_BG9408 5 TCPIP$S_BG TCPIP$S_BG10000 - The originating client host and username or port identification are not available in an ssh session on the OpenVMS server. For example, with a $ SHOW TERMINAL command for a telnet connection, the following lines are displayed; these lines are missing in SSH sessions: from a UNIX client: Remote Port Info: Host: unixsys.myco.com Port: 2728 from an OpenVMS client: Remote Port Info: Host: mysys.com Locn: _RTA4:/USER - The command line accepted for remote execution through ssh is limited to 153 characters. - In some cases of error or exit, SSH displays UNIX-style signal information, for example, a results in the message: Received signal 2, SIGINT: Interactive attention signal. These messages can be ignored. - The pairing of username and UIC in the sysuaf, as displayed by SHOW/IDENTIFIER must match that in the user account record. If there is a mismatch, the following error occurs when the user attempts to establish an SSH session: Received signal 10, SIGBUS: invalid access to memory objects. The workaround is to correct the pairing of username and UIC value in the sysuaf. - ssh, sftp and scp do not work correctly in batch mode - Packet related warnings may appear when using the sftp and scp commands on an OpenVMS SSH client when accessing an OpenSSH server, for example: sftp> ls . .bash_logout .login Warning: packet length mismatch: expected 27, got 8; connection to non-standard server? { and then after a pause... } sftp> Warning: packet length mismatch: expected 23, got 8; connection to non-standard server? The operation on OpenVMS succeeds despite the warnings. To suppress the warnings, assign the logical name "TCPIP$SSH_TOLERANT_PROTOCOL_STATUS" system-wide, for example: $ ASSIGN/SYSTEM 1 TCPIP$SSH_TOLERANT_PROTOCOL_STATUS To make this assignment persist over reboots, add it to a procedure executed at OpenVMS system startup time. Note that the if you enclose the logical name in quotation marks you must specify it in upper case, for example: $ ASSIGN/SYSTEM 1 "TCPIP$SSH_TOLERANT_PROTOCOL_STATUS" - Any non-OpenVMS client which implements the scp command using the ssh version 1 protocol is incompatibile with the OpenVMS SSH server. - The scp and sftp commands from the following Windows clients have been tested and interoperate correctly withthe OpenVMS SSH server: - PuTTY - SSH Communications Other versions and other clients may work, depending on protocol implemtntation and factors such as whether the formatting used by the client can handle OpenVMS format file paths and names. - When using sftp, before connecting to a remote system, characters entered at the sftp> prompt no longer double echo. Also, the left and arrow keys , , , and now work as expected to erase line, refresh line, and exit, respectively. However pressing does not display "Cancel". Also, does not work as in DCL to display a status line; instead it toggles two adjacent characters, as in UNIX. - The sftp ls command pauses for an extended time before continuing after the display of a page of data. - Using scp or sftp to copy a file back to itself (either in local mode, or by connecting back to the client host) fails with the error: %TCPIP-E-SSH_FC_ERR_INVA, file record format invalid for copy - Any client that uses ssh version 1 as the basis for the scp command will not work with the OpenVMS SSH server, which does not support that version of the protocol. - The -e option for ssh_keygen does not work - The following notes apply to implementation of X11 port forwarding: 1) If you have the system setup to run the remote X client application on your X server, all those applications can now be forwarded via SSH without any setup needed i.e. X11 forwarding works in it's native mode. The transports used for forwarding X applications on ssh is local and tcpip for X server running on a local system, and tcpip for X server running on a remote system. 2) The minimum requirement for X11 forwarding to work in native mode is DEC MOTIF 1.3. X11 forwarding uses the xauth feature of the X server authentication to authenticate the host/user. Xauth needs to be installed on the system for X11 forwarding to work. For more information on how to use xauth, see the documentation for DECwindows Motif for OpenVMS. 3) For X11 forwarding to work in the native mode, enable x11 forwarding on both client and server. To enable it on the client, set the value for forwardx11 to yes in client config file ssh2_config. To enable it on the server set the value for AllowX11Forwarding to yes in the server config file sshd2_config. An alternative way for client to enable x11 forwarding is to use the option +x . It does not matter if both the option are used. But If the X forwarding is enabled in the config file, you can disable it using the -x option. 4) If the X forwarding is enabled on both the ssh client and the ssh server, and you make a simple ssh connection to the remote ssh server, you should be able to run X client applications on your remote system and get the display on your X server. For example, you should be able to run DECW$CLOCK after making an ssh connection to the remote system. 5) SSH chaining of X11 forwarding is also possible. For example, if you are using excursion on a PC to display your remote OpenVMS or a UNIX system. From this system (say system1) you make a ssh connection to remote system (system2) and run X client application, for example, DECW$CLOCK for OpenVMS or xclock for UNIX. You would see the clock on your PC. In fact, you make a ssh connection from system1 to system2 and then to system3 and then to system4 and then to system5 and run an X client application on system5, you should still get the display on system1 even if the intermediate systems are not running X server. Problems user may encounter while forwarding X applications via SSH: 1) Display not set: Make sure that you have the display variable for the display running the ssh client. The display variable tells the ssh client which X server to connect, to display the X client application. You can check the display variable by using the following commands: On OpenVMS: $ SHOW LOGICAL DECW$DISPLAY The logical DECW$DISPLAY should have a value. It can either have a value of unix style display format :server.screen. Examples would be something like 16.20.99.10:0.0 or myhost.myco.com:0.0 or local/0:0.0 or a WSA device name. If it is a WSA device, you should get the display information using the following command (where 16.20.99.10 is a sample IP address): $ SHOW DISPLAY Device: WSA38: [super] Node: 16.20.99.10 Transport: TCPIP Server: 0 Screen: 0 On TRU64 Unix > echo $DISPLAY 16.20.99.10:0.0 If the display variable is not set on the ssh client, you can set it by using the following commands: On OpenVMS $ SET DISPLAY/CREATE/NODE=16.20.99.10/TRANSPORT=TCPIP Note that OpenVMS supports only LOCAL and TCPIP transports. For display using LOCAL transport, you must be logged in directly on the X11 server system, and X11 must be running. $ SET DISPLAY/CREATE/TRANSPORT=LOCAL On TRU64 Unix > setenv display 16.20.99.10:0.0 or for display on the local system: > setenv display :0.0 2) XAUTH not installed Make sure, that the OpenVMS system has xauth (X authentication) installed on the system. If it is not installed, you need to install DEC MOTIF V1.3 to install xauth. 3) X server or client not set up properly. Make sure that the X client is authenticated by the X server. Try running X client application on the X server and it should succeed. If not, then you may have to make appropriate changes for X applications to run on X server. --------------------------------------------------------------------------- Corrections for HP TCP/IP Services V5.4 BFS Images --------------------------------------------------------------------------- ECO 1 updates ------------- ECO A 23-DEC-2003 Alpha and VAX Problem: A binary file FTP'd from Unix to OpenVMS and then copied back to Unix via NFS is found to be a different size than the original, and a different size than reported via NFS. Deliverables: TCPIP$CFS_SHR.EXE V5.4-15A Reference: PTR 70-5-2350 / CFS.101076 / Req Id: GB_G07470 TCPIP_BUGS Note 2906.1 ECO B 23-DEC-2003 Alpha and VAX Problem: Using SFU or HUMMINGBIRD MAESTRO NFS clients, an attempt to edit an existing file on OpenVMS NFS server using Wordpad is unsuccessful. Messages such as the following are seen on OPCOM: %TCPIP-E-CFS_DATAFAIL, failed to write file data -TCPIP-I-CFS_FILEID, file DKA200:(10252,6,0) -TCPIP-I-CFS_CLUSTER, virtual blocks 1 through 1 -SYSTEM-F-NOPRIV, insufficient privilege or object protection violation Deliverables: TCPIP$CFS_SHR.EXE V5.4-15A Reference: PTR 70-5-2367 / CFS.102003 / Req Id: DE_G07830 TCPIP_BUGS Note 2974 ECO C 23-DEC-2003 Alpha and VAX Problem: Directories are not inheriting the default version limit from the parent directory, except with an OpenVMS client. Deliverables: TCPIP$CFS_SHR.EXE V5.4-15A Reference: PTR 70-5-2300 / CFS.99615 / Req Id: HPAQH0LHT TCPIP_BUGS Note 2996 PTR 70-5-2311 / CFS.99908 / Req Id: HPAQ403SF ECO D 23-DEC-2003 Alpha, IA64, and VAX Problem: ( 1) Performance issues ( 2) New directory and name cache inconsistencies ( 3) XQP returns SS$_UNSUPPORTED when FID_NUM is <= reserved files irregardless of what is in FID_NMX ( 4) Need access to a safe copy of the original argument list in dumps ( 5) Issues in file system's time management Deliverables: TCPIP$CFS_SHR.EXE V5.4-15A Reference: TCPIP_BUGS Note 3005 ECO E 23-DEC-2003 Alpha and VAX Problem: (1) If a mapped device was not mounted, the BFS mount routine ignored the error return from the $PARSE call and then failed later because of a variable not being correctly set by $PARSE. The BFS mount routine is called for the statfs NFS procedure, for the SHOW MAP command, and so forth. (2) The wrong time granularity was being set in the BFS mount routine. The time granularity is reported to clients in the reply to the fsinfo NFS procedure call. Deliverables: TCPIP$CFS_SHR.EXE V5.4-15A Reference: TCPIP_BUGS Note 2990 ECO F 23-DEC-2003 Alpha and VAX Problem: Directories in a container file system cannot be deleted either by UCP or by clients. The error message is "no such file". Deliverables: TCPIP$CFS_SHR.EXE V5.4-15A Reference: CFS.99613 / Req Id: HPAQH0KS8 TCPIP_BUGS Note 2830 ECO G 23-DEC-2003 Alpha, IA64, and VAX Problem: Latent support for future enhancements. Deliverables: TCPIP$UCP.EXE V5.4-15A Reference: PTR 70-5-2404 TCPIP_BUGS Note 3015 --------------------------------------------------------------------------- Corrections for HP TCP/IP Services V5.4 BIND_RESOLVER Images --------------------------------------------------------------------------- ECO 1 updates ------------- ECO A 18-NOV-2003 Alpha and VAX Problem: The getipnodebyaddr() routine sometimes returned the same structure twice, leading the application which called it to call freehostent() twice for the same block of memory. This led to memory corruption and subsequent anomalous behavior such as ACCVIO's following repeated getipnodebyaddr() calls for a host in the IPNODES.DAT file. Deliverables: TCPIP$IPC_SHR.EXE V5.4-15A Reference: PTR 30-5-434 TCPIP_BUGS Note 3010 --------------------------------------------------------------------------- Corrections for HP TCP/IP Services V5.4 FAILSAFE Images --------------------------------------------------------------------------- ECO 1 updates ------------- ECO A 21-NOV-2003 Alpha, IA64, and VAX Problem: 1) Phantom failure occurs on a quiet LAN where there is only one IP address configured on multiple interfaces. The workaround is to configure an IP address on at least one other interface or generate periodic broadcast traffic on the LAN (e.g. with OSPF hello packets). 2) The mapping between ifname and the OpenVMS device name is statically declared. If customers define their own ifname and OpenVMS device, then failSAFE will not start. The LAN failover device (LLA0) also has no mapping, since it was not included in the failSAFE mapping table in time for the first release. 3) A user-defined log file name can now be specified in the SYS$SYSDEVICE:[TCPIP$FSAFE]TCPIP$FAILSAFE.CONF configuration file. For file name syntax information, refer to the configuration file provided when failSAFE is configured for the first time. Deliverables: TCPIP$FAILSAFE.CONF TCPIP$FAILSAFE.EXE V5.4-15A Reference: UCX Note 10084 TCPIP_BUGS Note 3023 --------------------------------------------------------------------------- Corrections for HP TCP/IP Services V5.4 FTP_CLIENT Images --------------------------------------------------------------------------- ECO 1 updates ------------- ECO A 19-DEC-2003 Alpha and VAX Problem: [1] Unable to get ODS-5 files from V5.3 FTP server. For example: FTP> get NAME^_SPACE.TXT 550-Failed to open DISK:[DIR]NAME^^_SPACE.TXT; for input. 550 file not found A corollary to this problem is that mget (and wildcarded get) also fails on any ODS-5 filenames. [2] Unable to put files using '%' wildcards to a non-OpenVMS FTP server from V5.3 FTP client. For example: FTP> put *.*_%%%%%%%%;* %TCPIP-E-FTP_INPROCF, error processing input file DISK:[DIR]*.*_^%^%^%^%^%^%^%^%;* -RMS-E-FND, ACP file or directory lookup failed -SYSTEM-W-BADFILENAME, bad file name syntax [3] Unable to use '.' as a version separator when listing files on a V5.3 FTP server. For example: FTP> ls tcpip$ftp_server.log.* 200 PORT command successful. 150 Opening data connection for tcpip$ftp_server.log.* ... 550 file not found (Using ';' works, but some FTP clients do not accept ';' appearing in client commands.) All of these problems are new in V5.3 and worked fine in earlier versions. They all relate to COE/Unix functionality added to FTP in V5.2, which was released in V5.3 to the wider audience of OpenVMS Alpha customers under the guise of "FTP Server and FTP Client Support for UNIX Path Names." As a solution, two new logicals were introduced, TCPIP$FTP_COMPAT_REV (for client) and TCPIP$FTPD_COMPAT_REV (for server) that can be set to "5.1" to restore the TCPIP V5.1 and earlier file name / path name interpretation. Deliverables: TCPIP$FTP_CHILD.EXE V5.4-15A TCPIP$FTP_SERVER.EXE V5.4-15A TCPIP$FTP_CLIENT.EXE V5.4-15A Reference: PTR 70-5-2305 / CFS.99732 / Req Id: KAOB42626 TCPIP_BUGS Note 2976 PTR 70-5-2340 / CFS.100721 / Req Id: CH_G07347 PTR 70-5-2356 / CFS.101367 / Req Id: HPAQ604HH ECO B 19-DEC-2003 Alpha and VAX Problem: Unable to reconnect to server after prior idle disconnect timeout. The following sequence of commands fails: $ ftp FTP> open xxx (*** Wait for idle disconnect timeout ***) FTP> disconnect %TCPIP-E-FTP_NETERR, I/O error on network device -SYSTEM-F-CONNECFAIL, connect to network object timed-out or failed FTP> open xxx %TCPIP-E-FTP_NETERR, I/O error on network device -SYSTEM-S-NORMAL, normal successful completion Deliverables: TCPIP$FTP_CLIENT.EXE V5.4-15A Reference: PTR 70-5-2373 / CFS.102206 / Req Id: NL_G07910 / UCX Note 9917 TCPIP_BUGS Note 2983 ECO C 22-DEC-2003 Alpha and VAX Problem: FTP (VMS-to-VMS in VMS-Plus mode) doesn't transfer a file's Longest Record Length attribute. Deliverables: TCPIP$FTP_CLIENT.EXE V5.4-15A TCPIP$FTP_CHILD.EXE V5.4-15A Reference: PTR 70-5-2390 / CFS.103251 / Req Id: CH_G08326 / UCX Note 9965 TCPIP_BUGS Note 2998 --------------------------------------------------------------------------- Corrections for HP TCP/IP Services V5.4 FTP_SERVER Images --------------------------------------------------------------------------- ECO 1 updates ------------- ECO A 19-DEC-2003 Alpha and VAX Problem: FTP Server process fails with log showing ACCVIO occurred. Deliverables: TCPIP$FTP_SERVER.EXE V5.4-15A TCPIP$FTP_CHILD.EXE V5.4-15A Reference: PTR 70-5-2363 / CFS.101913 / Req Id: KAOB74175 / UCX Note 9893 TCPIP_BUGS Note 2941 ECO B 19-DEC-2003 Alpha and VAX Problem: [1] Unable to get ODS-5 files from V5.3 FTP server. For example: FTP> get NAME^_SPACE.TXT 550-Failed to open DISK:[DIR]NAME^^_SPACE.TXT; for input. 550 file not found A corollary to this problem is that mget (and wildcarded get) also fails on any ODS-5 filenames. [2] Unable to put files using '%' wildcards to non-OpenVMS FTP server from V5.3 FTP client. For example: FTP> put *.*_%%%%%%%%;* %TCPIP-E-FTP_INPROCF, error processing input file DISK:[DIR]*.*_^%^%^%^%^%^%^%^%;* -RMS-E-FND, ACP file or directory lookup failed -SYSTEM-W-BADFILENAME, bad file name syntax [3] Unable to use '.' as a version separator when listing files on a V5.3 FTP server. For example: FTP> ls tcpip$ftp_server.log.* 200 PORT command successful. 150 Opening data connection for tcpip$ftp_server.log.* ... 550 file not found (Using ';' works, but some FTP clients do not accept ';' appearing in client commands.) All of these problems are new in V5.3 and worked fine in earlier revisions. They all relate to COE/Unix functionality added to FTP in V5.2 which got released in V5.3 to the wider audience of OpenVMS Alpha customers under the guise of "FTP Server and FTP Client Support for UNIX Path Names". As a solution, two new logicals, TCPIP$FTP_COMPAT_REV (for client) and TCPIP$FTPD_COMPAT_REV (for server) that can be set to "5.1" to restore the TCPIP V5.1 and earlier file name / path name interpretation. Deliverables: TCPIP$FTP_CHILD.EXE V5.4-15A TCPIP$FTP_SERVER.EXE V5.4-15A TCPIP$FTP_CLIENT.EXE V5.4-15A Reference: PTR 70-5-2305 / CFS.99732 / Req Id: KAOB42626 TCPIP_BUGS Note 2976 PTR 70-5-2340 / CFS.100721 / Req Id: CH_G07347 PTR 70-5-2356 / CFS.101367 / Req Id: HPAQ604HH ECO C 22-DEC-2003 Alpha and VAX Problem: FTP (VMS-to-VMS in VMS-Plus mode) does not transfer a file's Longest Record Length attribute. Deliverables: TCPIP$FTP_CLIENT.EXE V5.4-15A TCPIP$FTP_CHILD.EXE V5.4-15A Reference: PTR 70-5-2390 / CFS.103251 / Req Id: CH_G08326 / UCX Note 9965 TCPIP_BUGS Note 2998 --------------------------------------------------------------------------- Corrections for HP TCP/IP Services V5.4 INET_V54 Images --------------------------------------------------------------------------- ECO 1 updates ------------- ECO A 18-FEB-2004 Alpha, IA64, and VAX Problem: (1) Receive failures lose quota. (2) Receive IOSB not compliant with documentation. Deliverables: TCPIP$INETDRIVER.EXE V5.4-15A Reference: PTR 70-5-2405 / CFS.103830 TCPIP_BUGS Note 3035 --------------------------------------------------------------------------- Corrections for HP TCP/IP Services V5.4 INSTALL Images --------------------------------------------------------------------------- ECO 1 updates ------------- ECO A 23-DEC-2003 Alpha, IA64, and VAX Problem: The TCPIP$DEFINE_COMMANDS.COM command procedure fails to define foreign commands for DHCP-related utility programs. For example, after running the command procedure: $ @sys$manager:tcpip$define_commands.com it results in no DHCP symbols: $ show symbol dhc* %DCL-W-UNDSYM, undefined symbol - check validity and spelling The command procedure should display the following: $ show symbol dhc* DHCPCONF == "$SYS$SYSTEM:TCPIP$DHCP_CLIENT_CONF.EXE" DHCPDBD*UMP == "$SYS$SYSTEM:TCPIP$DHCP_DBDUMP.EXE" DHCPDBMOD*IFY == "$SYS$SYSTEM:TCPIP$DHCP_DBMODIFY.EXE" DHCPDBREG*ISTER == "$SYS$SYSTEM:TCPIP$DHCP_DBREGISTER.EXE" DHCPDBSH*OW == "$SYS$SYSTEM:TCPIP$DHCP_DBSHOW.EXE" DHCP*GUI == "$SYS$SYSTEM:TCPIP$DHCP_GUI.EXE" DHCPSHOWDBS == "$SYS$SYSTEM:TCPIP$DHCP_SHOWDBS.EXE" . . . Deliverables: TCPIP$DEFINE_COMMANDS.COM Reference: TCPIP_BUGS Note 3003 ECO A 23-DEC-2003 Alpha, IA64, and VAX Problem: The TCPIP$NFS_SHUTDOWN.COM service shutdown command procedure fails to delete the following file-system related logical name tables: 1. TCPIP$CFS_FILESYSTEM_DIRECTORY 2. TCPIP$CFS_PATHNAME_DIRECTORY Deliverables: TCPIP$NFS_SHUTDOWN.COM Reference: TCPIP_BUGS Note 3016 ECO A 23-DEC-2003 Alpha, IA64, and VAX Problem: The TCPIP$STARTUP.COM command procedure corrupts the message help database search list (msglib$library) when adding a new path. Deliverables: TCPIP$STARTUP.COM Reference: PTR 30-13-340 TCPIP_BUGS Note 3009 ECO B 28-JAN-2004 Alpha, IA64, and VAX Problem: The TCPIP$IP6_SETUP.COM configuration procedure needs reworking to address the following: 1. 6to4 tunnels a. Support RFC 1918 (private addresses) for 6to4 tunnels b. Correct bugs detailed in the following PTRs: - PTR 30-13-228 - valid address prefixes are rejected when configuring 6to4 tunnels - PTR 30-13-251 - grammatical errors in configuration prompts - PTR 75-83-1108 - numerous DCL errors result when "?" is entered when configuring 6to4 tunnels c. Configure all routes required for 6to4 relay router 2. Automatic tunnels a. Correctly configure tunnel's endpoint 3. Configured (manual) tunnels a. Support IPv6 over IPv6 configured tunnels b. Support all attributes for configured tunnels (i.e., address prefixes) 4. Correct errors generated in IPv6 configuration and initialization files during IPv6 host/router configuration 5. Support defining manual routes 6. Enhance configuration summary for IPv6 hosts and routers Deliverables: TCPIP$IP6_SETUP.COM Reference: PTR 30-13-228 TCPIP_BUGS Note 3040 PTR 30-13-251 PTR 75-83-1108 ECO C 11-FEB-2004 All Problem: Version 5.1 and Version 5.3 of TCP/IP Services for OpenVMS imposed restrictions on the usage of non-alphanumeric characters in SNMP community names. With Version 5.4, these restrictions have been relaxed. However, a space is not accepted in an SNMP community name. In addition, a quotation mark (") specified as part of a community name might not be handled correctly by TCPIP$CONFIG.COM. A message warns the user to check the validity of the name with the SHOW CONFIGURATION SNMP command, and if necessary, to correct the name with the SET CONFIGURATION SNMP command. Deliverables: TCPIP$CONFIG.COM Reference: PTR 70-5-2389 / UCX Note 9967 TCPIP_BUGS Note 3039 ECO D 2-MAR-2004 Alpha, IA64, and VAX Problem: After IPv6 is configured with TCPIP$IP6_SETUP.COM, the TCPIP$STARTUP command procedure: 1. Cannot create the Neighbor Discovery Daemon process TCPIP$ND6HOST on a system configured as an IPv6 host 2. Cannot create the Router Daemon process TCPIP$IPRTRD on a system configured as an IPv6 router Deliverables: TCPIP$IP6_SETUP.COM Reference: PTR 30-13-347 TCPIP_BUGS Note 3064 --------------------------------------------------------------------------- Corrections for HP TCP/IP Services V5.4 IPC Images --------------------------------------------------------------------------- ECO 1 updates ------------- ECO A 18-NOV-2003 Alpha and VAX Problem: The getipnodebyaddr() routine sometimes returned the same structure twice, leading the application which called it to call freehostent() twice for the same block of memory. This led to memory corruption and subsequent anomalous behavior such as ACCVIO's following repeated getipnodebyaddr() calls for a host in the IPNODES.DAT file. Deliverables: TCPIP$IPC_SHR.EXE V5.4-15A Reference: PTR 30-5-434 TCPIP_BUGS Note 3010 ECO B 8-DEC-2003 Alpha and VAX Problem: Traceroute does not exit with proper status code or error message. Deliverables: TCPIP$TRACEROUTE.EXE V5.4-15A TCPIP$IPC_SHR.EXE V5.4-15B Reference: PTR ! / CFS.! / Req Id: ! / UCX Note ! TCPIP_BUGS Note 2985 ECO C 8-DEC-2003 Alpha and VAX Problem: A call to getaddrinfo() hangs Deliverables: TCPIP$IPC_SHR.EXE V5.4-15C Reference: PTR 30-5-423 TCPIP_BUGS Note 2829 --------------------------------------------------------------------------- Corrections for HP TCP/IP Services V5.4 KERNEL_NFS Images --------------------------------------------------------------------------- ECO 1 updates ------------- ECO A 27-JAN-2004 ALPHA, and VAX Problem: ( 1) Problems with "after" attributes on directory-modifying operations ( 2) Improper conversion of time to/from OpenVMS granularity ( 3) Add debugging/logging facilities ( 4) Configurable duplicates cache ( 5) Readdir-plus takes too long Deliverables: TCPIP$NFS_SERVER.EXE V5.4-15A TCPIP$NFS_SERVICES.EXE V5.4-15A Reference: TCPIP_BUGS Note 3006 ECO B 22-FEB-2004 Alpha, IA64, and VAX Problem: Build procedure change to remove image references to DECC$SHR_EV56. Deliverables: TCPIP$NFS_SERVER.EXE V5.4-15B TCPIP$NFSSTAT.EXE V5.4-15B Reference: TCPIP_BUGS Note 3056 --------------------------------------------------------------------------- Corrections for HP TCP/IP Services V5.4 KERNEL_RPC Images --------------------------------------------------------------------------- ECO 1 updates ------------- ECO A 27-JAN-2004 ALPHA, and VAX Problem: ( 1) Problems with "after" attributes on directory-modifying operations ( 2) Improper conversion of time to/from OpenVMS granularity ( 3) Add debugging/logging facilities ( 4) Configurable duplicates cache ( 5) Readdir-plus takes too long Deliverables: TCPIP$NFS_SERVER.EXE V5.4-15A TCPIP$NFS_SERVICES.EXE V5.4-15A Reference: TCPIP_BUGS Note 3006 --------------------------------------------------------------------------- Corrections for HP TCP/IP Services V5.4 KERNEL_VFS Images --------------------------------------------------------------------------- ECO 1 updates ------------- ECO A 28-JAN-2004 ALPHA, and VAX Problem: ( 1) Problems with "after" attributes on directory-modifying operations ( 2) Improper conversion of time to/from OpenVMS granularity ( 3) Add debugging/logging facilities ( 4) Configurable duplicates cache ( 5) Readdir-plus takes too long Deliverables: TCPIP$NFS_SERVER.EXE V5.4-15A TCPIP$NFS_SERVICES.EXE V5.4-15A Reference: TCPIP_BUGS Note 3006 --------------------------------------------------------------------------- Corrections for HP TCP/IP Services V5.4 LPD5 Images --------------------------------------------------------------------------- ECO 1 updates ------------- ECO A 23-DEC-2003 Alpha and VAX Problem: LPD does not respect wildcarded remote user communication proxies. Deliverables: TCPIP$LPD_SHR.EXE V5.4-15A Reference: PTR 70-5-2332 / CFS.100536 / Req Id: DE_G07268 TCPIP_BUGS Note 2973 ECO A 23-DEC-2003 Alpha and VAX Problem: TelnetSym does not report or log an error when there is no disk space available to write to the log file or the temporary relay file when configured to relay to an LPD queue. Deliverables: TCPIP$TELNETSYM.EXE V5.4-15A Reference: PTR 70-5-2306 / CFS.99733 / Req Id: KAOB42346 TCPIP_BUGS Note 2950 --------------------------------------------------------------------------- Corrections for HP TCP/IP Services V5.4 NET Images --------------------------------------------------------------------------- ECO 1 updates ------------- ECO A Alpha and VAX Problem: TCPTRACE does not trace outgoing IP packets when running the scaling kernel. Deliverables: TCPIP$INTERNET_SERVICES_PERF.EXE V5.4-15A PF Reference: TCPIP_BUGS Note 2980 ECO A Alpha and VAX and Itanium Problem: Two problems. 1. System crash (INCONSTATE, call to panic() from sbflush()) when running the scaling kernel and using DECnet/IP on multi-CPU systems. 2. Intermittent leaking of BG UCBs and their sockets when running the scaling kernel and using DECnet/IP on multi-CPU systems. Deliverables: TCPIP$INTERNET_SERVICES_PERF.EXE V5.4-15A PF TCPIP$INTERNET_SERVICES.EXE V5.4-15A TCPIP$INETACP_PERF.EXE V5.4-15A PF Reference: TCPIP_BUGS Note 2994 ECO A Alpha and VAX Problem: An unprivileged application can cause a crash at location UDP_OUTPUT+DC. Deliverables: TCPIP$INTERNET_SERVICES.EXE V5.4-15A TCPIP$INTERNET_SERVICES_PERF.EXE V5.4-15A PF Reference: PTR 30-13-336 TCPIP_BUGS Note 2995 ECO A Alpha and VAX Problem: Crash during TCP/IP shutdown when attempting to deallocate a structure (INET$FREE) that is not a true malloc structure. Deliverables: TCPIP$INETACP.EXE V5.4-15A TCPIP$INETACP_PERF.EXE V5.4-15A PF Reference: PTR 75-83-1556 TCPIP_BUGS Note 2997 ECO A Alpha and VAX Problem: TCPIP$INTERNET_SERVICES INVEXCEPTN crash during shutdown caused by $ TCPIP DISCONNECT DEVICE command. Deliverables: TCPIP$INTERNET_SERVICES.EXE V5.4-15A Reference: PTR 70-5-2380 / CFS.102586 / Req Id: GB_G08063 TCPIP_BUGS Note 2986 ECO A Alpha and VAX Problem: UDP applications such as PING may experience behavior in certain error scenarios not seen before with the V5.4 scaling kernel. For example, when attempting to ping a node for which we have no routes, traditionally one would expect to see an error such as: ping: sendto: no route to host But with the scaling kernel only a timeout error was seen. Deliverables: TCPIP$INTERNET_SERVICES_PERF.EXE V5.4-15A PF Reference: TCPIP_BUGS Note 3004 ECO A Alpha and VAX Problem: System crash after having disabled a user-written Listen Service. Deliverables: TCPIP$INETACP.EXE V5.4-15A TCPIP$INETACP_PERF.EXE V5.4-15A PF Reference: PTR 70-5-2394 / CFS.103337 TCPIP_BUGS Note 3011 ECO B Alpha and VAX Problem: System crash in SMP$CPU_SWITCH trying to switch to a non-existent CPU. Deliverables: TCPIP$INTERNET_SERVICES.EXE V5.4-15B TCPIP$INTERNET_SERVICES_PERF.EXE V5.4-15B PF Reference: TCPIP_BUGS Note 3024 ECO C Alpha and VAX Problem: System crash in SMP$CPU_SWITCH trying to switch to a non-existent CPU. Similar but not identical to previous problem. Deliverables: TCPIP$INTERNET_SERVICES.EXE V5.4-15C TCPIP$INTERNET_SERVICES_PERF.EXE V5.4-15C PF Reference: TCPIP_BUGS Note 3020 TCPIP_BUGS Note 3024 ECO D Alpha and VAX Problem: Two crash problems in the scaling kernel. First, a crash may occur in routine SORECEIVE_STREAM_KERNEL when the KVCI client specifies that it wants to read a specified number of bytes rather than all the data available in the Pseudo_SB. The client in this situation was INETDRIVER. The problem arose when we were asked to read 4 bytes of data and there was only one byte available. The code then went off the end of the mbuf chain trying to satisfy the request for 4 bytes. In the course of analyzing this first crash, two other less serious bugs were found. One caused incorrect behavior with respect to OOB data for KVCI clients, and the other causes a minor leakage of TCPIP_KRP structures in OOB data processing in routine INET_SORECEIVE_STREAM. Both of these lesser problems were also fixed. The second crash occurred because to a synchronization bug in INET_KVCI.C wherein an INETKVCI structure was prematurely deallocated. A thread in routine KVCI$$CLOSE_ASSOC set the INETKVCI$V_DELETE bit in the INETKVCI so as to indicate that the structure was available for deallocation. However, the thread in question still needed to use that structure. The setting of the bit was meant as a means of signaling to itself that the structure should be deallocated later. However, with the new parallelism available in the scaling kernel, a different thread executing in routine KVCI$$REPORT_EVENT_FORK noticed the bit set, and that thread proceeded to deallocate the structure from under the first thread. Deliverables: TCPIP$INTERNET_SERVICES.EXE V5.4-15D TCPIP$INTERNET_SERVICES_PERF.EXE V5.4-15D PF Reference: TCPIP_BUGS Note 3030 ECO D Alpha and VAX Problem: System shutdown crash. Deliverables: TCPIP$INTERNET_SERVICES_PERF.EXE V5.4-15D PF Reference: TCPIP_BUGS Note 3031 ECO D Alpha and VAX Problem: A previous ECO in this stream that fixed a system crash occurring after a user-written Listen Service was disabled was found to have a typing error in the modules edited for that fix. The error causes an inserted line of code to be off by one line. Deliverables: TCPIP$INTERNET_SERVICES_PERF.EXE V5.4-15D PF Reference: TCPIP_BUGS Note 3032 ECO E Alpha and VAX Problem: Applications such as SNMP may experience an Invalid Buffer error when making connections while using the scaling kernel. Deliverables: TCPIP$INTERNET_SERVICES_PERF.EXE V5.4-15E PF Reference: TCPIP_BUGS Note 3036 ECO F Alpha and VAX Problem: System crash during TCP/IP Shutdown. Deliverables: TCPIP$INTERNET_SERVICES.EXE V5.4-15F TCPIP$INTERNET_SERVICES_PERF.EXE V5.4-15F PF Reference: PTR 70-5-2437 / CFS.104761 TCPIP_BUGS Note 3037 ECO G Alpha and VAX Problem: Problem seen only with the scaling kernel and will result in a crash due either to pool exhaustion or to CPUSPINWAIT where the wait is for IOLOCK8. Deliverables: TCPIP$PWIPDRIVER.EXE TCPIP$INTERNET_SERVICES.EXE Reference: PTR 70-5-2455 / CFS.105464 TCPIP_BUGS Note 3044 ECO H Alpha and VAX Problem: In some circumstances, when running with the Scaling Kernel, Select or ATTNAST requests may fail. This was noticed on IA64 systems running with Sysgen parameter, VMSD2 set to 1, where POP and MONITOR fail. Deliverables: TCPIP$INTERNET_SERVICES_PERF.EXE V5.4-15H PF Reference: TCPIP_BUGS Note 3052 ECO I 25-FEB-2004 Alpha and VAX Problem: When running the scaling kernel and shutting down TCPIP, some behavior has changed. In particular, we were returning SS$_CANCEL status to some outstanding QIO requests rather than the SS$_SHUT that we used to return. With this update, we restore the previous return value. Note that this also corrects issues with the behavior of the HP DECwindows X display server after network shutdown. With the fix installed, the DECwindows X display server recovers and accepts connections over the TCPIP transport a short time after the network restarts. Deliverables: TCPIP$INTERNET_SERVICES_PERF.EXE V5.4-15I PF Reference: PTR 75-102-283 TCPIP_BUGS Note 3059 --------------------------------------------------------------------------- Corrections for HP TCP/IP Services V5.4 NETUTIL6 Images --------------------------------------------------------------------------- ECO 1 updates ------------- ECO A 8-DEC-2003 Alpha and VAX Problem: Traceroute not exiting with proper status code or error message. Deliverables: TCPIP$TRACEROUTE.EXE V5.4-15A TCPIP$IPC_SHR.EXE V5.4-15B Reference: PTR ! / CFS.! / Req Id: ! / UCX Note ! TCPIP_BUGS Note 2985 ECO B 8-DEC-2003 Alpha, Vax, IA64 Problem: TCPIP$IP6_SETUP.COM required TCP/IP to be started. Deliverables: TCPIP$IP6_TESTADDR.EXE V5.4-15B Reference: PTR 30-10-76 / CFS.! / Req Id: ! / UCX Note ! TCPIP_BUGS Note 3008 --------------------------------------------------------------------------- Corrections for HP TCP/IP Services V5.4 NTP4_SERVER Images --------------------------------------------------------------------------- The following NTP problem is fixed in V5.4 Problem: When running on certain high-performance Alpha systems, NTP may be unable to adjust the system clock; therefore, NTP will not be able to provide accurate timekeeping. When this happens, the following error message appears in the NTP log file: %SYSTEM-F-BADLOGIC, internal logic error detected VMS timekeeping is not working as expected - can't proceed Solution: This problem was corrected in the previous release of the product; however, the Version 5.4 Release Notes did not indicate the problem had been fixed. ECO 1 updates ------------- ECO A 5-DEC-2003 Alpha, VAX, and IA64 Problem: NTP bugs uncovered while tracking an IA64 issue. Deliverables: TCPIP$NTP.EXE V5.4-15A Reference: PTR ! / CFS.! / Req Id: ! / UCX Note ! TCPIP_BUGS Note 2992 ECO B 5-DEC-2003 Alpha, Vax, IA64 Problem: "volatile" bug fixed for IA64 Deliverables: TCPIP$NTP.EXE V5.4-15B Reference: PTR ! / CFS.! / Req Id: ! / UCX Note ! TCPIP_BUGS Note 3007 --------------------------------------------------------------------------- Corrections for HP TCP/IP Services V5.4 PWIP Images --------------------------------------------------------------------------- ECO 1 updates ------------- ECO A 22-DEC-2003 Alpha and VAX Problem: When PWIP is shut down, the system crashes at location PWIP_WRITE_C+001DC. Deliverables: TCPIP$PWIPDRIVER.EXE V5.4-15A Reference: TCPIP_BUGS Note 2984 ECO B 22-DEC-2003 Alpha and VAX Problem: While running DECnet/IP applications the system crashes with a corrupt INETKVCI$A_VCRP_FLINK/INETKVCI$A_VCRP_BLINK queue. Deliverables: TCPIP$PWIPDRIVER.EXE V5.4-15A Reference: PTR 75-83-1514 TCPIP_BUGS Note 2989.1 ECO C Alpha and VAX Problem: System crash if running scaling kernel and PATHWORKS is stopped. Deliverables: TCPIP$PWIPDRIVER.EXE V5.4-15C Reference: TCPIP_BUGS Note 3034 ECO D Alpha and VAX Problem: Problem seen only with the scaling kernel and will result in a crash due either to pool exhaustion or to CPUSPINWAIT where the wait is for IOLOCK8. Deliverables: TCPIP$PWIPDRIVER.EXE TCPIP$INTERNET_SERVICES.EXE Reference: PTR 70-5-2455 / CFS.105464 TCPIP_BUGS Note 3044 --------------------------------------------------------------------------- Corrections for HP TCP/IP Services V5.4 SMTP Images --------------------------------------------------------------------------- ECO 1 updates ------------- ECO A 10-DEC-2003 Alpha and VAX Problem: A hole exists in the anti-SPAM route-through check which allows a SPAMmer to trick the SMTP receiver into relaying SPAM. Deliverables: TCPIP$SMTP_RECEIVER.EXE V5.4-15A Reference: PTR 70-5-2370 / CFS.102136 / Req Id: GB_G07885 / UCX Note 9907 TCPIP_BUGS Note 2960 TCPIP_BUGS Note 2965 ECO B 26-JAN-2004 Alpha and VAX and IA64 Problem: The SMTP receiver does not check to see if the recipient email address in the RCPT TO SMTP protocol command is deliverable, for example that the user account exists on the system. This check is instead deferred to the processing of the mail message in the SMTP queue by the SMTP symbiont process. By this time your host has taken responibility for the message and if there is a problem delivering the message your host must bounce the message itself. This behavior, while not a bug, has become problematic with the advent of SPAM. The following scenario occurs. SPAM arrives on your host for a non-existent user and is bounced by your host's symbiont process to the email address in the SPAM's Return-Path: header. The SPAM's Return-Path header contains an invalid email address so the bounced SPAM is in turn bounced back to your host's postmaster account. The postmaster account's mail is forwarded to the SYSTEM account which means that the SYSTEM user must constantly separate these doubly bounced SPAMs from their valid email. To solve this problem the SMTP receiver has been changed to check to see if the recipient email address in the RCPT TO SMTP protocol command is deliverable. This solves the problem by not letting the SPAM for the unknown user onto your host in the first place. There is a new configurable boolean switch to turn this new feature on and off. The switch is called Symbiont-Checks-Deliverability and is entered in the SMTP.CONFIG SMTP configuration file. Setting this switch to TRUE preserves the old behavior - where the receiver does not check the deliverability of RCPT TO recipients, deferring to the symbiont. Setting Symbiont-Checks-Deliverability to FALSE turns on the new behavior, telling the receiver to check the deliverability of RCPT TO recipients itself. To preserve existing behavior this switch is defaulted to TRUE for TCP/IP Services Version 5.4. For future versions it will default to FALSE. Deliverables: TCPIP$SMTP_MAILSHR.EXE V5.4-15B TCPIP$SMTP_PARSESHR.EXE V5.4-15B TCPIP$SMTP_PARSESHR_TV.EXE (AXP ONLY) V5.4-15B TCPIP$SMTP_RECEIVER.EXE V5.4-15B TCPIP$SMTP_SFF.EXE V5.4-15B TCPIP$SMTP_SYMBIONT.EXE V5.4-15B Reference: PTR 30-14-77 TCPIP_BUGS Note 3043 --------------------------------------------------------------------------- Corrections for HP TCP/IP Services V5.4 SSH Images --------------------------------------------------------------------------- ECO 1 updates ------------- ECO A 16-JAN-2004 Alpha Problem: - Client does not yet have the server host key (file with name such as key_22_servername.pub in [.ssh2.hostkeys] subdirectory of user's sys$login) - User runs sftp or scp (the value for StrictHostkeyChecking in ssh2_Config can be yes, no, or ask) With version of decc$shr.exe on the support person's machine (V7.3-0), the following messages appeared: Received signal 10, SIGBUS: invalid access to memory objects. ssh_sigchld_real_callbackspecific fatal error condition Deliverables: TCPIP$SSH_SSH2.EXE V5.4-15A Reference: PTR 30-13-335 TCPIP_BUGS Note 3022 ECO A 16-JAN-2004 Alpha Problem: Hangs observerd with sftp when using: - put to an FreeBSD/OpenSSH server - ls when connected to a FreeBSD/OpenSSH server These errors occurred independently of each other. Deliverables: TCPIP$SSH_SSH2.EXE V5.4-15A Reference: PTR 30-13-300 TCPIP_BUGS Note 3025 PTR 30-13-143 ECO A 16-JAN-2004 Alpha Problem: SSH client takes inordinate amount of time (such as greater then 5 minutes) to time out when attempting to connect to a host name that does not resolve or on which the SSH server is not responding. Deliverables: TCPIP$SSH_SSH2.EXE V5.4-15A Reference: PTR 30-13-181 TCPIP_BUGS Note 3027 ECO A 16-JAN-2004 Alpha Problem: 1. 30-13-328: After starting an sftp2 client without connecting on the DCL command line, input is double echoed. This problem disappears after a sftp> open {remote} 2. 30-14-64: CTRL/C causes display of signal-handling error 3. 30-13-224: "exit" not present as sftp command Deliverables: TCPIP$SSH_SSH2.EXE V5.4-15A Reference: PTR 30-13-328 TCPIP_BUGS Note 3033 PTR 30-14-64 PTR 30-13-224 ECO B 23-JAN-2004 Alpha Problem: X11 forwarding on SSH was not working in the native mode. Deliverables: TCPIP$SSH_SSH2.EXE V5.4-15B TCPIP$SSH_SSHD2.EXE V5.4-15B Reference: PTR 30-13-279 TCPIP_BUGS Note 3041 ECO C 17-FEB-2004 All Problem: Some ssh session setup information showing up in "clear" Deliverables: TCPIP$SSH_SSHD2.EXE V5.4-15C Reference: PTR 30-14-90 TCPIP_BUGS Note 3049 ECO D 8-MAR-2004 Alpha Problem: SSH images rebuilt with correct include files. Deliverables: TCPIP$SSH_SCP2.EXE V5.4-15D TCPIP$SSH_SFTP-SERVER2.EXE V5.4-15D TCPIP$SSH_SFTP2.EXE V5.4-15D TCPIP$SSH_SSH-ADD2.EXE V5.4-15D TCPIP$SSH_SSH-AGENT2.EXE V5.4-15D TCPIP$SSH_SSH-KEYGEN2.EXE V5.4-15D TCPIP$SSH_SSH-SIGNER2.EXE V5.4-15D TCPIP$SSH_SSH2.EXE V5.4-15D TCPIP$SSH_SSHD2.EXE V5.4-15D Reference: TCPIP_BUGS Note 3068 --------------------------------------------------------------------------- Corrections for HP TCP/IP Services V5.4 TCPIPLIB Images --------------------------------------------------------------------------- ECO 1 updates ------------- ECO A 15-JAN-2004 Alpha, IA64, and VAX Problem: Network applications are unable to map internet interface names to OpenVMS network device names without having to resort to "static" tables. Hence, the customer-defined internet interface to OpenVMS network device mappings cannot be supported. Deliverables: None. Reference: TCPIP_BUGS Note 3028 ECO B 22-FEB-2004 Alpha, IA64, and VAX Problem: Functions PUTENV() and STRDUP() mistakenly exist in TCPIP$LIBRARY:TCPIP$LIB.OLB with a DECC$ prefix. This can cause link conficts with the C RTL. Deliverables: TCPIP$LIB.OLB Reference: PTR 30-14-90 TCPIP_BUGS Note 3051 ECO C 17-MAR-2004 Alpha Problem: Relink images to the TCPIP$LIB.OLB library provided with this ECO. Deliverables: TCPIP$CFS_SHR.EXE V5.4-15H TCPIP$FTP_CLIENT.EXE V5.4-15D TCPIP$FTP_CHILD.EXE V5.4-15D TCPIP$FTP_SERVER.EXE V5.4-15D TCPIP$IPC_SHR.EXE V5.4-15D TCPIP$IPC_SHR_EV56.EXE V5.4-15D TCPIP$LPD_RCV.EXE V5.4-15C TCPIP$LPD_SHR.EXE V5.4-15C TCPIP$LPD_SMB.EXE V5.4-15C TCPIP$LPD_UTILITIES.EXE V5.4-15C TCPIP$LPQ.EXE V5.4-15C TCPIP$LPRM.EXE V5.4-15C TCPIP$LPRSETUP.EXE V5.4-15C TCPIP$INETACP.EXE V5.4-15I TCPIP$INETACP_PERF.EXE V5.4-15I PF TCPIP$TRACEROUTE.EXE V5.4-15C TCPIP$NTP-GENKEYS.EXE V5.4-15C TCPIP$NTP.EXE V5.4-15C TCPIP$NTPDATE.EXE V5.4-15C TCPIP$NTPDC.EXE V5.4-15C TCPIP$NTPQ.EXE V5.4-15C TCPIP$NTPTRACE.EXE V5.4-15C TCPIP$NTP_RES_CHILD.EXE V5.4-15C TCPIP$PWIPACP.EXE V5.4-15E TCPIP$PWIPDRIVER.EXE V5.4-15E TCPIP$PWIPSHUT.EXE V5.4-15E TCPIP$TELNETSYM.EXE V5.4-15C TCPIP$TELNET.EXE V5.4-15B TCPIP$IPC_SHR.EXE V5.4-15D TCPIP$IPC_SHR_EV56.EXE V5.4-15D TCPIP$UCP.EXE V5.4-15B UCX$IPC_SHR.EXE V5.4-15D UCX$IPC_SHR_EV56.EXE V5.4-15D UCX$LPD_SMB.EXE V5.4-15C Reference: TCPIP_BUGS Note 3057 --------------------------------------------------------------------------- Corrections for HP TCP/IP Services V5.4 TELNET_CLIENT Images --------------------------------------------------------------------------- ECO 1 updates ------------- ECO A 24-NOV-2003 Alpha and VAX Problem: The TELNET> SHOW DEVICE command displays incorrect information for local and remote IPv4 addresses on TELNET devices. Deliverables: TCPIP$TELNET.EXE V5.4-15A Reference: PTR 70-5-2346 / CFS.101020 / Req Id: HPAQ601BD / UCX Note 9829 TCPIP_BUGS Note 2979 --------------------------------------------------------------------------- Corrections for HP TCP/IP Services V5.4 TELNET_SERVER Images --------------------------------------------------------------------------- ECO 1 updates ------------- ECO A 24-NOV-2003 Alpha and VAX Problem: [1] On V5.1/V5.3, a SSRVEXCEPT crash can occur in theTCPIP$TNDRIVER image when doing IO$_TTY_PORT_BUFIO | IO$M_TN_SENSEMODE with an output item list requesting TN$_NETWORK_DEVICE_NAME. On V5.4, while the potential for a crash does exist, the symptom is usually just extraneous information returned for the network device name, which can be seen in the TELNET> SHOW DEVICE/FULL output. [2] Build issue. The compiler is unable to locate header files that were not in the same directory as the source files being compiled. Deliverables: TCPIP$TNDRIVER.EXE V5.4-15A TCPIP$TNDRIVER_PERF.EXE V5.4-15A PF Reference: PTR 70-5-2376 / CFS.102120 / Req Id: AT_G07872 TCPIP_BUGS Note 2978 ECO B 12-Dec-2003 Alpha and VAX Problem: System crash in KVCI$$RECEIVE+00098. Deliverables: TCPIP$TNDRIVER.EXE V5.4-15B TCPIP$TNDRIVER_PERF.EXE V5.4-15B PF Reference: TCPIP_BUGS Note 3019 --------------------------------------------------------------------------- Corrections for HP TCP/IP Services V5.4 UCP Images --------------------------------------------------------------------------- ECO 1 updates ------------- ECO A 8-DEC-2003 Alpha, IA64, and VAX Problem: Latent support for future enhancements. Deliverables: TCPIP$UCP.EXE V5.4-15A Reference: PTR 70-5-2404 TCPIP_BUGS Note 3015 --------------------------------------------------------------------------- 7 COPYRIGHT AND DISCLAIMER: (C) Copyright 2004 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP and/or its subsidiaries required for possession, use, or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. Neither HP nor any of its subsidiaries shall be liable for technical or editorial errors or omissions contained herein. The information in this document is provided "as is" without warranty of any kind and is subject to change without notice. The warranties for HP products are set forth in the express limited warranty statements accompanying such products. Nothing herein should be construed as constituting an additional warranty. DISCLAIMER OF WARRANTY AND LIMITATION OF LIABILITY THIS PATCH IS PROVIDED AS IS, WITHOUT WARRANTY OF ANY KIND. ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR PARTICULAR PURPOSE, OR NON-INFRINGEMENT, ARE HEREBY EXCLUDED TO THE EXTENT PERMITTED BY APPLICABLE LAW. IN NO EVENT WILL HP BE LIABLE FOR ANY LOST REVENUE OR PROFIT, OR FOR SPECIAL, INDIRECT, CONSEQUENTIAL, INCIDENTAL OR PUNITIVE DAMAGES, HOWEVER CAUSED AND REGARDLESS OF THE THEORY OF LIABILITY, WITH RESPECT TO ANY PATCH MADE AVAILABLE HERE OR TO THE USE OF SUCH PATCH.