Release Notes for HP TCP/IP Services for OpenVMS V5.5
	Update ECO 3

	________________________________________________________________


	© 2008 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.


---------------------------------------------------------------------------
Known Problems and Restrictions
---------------------------------------------------------------------------

Reference: 30-14-195

        The dnssec_signzone utility can experience a hang when invoked via
        a foreign symbol, on both Alpha and Integrity.  The utility does
        not exhibit this behavior when run from the command line using
        'mcr' or when the -r option is used to specify a source of
        entropy.

Reference: 75-109-1614

        In SFTP, an "ls" command entered using a path in OpenVMS format
        displays with UNIX style formatting, e.g.:

        sftp> ls [.ssh_testfiles]
        ./ssh_testfiles
        ./ssh_testfiles/98277_SLF.Z;1

Reference: 30-14-196

        The NFS server is not supported on TCP/IP Services Version 5.5. 
        The feature was added with Version 5.6.

Reference: 30-15-53

        An IP address added to a tunnel interface cannot be seen with
        ifconfig.  The new address cannot be seen unless you do a netstat
        -rn.

Reference: 30-14-199

        On Integrity, different displays for LOCKD/STATD display different
        statuses:

        - The menu in TCPIP$CONFIG:
            11 - LOCKD/STATD  Enabled  Started 

        - TCPIP SHOW SERVICE
            Service    Port  Process          Address         State
            ...
            LOCKD     53212  TCPIP$LOCKD      0.0.0.0         Disabled
            ...
            STATD     53213  TCPIP$STATD      0.0.0.0         Enabled

Reference: 30-14-201

        COPY /FTP does not properly support ODS-5 filesystem files.

Reference: 30-14-203

        In SFTP, the "ls -R" command fails to handle subdirectories if the
        directory filename includes ODS-5 extended characters.

Reference: 30-14-204

        The sftp command:
             sftp> ls [.ssh_testfiles]*.*
        does not give a complete listing.

        The following commands work properly:
             sftp> ls [.ssh_testfiles]*.*;* 
             sftp> ls [.ssh_testfiles]*

Reference: 30-14-205

        The SFTP "get" command is not parsing version numbers to the file
        correctly.  For example, the following input gets a version of the
        file although the version number is invalid:

        sftp> get TCPIP$FTP_SERVER.LOG;-5000000

Reference: 30-14-206

        No error message appears with an SFTP "get" on a file with an
        invalid version number and also a wildcard character.

Reference: 30-14-207

        In SFTP, the lrm command fails with the wildcard character '*'.

        sftp> lrm *.*;*
        Command failed.
        sftp> lrm BIG_VFC.*;*
        Command failed.

Reference: customer contact

        Use of colon character in pathname for source and/or destination
        filename parameters to the SCP command may cause delay.

        Due to an overloading of the colon character (:) in SCP syntax
        to indicate a hostname and in OpenVMS as a path delimiter, what
        is intended to be a Open VMS logical name for a device or directory
        in an SCP file parameter may be checked  as a hostname first and
        passed to a DNS lookup.  Normally this is benign but this could
        incur an otherwise unexplainable wait in an environment
        experiencing DNS lookup delays.  To avoid the possibility of
        confusion use UNIX
 style filename syntax.

---------------------------------------------------------------------------
Corrections for HP TCP/IP Services V5.5 NFS Server Images
---------------------------------------------------------------------------
ECO 1 updates
-------------
19-Apr-2005	Alpha and IA64

	Problems:

	(1) Corrections to handling of mode, uid, gid, size, atime, mtime.

	(2) Corrections for VMS UIC when changing uid and/or gid.

	(3) Do not create a file with no access for the owner.

	(4) A chmod operation from a UNIX
 client results in an invalid
	date, which may make the file seem to disappear.

	(5) The NFS server leaks btree entries.

	Deliverables:

	TCPIP$CFS_SHR.EXE
	TCPIP$NFS_SERVER.EXE
	TCPIP$NFS_SERVICES.EXE
 
	Reference:

	TCPIP_BUGS Note 3117

20-Apr-2005	Alpha and IA64

	Problem:

	INVEXCPTN bugcheck at TCPIP$NFS_SERVICES+2FAE8, facility
	KERNEL_VFS module VFS_SUBR.C subroutine vn_ok_to_dealloc+0x48.

	Deliverables:

	TCPIP$NFS_SERVICES.EXE

	Reference:

	PTR 70-5-2653, TCPIP_BUGS Note 3303

ECO 2 updates
-------------
07-Nov-2005	Alpha and IA64

	Problem:

	Deleting a directory or file from an NFS container filesystem
	could trigger an ACCVIO or, when the SYSGEN parameter
	SYSTEM_CHECK was enabled, a system crash.
	
	Deliverables:

	TCPIP$CFS_SHR.EXE

	Reference:

	75-102-2181, 30-15-12

11-Nov-2005	Alpha and IA64

	Problem:

	A KP_INCONSTATE system crash sometimes occurred while importing a
	file into an NFS container.
	
	Deliverables:

	TCPIP$CFS_SHR.EXE

	Reference:

	30-15-61

30-Jan-2006	Alpha and IA64

	Problem:

	When using the TCP transport, the NFS server sometimes failed to
	send a packet, erroneously believing there had been a network
	error.  This led to a hung connection, because NFS does not
	retransmit packets over TCP.
	
	Deliverables:

	TCPIP$NFS_SERVICES.EXE

	Reference:

	70-5-2777, 70-5-2471, 70-5-2632, and 70-5-2633

15-Feb-2006	Alpha and IA64

	Problem:

	In certain cases, the NFS server neglected to write a file's
	updated size to disk, meaning that recently appended data did not
	appear.
	
	Deliverables:

	TCPIP$CFS_SHR.EXE

	Reference:

	70-5-2414, CFS-104151, TCPIP_BUGS Note 3332

04-Apr-2006	Alpha and IA64

	Problem:

	When using the UDP transport, the NFS server sometimes failed to
	send a packet, erroneously believing there had been a network
	error.  This led to sluggish performance, although the lost
	packet was eventually retried and delivered properly.
	
	Deliverables:

	TCPIP$NFS_SERVICES.EXE

	Reference:

	70-5-2790

11-Apr-2006	Alpha and IA64

	Problem:

	A system crash could occur while shutting down and unloading the
	NFS server.
	
	Deliverables:

	TCPIP$NFS_SERVICES.EXE

	Reference:

	75-3-8734, QXCM1000328495, TCPIP_BUGS Note 3436

22-Mar-2006	Alpha and IA64

	Problem:

	The NFS server, when a file had been appended by a means other
	than NFS, sometimes failed to re-read the updated data.
	
	Deliverables:

	TCPIP$CFS_SHR.EXE

	Reference:

	70-5-2913, QXCM1000315319, TCPIP_BUGS Note 3423

---------------------------------------------------------------------------
Corrections for HP TCP/IP Services V5.5 BIND_RESOLVER Images
---------------------------------------------------------------------------
ECO 1 updates
-------------
19-Apr-2005	Alpha and IA64

	Problem:

	Selection of MX records to route mails to destination does not work
        according to the preference values.  When multiple MX records from
        the DNS server are given and one of them has a preference value of
        32768 or 65535, then the MX record with that value will be used
        first instead of other MX records with lower preference values.

	Deliverables:

	TCPIP$ACCESS_SHR.EXE

	Reference:

	PTR 70-5-2772, TCPIP_BUGS Note 3335

ECO 2 updates
-------------
09-Sep-2005	Alpha and IA64

	Problem:

	Following a BIND resolver configuration change, lookups initiated
	via DECnet over IP continued to use the old configuration.  Users
	had to reboot or restart TCPIP to pick up new nameservers.
	
	Deliverables:

	TCPIP$IPC_SHR.EXE

	Reference:

	70-5-2859, Note 10738, TCPIP_BUGS Note 3345

---------------------------------------------------------------------------
Corrections for HP TCP/IP Services V5.5 FTP_CLIENT Images
---------------------------------------------------------------------------
ECO 1 updates
-------------
15-Apr-2005	Alpha and IA64

	Problem:

	FTP copies  between VMS system of large (multi-gigabyte)
	files to a disk with highwater marking could take a long time
	and make the disk inaccessable to other users. This fix makes
	FTP a better community member.  Depending upon the size of the
	file and the type of the output disk, file creation may
	still take time, but the time and impact to other users should
	be reduced.

	Deliverables:

	TCPIP$FTP_CLIENT.EXE

	Reference:

	TCPIP_BUGS Note 3292

ECO 3 updates
-------------
 3-Sep-2007	Alpha and IA64

	Problem:

	The FTP client did not properly construct wildcarded filenames.
	COPY /FTP TEST.EXE_OLD nodename"username password"::*.EXE
	created a file named "_.EXE" on the remote system.
	Also, COPY /FTP TEST.EXE_OLD nodename"username password"::FILE.*
	would create a file named "FILE._" on the remote system.
	
	Deliverables:

	TCPIP$FTP_CLIENT.EXE

	Reference:

	QXCM1000383582, QXCM1000435497, QXCM1000452204

27-Sep-2007	Alpha and IA64

	Problem:

	Entries made in the TCPIP$ETC:IPNODES.DAT file were not seen
	by the FTP client.

	Deliverables:

	TCPIP$FTP_CLIENT.EXE

	Reference:

	PTR 75-109-1540

---------------------------------------------------------------------------
Corrections for HP TCP/IP Services V5.5 FTP_SERVER Images
---------------------------------------------------------------------------
ECO 1 updates
-------------
17-Apr-2005	Alpha and IA64

	Problem:

	FTP writes garbage into the FTP anonymous log file when
	an anonymous user attempt to change working directory (CWD)
	fails.

	Deliverables:

        TCPIP$FTP_CHILD.EXE

	Reference:

	TCPIP_BUGS Note 3293

ECO 2 updates
-------------
19-Apr-2006	Alpha and IA64

	Problem:

	A command such as:
	
	COPY /FTP A.B remoteVMS::*.*;
	
	would lead to the creation of a file named "_._;"
	
	Users expected COPY /FTP to behave more like DECnet, using the
	original filename to construct an output filename in cases where
	the destination was specified using wildcards.
	
	Deliverables:

	TCPIP$FTP_CLIENT.EXE

	Reference:

	75-102-76, 70-5-2906, 70-5-2923, TCPIP_BUGS Note 3444

ECO 3 updates
-------------
 8-Mar-2007	Alpha and IA64

	Problem:

	The FTP server, upon receiving a USER command in a session that
	was already logged in, failed to return a proper error, leading
	to a hang.  It should send "503 User SMITH, is already logged
	in".	

	Deliverables:

	TCPIP$FTP_SERVER.EXE

	Reference:

	PTR 70-5-3087

23-Mar-2007	Alpha and IA64

	Problem:

	FTP did not understand "expanded" rooted logical name syntax.

	Deliverables:

	TCPIP$FTP_CLIENT.EXE
	TCPIP$FTP_SERVER.EXE

	References:

	PTR 70-5-2594, QXCM1000188905

10-May-2007	Alpha and IA64

	Problem:

	The FTP server terminates with an ACCVIO error when there are a
	lot of connections and disconnections.  The FTP server also gets
	error messages such as:

	session connection from 127.124.172.114 at 11-JAN-2007 18:42:08.42
	%SYSTEM-F-NOSLOT, no PCB available
	%TCPIP-E-FTP_CREPRC, failed to create a child process
	
	Deliverables:

	TCPIP$FTP_SERVER.EXE

	Reference:

	PTR's 70-5-3068 and 70-5-2879

 5-Oct-2007	Alpha and IA64

	Problem:

	The OpenVMS FTP client was echoing keyboard input associated with
	the Account (ACCT) command.  Because some FTP servers use the
	"account" as a secondary password, this raised security concerns.

	Deliverables:

	TCPIP$FTP_CLIENT.EXE

	Reference:

	QXCM1000372468

---------------------------------------------------------------------------
Corrections for HP TCP/IP Services V5.5 INSTALL/STARTUP Images
---------------------------------------------------------------------------
ECO 1 updates
-------------
20-May-2005	Alpha and IA64

	Problem:

	Customers using site specific startup and shutdown command
	procedures get "%DCL-W-IVVERB, unrecognized command verb"
	errors if they attempt to define/use symbols from within
	those procedures.

	Deliverables:

	TCPIP$STARTUP.COM
	TCPIP$SHUTDOWN.COM
	(and individual service STARTUP/SHUTDOWN procedures)

	Reference:

	PTR 70-5-2680, TCPIP_BUGS Note 3320

10-Jun-2005	Alpha and IA64

	Problem:

	Enable PPP (point to point protocol) serial line support
	on Alpha and IA64.  NOTE: SLIP is no longer supported.

	Deliverables:

	TCPIP$INET_STARTUP.COM
	TCPIP$INET_SHUTDOWN.COM
	(related change in NET and UCP components, omitted below)

	Reference:

	TCPIP_BUGS Note 3334

---------------------------------------------------------------------------
Corrections for HP TCP/IP Services V5.5 NET (Kernel) Images
---------------------------------------------------------------------------
ECO 1 updates
-------------
28-Oct-2004	Alpha and IA64

	Problem:

	An accept request with a bad parameter can lead to a
        system crash.

	Deliverables:

	TCPIP$INTERNET_SERVICES.EXE

	Reference:

	PTR 75-102-1984, TCPIP_BUGS Note 3221

15-Nov-2004	Alpha and IA64

	Problem:

	Crash (INCONSTATE) (call to panic()) with the sb_cc
	field of the receive sockbuf non-zero.

	Deliverables:

	TCPIP$INTERNET_SERVICES.EXE

	Reference:

	PTR 70-5-2598, TCPIP_BUGS Note 3231

03-Dec-2004	Alpha and IA64

	Problem:

	System crash on shutdown, TCPIP$INETACP+529C0.

	Deliverables:

	TCPIP$INTERNET_SERVICES.EXE

	Reference:

	TCPIP_BUGS Note 3240

24-Jan-2005	Alpha and IA64

	Problems:

	(1) System crash with the UCB$L_LINK field of a BG UCB
	containing the value -1.  Other symptoms are possible
	corruption of OpenVMS lookaside lists, notably the ones
	for blocks of length C0 hex and 500 hex.

	(2) Crash in routine, INET_QUEUE_TCPIP_KRP called from
	WAKEUP() (INET_MAIN.MAR) trying to queue a TCPIP_KRP with
	an invalid address.

	Deliverables:

	TCPIP$INTERNET_SERVICES.EXE

	Reference:

	70-5-2700, TCPIP_BUGS Note 3254

07-Feb-2005	Alpha and IA64

	Problem:

	System crash or system hang with I/O Post requests
	building up on one of the per CPU queues with no
	software interrupt being generated.

	Deliverables:

	TCPIP$INTERNET_SERVICES.EXE

	Reference:

	PTR 70-3-8277, TCPIP_BUGS Note 3255

14-Feb-2005	Alpha and IA64

	Problem:

	It was not possible to identify where the standys addresses
	were configured, without visiting each node in the cluster.
	Now with "ifconfig -v", the display will identify if there
	are standbys configured, and if so, the node on which they
	are configured.

	Deliverables:

	TCPIP$INETACP.EXE
	TCPIP$IFCONFIG.EXE

	Reference:

	TCPIP_BUGS Note 3256

23-Mar-2005	Alpha and IA64

	Problem:

	Unsupported "ifconfig filter" functionality was broken.  (OK,
	you caught us.  Sometimes, we do maintain unsupported features.)

	Deliverables:

	TCPIP$INTERNET_SERVICES.EXE

	Reference:

	PTR 70-5-2731, TCPIP_BUGS Note 3282

30-Mar-2005	Alpha and IA64

	Problem:

	Connections made using INET device may hang.

	Deliverables:

	TCPIP$INETDRIVER.EXE

	Reference:

	PTR 70-5-2751, TCPIP_BUGS Note 3284

15-Apr-2005	IA64 only

	Problem:

	On IA64, large writes to a socket (over 10716 bytes) where
	the user buffer is located in P2 user space will not be
	properly copied to system space and incorrect data will
	be transmitted.

	Deliverables:

	TCPIP$INTERNET_SERVICES.EXE

	Reference:

	PTR 75-13-1427, TCPIP_BUGS Note 3291

26-Apr-2005	Alpha and IA64

	Problem:

	Select can fail repeatedly with SS$_DEVACTIVE (EBUSY) errors.

	Deliverables:

	TCPIP$INTERNET_SERVICES.EXE

	Reference:

	PTR 70-5-2795, TCPIP_BUGS Note 3308

10-May-2005	Alpha and IA64

	Problem:

	System crashes with CLUEXIT or CPUSPINWAIT.

	Deliverables:

	TCPIP$INTERNET_SERVICES.EXE

	Reference:

	PTR 70-5-2797, TCPIP_BUGS Note 3315

05-May-2005	Alpha and IA64

	Problem:

	System crash, INVEXCEPTN, with a failing PC of SOQMVQUE_C+00358.

	Deliverables:

	TCPIP$INTERNET_SERVICES.EXE

	Reference:

	QXCM1000235381, TCPIP_BUGS Note 3311

13-May-2005	Alpha and IA64

	Problem:

	System crash, INCONSTATE (call to panic() from sbdrop())
	for an RLOGIN socket.

	Deliverables:

	TCPIP$TNDRIVER.EXE

	Reference:

	PTR 30-23-384, TCPIP_BUGS Note 3316

18-May-2005	Alpha and IA64

	Problem:

	IPv6 links do not handle gigabit jumbo frames.

	Deliverables:

	TCPIP$INTERNET_SERVICES.EXE

	Reference:

	TCPIP_BUGS Note 3319

17-Jun-2005	Alpha and IA64

	Problem:

	Memory leaks when scatter/gather operations are aborted.

	Deliverables:

	TCPIP$INTERNET_SERVICES.EXE

	Reference:

	PTR 70-5-2820, TCPIP_BUGS Note 3328

22-Jun-2005	Alpha and IA64

	Problem:

	System crash at SOQMVQUE_C+00358

	Deliverables:

	TCPIP$INTERNET_SERVICES.EXE

	Reference:

	QXCM1000243420, TCPIP_BUGS Note 3327

28-Jun-2005	Alpha and IA64

	Problem:

	Process TCPIP$INETACP runs out of BYTCNT quota.

	Deliverables:

	TCPIP$INETACP.EXE

	Reference:

	TCPIP_BUGS Note 3333

30-Jun-2005	Alpha and IA64

	Problem:

	failSAFE IP was not very graceful in the case of single
	address failover.

	Deliverables:

	TCPIP$INTERNET_SERVICES.EXE

	Reference:

	TCPIP_BUGS Note 3309

10-Jul-2005	Alpha and IA64

	Problem:

	Incorporate selected Tru64 UNIX BL26 remedial patches
	relating to TCP ISS and MSS, as well as to the reporting
	of last-minute pending errors upon socket closure and
	correcting a control mbuf memory leak.

	Deliverables:

	TCPIP$INTERNET_SERVICES.EXE

	Reference:

	PTR 10-Jul-2005, TCPIP_BUGS Note 3337

ECO 2 updates
-------------
19-Jul-2005	Alpha and IA64

	Problem:

	Pool leak of INETKVCI structures.
	
	Deliverables:

	TCPIP$INTERNET_SERVICES.EXE
	TCPIP$INETDRIVER.EXE

	Reference:

	70-5-2843, QXCM1000278813

27-Jul-2005	Alpha and IA64

	Problem:

	Multicast addresses did not failover to the standby interface.
	This would result in the multicast receiver no longer seeing the
	datagrams, because the standby interface was not made a member of
	the multicast group.
	
	Additionally, if a multicast listener was active on an inteface
	and a new primary address was added to that interface, then it
	would no longer receive multicast datagrams.
	
	NOTE: For the multicast sender, in the event that no addresses are
	active on the system at the time of a sendto(), it will return
	EADDRNOTAVAIL.  Because failSAFE IP deletes the address on the
	failed interface, then recreates it on a standby, there is a small
	window where that address is not configured.  If a sendto() occurs
	inside this window, it will return EADDRNOTAVAIL.  To avoid this
	situation, configure active addresses on each interface or modify
	the application to deal with this condition.
	
	Also note that if the multicast sender sets the IP_MULTICAST_IF
	socket option, which forces the kernel to use a specific interface
	for outgoing datagrams, and that interface fails, then outgoing
	datagrams will not failover to the standby interface, even if the
	address has. In this case, modifying the application to reissue
	the IP_MULTICAST_IF when sendto() returns EADDRNOTAVAIL will
	redirect it to the new interface.
	
	You can avoid these issues for the multicast sender by not setting
	the IP_MULTICAST_IF socket option and configuring each interface
	with an active IP address, as well as standby addresses.
	
	DEVELOPER NOTE: Applications that listen on multicast addresses
	will now continue to receive after a failSAFE IP event.
	
	CAUTION: This does not affect the send side if it sets the
	IP_MULTICAST_IF socket option.  That is, if the only address on
	that interface fails over to a standby, then the sender will see
	EADDRNOTAVAIL and will need to reissue the setsockopt to refer to
	the standby interface.  Wherever possible, HP recommends that
	a multicast sender not set the IP_MULTICAST_IF socket option
	in a failSAFE configuration.
	
	Deliverables:

	TCPIP$INTERNET_SERVICES.EXE

	Reference:

	70-5-2692, TCPIP_BUGS Note 3339

12-Aug-2005	Alpha and IA64

	Problem:

	In configurations where the primary address is not protected with
	a standby address, the multicast address does not move after a
	failover event.
	
	Deliverables:

	TCPIP$INTERNET_SERVICES.EXE

	Reference:

	70-5-2692 (addendum), TCPIP_BUGS Note 3339

6-Sep-2005	Alpha and IA64

	Problem:

	After a loss of synchronization in the kernel, the system crashed.
	A number of footprints could result.
	
	If the bugcheck code is INCONSTATE, then there will probably be
	a broken link in the (BG) i/o database (ucb$l_link = -1); if the
	bugcheck code is INVEXCEPTN, the failing instruction is often
	INSQUEL/D.
	
	Deliverables:

	TCPIP$INTERNET_SERVICES.EXE

	Reference:

	70-5-2851, QXCM1000284947, TCPIP_BUGS Note 3343

6-Sep-2005	Alpha and IA64

	Problem:

	ARP request packets were ignored when they contained an
	address associated with a permanent ARP entry.  The problem
	was introduced in the TCPIP V5.3 timeframe.
	
	Deliverables:

	TCPIP$INTERNET_SERVICES.EXE

	Reference:

	70-5-2858, QXCM1000287199, Note 9995, TCPIP_BUGS Note 3344

29-Nov-2005	Alpha and IA64

	Problem:

	Shutting down TCPIP while TCPDUMP was running would trigger a
	system crash.
	
	Deliverables:

	TCPIP$INTERNET_SERVICES.EXE

	Reference:

	30-15-113, TCPIP_BUGS Note 3372

10-Jan-2006	Alpha and IA64

	Problem:

	TCP/IP shutdown might stall on some systems where dynamic routing
	is enabled.
	
	Deliverables:

	TCPIP$INTERNET_SERVICES.EXE

	Reference:

	70-5-2888, QXCM1000306972, Note 3391

16-Jan-2006	Alpha and IA64

	Problem:

	A SSRVEXCEPT system crash at INET_SENSE_SOCKET_COUNTERS_C+00254
	(Alpha) could occur because of inadequate synchronization when a
	user process attempted to access current values for BG device
	counters.
	
	Deliverables:

	TCPIP$INTERNET_SERVICES.EXE

	Reference:

	70-5-2885, QXCM1000306081, Note 10810, TCPIP_BUGS Note 3390

21-Feb-2006	Alpha and IA64

	Problem:

	While attempting to shut down TCPIP, a process sometimes got stuck
	in LEF state.
	
	Deliverables:

	TCPIP$INETACP.EXE

	Reference:

	75-109-894, NONE, TCPIP_BUGS Note 3406

21-Feb-2006	Alpha and IA64

	Problem:

	A POOLCHECK crash occurred with current image java$java.exe.
	
	Deliverables:

	TCPIP$INTERNET_SERVICES.EXE

	Reference:

	75-109-1171, NONE, TCPIP_BUGS Note 3407

25-Feb-2006	Alpha and IA64

	Problem:

	The TCPIP$INET_ACP process hung during TCPIP shutdown.
	
	Deliverables:

	TCPIP$INTERNET_SERVICES.EXE

	Reference:

	75-5-2888, QXCM1000306972, TCPIP_BUGS Note 3409

10-Mar-2006	Alpha and IA64

	Problem:

	A PPP interface was deleted during or soon after its creation.
	
	Deliverables:

	TCPIP$INTERNET_SERVICES.EXE

	Reference:

	TCPIP_BUGS Note 3418

11-Apr-2006	Alpha and IA64

	Problem:

	An application process could hang (usually for 10 minutes or
	less) in MUTEX state while attempting to close a socket upon
	which the LINGER option had been set.
	
	Deliverables:

	TCPIP$INTERNET_SERVICES.EXE

	Reference:

	75-5-2912, QXCM1000315296, TCPIP_BUGS Note 3435

20-Apr-2006	Alpha and IA64

	Problem:

	A system crash occurred while closing a socket.
	
	Deliverables:

	TCPIP$INTERNET_SERVICES.EXE

	Reference:

	30-15-128, TCPIP_BUGS Note 3446

24-Jul-2006	Alpha and IA64

	Problem:

	Various system crashes were reported, showing evidence of nonpaged
	pool corruption.
	
	Deliverables:

	TCPIP$INTERNET_SERVICES.EXE

	Reference:

	75-109-1814, QXCM1000349964, QXCM1000330020, QXCM1000352590

1-Dec-2006	Alpha and IA64

	Problem:

	SACK retransmission sometimes resulted in too much data being
	retransmitted; that is, it retransmitted beyond the SACK Left
	Edge, SLE.
	
	Deliverables:

	TCPIP$INTERNET_SERVICES.EXE

	Reference:

	70-5-3025, Note 10983

ECO 3 updates
-------------
 6-Mar-2007	Alpha and IA64

	Problem:

	While it was possible to set the socket options, it was not
	possible to sense two of them: SHARE and FULL_DUPLEX_CLOSE.

	Deliverables:

	TCPIP$INTERNET_SERVICES.EXE

	Reference:

	PTR 70-5-3086, QXCM1000401933, TCPIP_BUGS Note 3545

13-Mar-2007	Alpha and IA64

	Problem:

	Setting the inet sysconfig parameter "ovms_printf_to_opcom"
	may cause a crash, at TCPIP start, on any version of the scaling
	kernel.  The crash will happen if the startup code attempts to
	print something, for instance:
	
	sysconfigtab: attribute sobacklog_hiwat in subsystem socket
	can't be configured

	Deliverables:

	TCPIP$INTERNET_SERVICES.EXE

	Reference:

	PTR 30-15-127, TCPIP_BUGS Note 3548

13-Mar-2007	Alpha and IA64

	Problem:

	A system crash occurred due to a coded bugcheck in routine
	m_copym() because an unexpected negative offset was
	calculated during SACK (selective acknowledgement)
	processing.

	Deliverables:

	TCPIP$INTERNET_SERVICES.EXE

	References:

	PTR 70-5-3066, 70-5-3071, 70-5-3073,
	QXCM1000391369, QXCM1000394833, QXCM1000395526,
	TCPIP_BUGS Note 3549

20-Mar-2007	Alpha and IA64

	Problem:

	The system occasionally crashed or created an ACK storm during
	some circumstances involving packet loss and SACK processing.

	Deliverables:

	TCPIP$INTERNET_SERVICES.EXE

	References:

	PTR 70-5-3073, 70-5-3025, 70-5-3066, 70-5-3071

30-Apr-2007	Alpha and IA64

	Problem:

	The system crashed during TCPIP shutdown followed by startup.

	Deliverables:

	TCPIP$INTERNET_SERVICES.EXE

	Reference:

	PTR 75-118-18, TCPIP_BUGS Note 3575

27-Jun-2007	Alpha and IA64

	Problem:

	Multicast traffic could be lost when aggressive IGMP snooping was
	enabled on a switch.  This was the result of OpenVMS delaying IGMP
	reports when the IGMP query specified a maximum response time less
	than 10 seconds.

	Deliverables:

	TCPIP$INTERNET_SERVICES.EXE

	Reference:

	QXCM1000419821

19-Jul-2007	Alpha and IA64

	Problem:

	Certain unusual application behavior involving TCP Out Of Band
	data could trigger a system crash.
	
	Deliverables:

	TCPIP$INTERNET_SERVICES.EXE

	Reference:

	QXCM1000424026, TCPIP_BUGS Note 3601

26-Jan-2008	IA64 only

	Problem:

	On OpenVMS Integrity systems, the TCPIP START ROUTING command
	failed to actually start a dynamic routing process (ROUTED or
	GATED).
	
	Deliverables:

	TCPIP$INETACP.EXE

	Reference:

	TCPIP_BUGS Note 3643

---------------------------------------------------------------------------
Corrections for HP TCP/IP Services V5.5 TELNET_CLIENT Images
---------------------------------------------------------------------------
ECO 1 updates
-------------
11-Mar-2005	IA64

	Problem:

	On IA64, a ^Y $exit during an initial Telnet client
	connection would ignore the interruption and wait until
	the connection had timed out.

	Deliverables:

	TCPIP$TELNET.EXE

	Reference:

	PTR 75-107-269, TCPIP_BUGS Note 3275

ECO 2 updates
-------------
26-Sep-2006	Alpha and IA64

	Problem:

	The peer hostname for outbound TN devices was not always set
	correctly by the TELNET client.
	
	Deliverables:

	TCPIP$TELNET.EXE

	Reference:

	70-5-2916, QXCM1000316661, TCPIP_BUGS Note 3502

---------------------------------------------------------------------------
Corrections for HP TCP/IP Services V5.5 TELNET_SERVER Images
---------------------------------------------------------------------------
ECO 1 updates
-------------
 9-May-2005	Alpha and IA64

	Problem:

	Crash when pool was exhausted due to failure to allocate a
	VCRP when closing a VCI association.

	Deliverables:

	TCPIP$TNDRIVER.EXE

	Reference:

	QuIX UXCM1000240318, TCPIP_BUGS Note 3313

 7-Jun-2005	Alpha and IA64

	Problem:

	When using outbound TELNET pseudo devices to connect to remote
	listener ports on a host that is not reachable, the used
	bg-devices were not always released.  This could result in the
	TCPIP$INETACP-process running out of channels, or to reach the
	limit of systemwide BG devices.

	Deliverables:

	TCPIP$TNDRIVER.EXE

	Reference:

	QuIX UXCM1000240318, TCPIP_BUGS Note 3323

ECO 2 updates
-------------
26-Oct-2005	Alpha and IA64

	Problem:

	Device ownership for inbound TELNET users was not properly set.
	
	Deliverables:

	TCPIP$INETACP.EXE
	TCPIP$INTERNET_SERVICES.EXE

	Reference:

	70-5-2865, QXCM1000292931, TCPIP_BUGS Note 3359

22-Mar-2006	Alpha and IA64

	Problem:

	The TELNET server dropped characters when large blocks of text were
	entered via cut-and-paste.
	
	Deliverables:

	TCPIP$TNDRIVER.EXE

	Reference:

	QXCM1000321354, TCPIP_BUGS Note 3422

20-Apr-2006	Alpha and IA64

	Problem:

	The TELNET server triggered a system crash in KVCI$$OPEN_ASSOC
	and/or KVCI$$GET_ADDR_INFO due to a synchronization fault.
	
	Deliverables:

	TCPIP$TNDRIVER.EXE

	Reference:

	70-5-2940, QXCM1000328598, TCPIP_BUGS Note 3445

---------------------------------------------------------------------------
Corrections for HP TCP/IP Services V5.5 INETDRIVER Images
---------------------------------------------------------------------------
ECO 1 updates
-------------
25-Jan-2005	Alpha and IA64

	Problems:

	(1) IO$_RECEIVE data structure was 20 bytes but should be 18.

	(2) IO$_RECEIVE was returning 0 for peer IP address.

	(3) IO$_RECEIVE improperly truncated user data at 20 bytes.

	Deliverables:

	TCPIP$INETDRIVER.EXE

	Reference:

	QuIX QXCM1000197607, TCPIP_BUGS Note 3253

ECO 3 updates
-------------
 5-Jun-2007	Alpha and IA64

	Problem:

	Users of the SRI QIO interface (INETDRIVER) reported a system
	crash with INVEXCEPTN in routine KVCI$$GENERATE_ASSOC_ID,
	following a shutdown and restart of the INETDRIVER component.
	
	Deliverables:

	TCPIP$INETDRIVER.EXE

	Reference:

	QXCM1000428905, TCPIP_BUGS Note 3589

---------------------------------------------------------------------------
Corrections for HP TCP/IP Services V5.5 SYSCONFIG Images
---------------------------------------------------------------------------
ECO 3 updates
-------------
 9-Sep-2007	Alpha and IA64

	Problem:

	The sysconfigdb command generated a "%SYSTEM-F-SSFAIL, system
	service failure" exception instead of exiting gracefully upon
	detecting an error.

	Deliverables:

	TCPIP$SYSCONFIGDB.EXE

	Reference:

	QXCM1000441503

---------------------------------------------------------------------------
Corrections for HP TCP/IP Services V5.5 NTP Images
---------------------------------------------------------------------------
ECO 1 updates
-------------
03-Dec-2004	Alpha and IA64

	Problem:

	The NTPDC 'peers' command or '-p' command line option would hang.

	Deliverables:

	TCPIP$NTPDC.EXE

	Reference:

	PTR 30-14-134 TCPIP_BUGS Note 3239

23-Mar-2005	Alpha and IA64

	Problem:

	The broadcast feature in NTP was not working on a system with
	IPv6 enabled.

	Deliverables:

	TCPIP$NTP.EXE

	Reference:

	PTR 30-15-37, TCPIP_BUGS Note 3281

23-Mar-2005	Alpha and IA64

	Problem:

	NTPDATE appears to step time when -d is specified.  With "-d",
	this utility prints useful information for debugging and does not
	change the time.

	Deliverables:

	TCPIP$NTPDATE.EXE

	Reference:

	PTR 30-15-35, TCPIP_BUGS Note 3279

ECO 2 updates
-------------
15-Sep-2005	Alpha and IA64

	Problem:

	The NTP Server stopped creating log files when the version limit
	on the file or directory was reached.
	
	Previously, the NTP server would automatically purge log files
	when NTP was started (/KEEP=5).  As long as NTP remained running,
	another purge was not performed.  With this release, the NTP
	server will still purge log files at NTP startup time.  It will
	also automatically purge log files once per day before creating
	the new daily log file.
	
	Deliverables:

	TCPIP$NTP.EXE

	Reference:

	70-5-2671, TCPIP_BUGS Note 3350

03-Apr-2006	Alpha and IA64

	Problem:

	The NTPDATE utility generated an ACCVIO when the NTP service
	was not defined.	

	Deliverables:

	TCPIP$NTPDATE.EXE

	Reference:

	75-109-1393, TCPIP_BUGS Note 3432

04-Dec-2006	Alpha and IA64

	Problem:

	The NTPDC utility incorrectly displayed the 'keyid' as optional
	in the usage and help statements.
	
	Deliverables:

	TCPIP$NTPDC.EXE

	Reference:

	TCPIP_BUGS Note 3519

ECO 3 updates
-------------
21-Mar-2007	Alpha and IA64

	Problem:

	NTP does not synchronize during the repeated hour at the summer
	to winter time change.

	Deliverables:

	TCPIP$NTP.EXE

	Reference:

	PTR 70-5-3076, TCPIP_BUGS Note 3555

---------------------------------------------------------------------------
Corrections for HP TCP/IP Services V5.5 IPC Images
---------------------------------------------------------------------------
ECO 1 updates
-------------
28-Mar-2005	Alpha and IA64

	Problem:

	Long timeout values (such as 30 minutes) resulted in an overflow,
	causing select() to return much earlier than intended.

	Deliverables:

	TCPIP$IPC_SHR.EXE

	Reference:

	PTR 30-14-186, TCPIP_BUGS Note 3283

28-Mar-2005	Alpha (with IA64 caveat)

	Problem:

	In V5.5, a symbol vector for the routine socketpair was
	inappropriately inserted in the IPC options file.  This caused
	applications that were linking directly against TCPIP$IPC_SHR
	to ACCVIO when run on an OpenVMS V8.2 system.  This problem has
	been corrected and will allow those previously linked programs
	to run on recent versions of OpenVMS.

	Please be advised that HP does not recommend or support linking
	directly against the TCPIP$IPC_SHR shareable image.  Note also
	that any images linked againt the originally-released version of
	TCPIP$IPC_SHR on either platform will now need to be re-linked.

	Deliverables:

	TCPIP$IPC_SHR.EXE

	Reference:

	PTR 75-13-1440, TCPIP_BUGS Note 3310

ECO 2 updates
-------------
17-Jun-2005	Alpha and IA64

	Problem:

	Applications should normally not be linked against the
	UCX$IPC_SHR or TCPIP$IPC_SHR image; however, some customer
	applications are linked that way.  Some are even linked against
	the IPC_SHR image found in an ECO kit.
	
	To properly support applications built in this unusual way, the
	GSMATCH minor version in the TCPIP$IPC_SHR image should be no less
	than the highest previously-shipped number.  Unfortunately,
	although the minor version reched 8 in the V5.3 ECO stream, it
	shipped at 7 in the V5.4 stream.  We are increasing the minor
	ident to accommodate such images.
	
	Deliverables:

	TCPIP$IPC_SHR.EXE

	Reference:

	70-5-2811, QXCM1000240138, Note 10662, TCPIP_BUGS Note 3362

06-Dec-2005	Alpha and IA64

	Problem:

	Users were unable to specify the gateway by name when adding a
	route.
	
	Deliverables:

	TCPIP$IPC_SHR.EXE

	Reference:

	70-5-2588, TCPIP_BUGS Note 3377

31-Jul-2006	Alpha and IA64

	Problem:

	Definitions for certain TCP socket options were missing from
	SYS$SHARE:TCPIP$INETDEF.*.  Following are the defintions added
	with this revision:
	
	#define INET$C_TCP_TSOPTENA 16  /* time stamp option             */
	#define INET$C_TCP_PAWS 32      /* PAWS option                   */
	#define INET$C_TCP_SACKENA 64   /* SACK enabled                  */
	
	Couterparts with the TCPIP$ prefix are also added.
	
	Deliverables:

	TCPIP$INETDEF.*

	Reference:

	70-5-2980

---------------------------------------------------------------------------
Corrections for HP TCP/IP Services V5.5 DNFS (NFS client) Images
---------------------------------------------------------------------------
ECO 1 updates
-------------
16-Nov-2004	Alpha and IA64

	Problem:

	TCPIP mount, dismount and show mount commands return a
	constant status %X10000000, upon either success or failure.

	Deliverables:

	TCPIP$DNFSDRIVER.EXE

	Reference:

	PTR 70-5-2519, TCPIP_BUGS Note 3236

14-Mar-2005	Alpha and IA64

	Problem:

	A $DIRECTORY of a directory on an NFS device (DNFS:) could
	report a file name twice.  One would see a.a;2, a.a;2, a.a;1
	where a.a;2 a.a;1 should have been.  This would would only occur
	when the NFS server was running on an operating system other
	than OpenVMS.

	Deliverables:

	TCPIP$DNFSDRIVER.EXE

	Reference:

	PTR 70-5-2747, TCPIP_BUGS Note 3277

---------------------------------------------------------------------------
Corrections for HP TCP/IP Services V5.5 SMTP Images
---------------------------------------------------------------------------
ECO 1 updates
-------------
25-Jan-2005	Alpha and IA64

	Problem:

	The SMTP SFF feature (TCPIP$SMTP_SFF.EXE image) loops for a mail
	message that contains a single header longer than 7192 bytes.

	If such a message is delivered to a recipient who has email
	forwarded to a PIPE% Mailshr mechanism that uses SFF (such as
	SpamAssassin), the symbiont will hang, waiting forever for the
	looping PIPE% child process.

	Deliverables:

	TCPIP$SMTP_SFF.EXE

	Reference:

	TCPIP_BUGS Note 3252

ECO 2 updates
-------------
25-Apr-2005	Alpha and IA64

	Problem:

	When a user had SYSPRV as an authorized privilege, but not an
	active one, sending mail via SMTP caused security alarms.
	
	Deliverables:

	TCPIP$SMTP_MAILSHR.EXE
	TCPIP$LIB.OLB

	Reference:

	70-5-2873, QXCM1000294118

19-Aug-2005	Alpha and IA64

	Problem:

	TCPIP SHOW MX and starting SMTP caused an ACCVIO.
	
	Deliverables:

	TCPIP$ACCESS_SHR.EXE

	Reference:

	70-5-2732, 70-5-2713, TCPIP_BUGS Note 3341

01-Dec-2005	Alpha and IA64

	Problem:

	The TCPIP SHOW MAIL /ENTRY=<entry_number> command fails on
	alternate attempts.
	
	Deliverables:

	TCPIP$UCP.EXE

	Reference:

	70-5-2801, QXCM1000237261

12-Dec-2005	Alpha and IA64

	Problem:

	SMTP could not process messages containing lines longer than 4093
	characters.
	
	Deliverables:

	TCPIP$SMTP_MAILSHR.EXE

	Reference:

	70-5-2877

11-Feb-2006	Alpha and IA64

	Problem:

	SMTP components attempting to open existing control files would in
	some cases abort upon finding the file locked by another user.
	
	The TCPIP ANALYZE MAIL /REPAIR command could mistakenly take an
	SMTP control file with no current job as an orphan when in fact
	the file was still in the process of being created and had simply
	not yet been submitted to the SMTP queue by its creator.
	
	The TCPIP ANALYZE MAIL /REPAIR command unnecessarily locked the
	mail directory during its analysis, which could lead to a delivery
	failure if new mail happened to arrive while the command executed.
	
	If the job executing in an SMTP queue was cancelled, as with
	DELETE /ENTRY, the SMTP symbiont sometimes exited, stopping the
	queue.
	
	Deliverables:

	TCPIP$SMTP_*.EXE

	Reference:

	70-5-2802, 70-5-2802, 70-5-2853, TCPIP_BUGS Note 3411

14-Feb-2006	Alpha and IA64

	Problem:

	A user without privileges sending mail caused security alarms for
	queue CONTROL and READ access.
	
	Deliverables:

	TCPIP$SMTP_MAILSHR.EXE

	Reference:

	70-5-2914, QXCM1000315372

08-Aug-2006	Alpha and IA64

	Problem:

	SMTP could not handle a message with a very large number of
	recipients.
	
	Deliverables:

	TCPIP$SMTP_MAILSHR.EXE
	TCPIP$SMTP_SYMBIONT.EXE
	TCPIP$SMTP_RECEIVER.EXE

	Reference:

	70-5-2970

ECO 3 updates
-------------
15-Feb-2007	Alpha and IA64

	Problem:

	1. VMS MAIL does not support lines longer than 255 characters.
	   Long header lines are becoming increasingly common in the
	   modern Internet.  While fetching such messages, the IMAP
	   server would return some headers in the body part of the
	   mail, causing it to appear corrupted to the client.
	
	2. IMAP had trouble fetching mails with lowercase or mixed case
	   RFC headers.

	Deliverables:

	TCPIP$SMTP_MAILSHR.EXE
	TCPIP$SMTP_SYMBIONT.EXE
	TCPIP$SMTP_RECEIVER.EXE

	Reference:

	TCPIP_BUGS Note 3540

12-Apr-2007	Alpha and IA64

	Problem:

	SMTP could not send a message when the domain name on the
	right hand side of a recipent's address included an all-numeric
	element, such as john@123.example.com.
	
	Deliverables:

	TCPIP$SMTP_MAILSHR.EXE

	Reference:

	70-5-3101

21-Sep-2007	Alpha and IA64

	Problem:

	SMTP distribution list filenames were not always formed
	properly, and it was not possible to specify a location
	other than TCPIP$SMTP_COMMON: to contain *.DIS files.
	
	Deliverables:

	TCPIP$SMTP_MAILSHR.EXE
	TCPIP$SMTP_RECEIVER.EXE
	TCPIP$SMTP_RUN_SCRIPT.EXE
	TCPIP$SMTP_SFF.EXE
	TCPIP$SMTP_SYMBIONT.EXE
	TCPIP$SMTP_UTILITIES.EXE

	Reference:

	PTR 75-118-375

---------------------------------------------------------------------------
Corrections for HP TCP/IP Services V5.5 LPD Images
---------------------------------------------------------------------------
ECO 1 updates
-------------
19-Jan-2005	Alpha and IA64

	Problem:

	Print jobs uing wildcard proxy from hosts with no
	name to address translation available should succeed but
	are rejected.	

	Deliverables:

	TCPIP$LPD_SHR.EXE

	Reference:

	TCPIP_BUGS Note 3251

07-Jun-2005	Alpha only

	Problem:

	$PRINT/PARAM=(host=x) would report an access violatation (ACCVIO).

	Deliverables:

	TCPIP$LPD_SHR.EXE

	Reference:

	PTR 30-15-41, TCPIP_BUGS Note 3251

ECO 3 updates
-------------
20-Dec-2006     Alpha and IA64

	Problem:

	LPD printing with the qualifier /PARAMETERS=MAIL included an
	incorrect job status in the resulting mail message.

	Deliverables:

	TCPIP$LPD_SHR.EXE

	Reference:

	PTR 75-109-1670

22-Jan-2007	Alpha and IA64

	Problem:

	Printing to an LPD queue with a large (over 1024 characters)
	setup module was inefficient.  Although correct output was
	printed, the logfile showed that for each job, there was a
	series of attempts to read the setup module into increasingly
	large buffers.

	Deliverables:

	TCPIP$LPD_SHR.EXE
	TCPIP$LPD_SMB.EXE

	Reference:

	PTR 70-5-3033, QXCM1000373653

	Note:

	A new configuration parameter "Setup-Buffer-Size" (in the
	TCPIP$LPD.CONF file) will allow the system manager to specify
	the initial setup module buffer size.

	The default value is 1024 bytes.

24-Sep-2007	Alpha and IA64

	Problem:

	Overly numerous "TCPIP-E-LPD_REQREJECT" messages appeared when
	attempting to deliver LPD jobs to a printer that was not in
	service.

	Deliverables:

	TCPIP$LPD_SHR.EXE
	TCPIP$LPD_RCV.EXE
	TCPIP$LPD_SMB.EXE
	TCPIP$LPD_UTILITIES.EXE

	Reference:

	QXCM1000460114

---------------------------------------------------------------------------
Corrections for HP TCP/IP Services V5.5 PWIP Images
---------------------------------------------------------------------------
ECO 1 updates
-------------
24-May-2005	Alpha and IA64

	Problem:

	The system crashed in KERNEL_GET_ADDR_INFO because the PWIP kernel
	client passed in an uninitialized socket length and GAI used it to
	write over a huge chunk of pool via MOVC3.

	Deliverables:

	TCPIP$PWIPDRIVER.EXE

	Reference:

	PTR 75-112-175, TCPIP_BUGS Note 3322

ECO 2 updates
-------------
30-Oct-2005	Alpha and IA64

	Problem:

	PWIP socket buffers were too small for the typical modern
	network environment, degrading performance in some cases.
	
	Deliverables:

	TCPIP$PWIPACP.EXE

	Reference:

	QXCM1000298713, TCPIP_BUGS Note 3360

20-Sep-2006	Alpha and IA64

	Problem:

	A crash occurred during PWIP shutdown: "DECNET, DECnet detected a
	fatal error."
	
	Deliverables:

	TCPIP$PWIPDRIVER.EXE

	Reference:

	70-5-3004, QXCM1000351730, TCPIP_BUGS Note 3501

---------------------------------------------------------------------------
Corrections for HP TCP/IP Services V5.5 IFCONFIG Images
---------------------------------------------------------------------------
ECO 1 updates
-------------
12-Apr-2005	Alpha and IA64

	Problem:

	Use of the ifconfig command "ndna" could crash the system.

	Deliverables:

	TCPIP$IFCONFIG.EXE

	Reference:

	TCPIP_BUGS Note 3289

23-Jun-2005	Alpha and IA64

	Problem:

	When the sysgen parameter LCKMGR_MODE was set to a nonzero
	value, then failSAFE would not failover or recover addresses.
	This could only be corrected by setting LCKMGR_MODE = 0 and
	restarting TCP/IP.

	Deliverables:

	TCPIP$IFCONFIG.EXE

	Reference:

	PTR 70-5-2824, TCPIP_BUGS Note 3330

ECO 3 updates
-------------
14-Jun-2007	Alpha and IA64

	Problem:

	Issuing the following command resulted in an ACCVIO due to a
	missing argument for the ip6hoplimit value:
	
		$ ifconfig we0 inet6 ip6hoplimit
	
	Deliverables:

	TCPIP$IFCONFIG.EXE

	Reference:

	75-117-29

---------------------------------------------------------------------------
Corrections for HP TCP/IP Services V5.5 NETSTAT Images
---------------------------------------------------------------------------
ECO 2 updates
-------------
3-Aug-2006	Alpha and IA64

	Problem:

	"netstat -i" was not correctly displaying network names.
	
	Deliverables:

	TCPIP$NETSTAT.EXE

	Reference:

	70-5-2981

---------------------------------------------------------------------------
Corrections for HP TCP/IP Services V5.5 DHCP Images
---------------------------------------------------------------------------
ECO 1 updates
-------------
19-Apr-2005	Alpha and IA64

	Problem:

	On OpenVMS 7.3-2 the DHCP client sometimes cannot renew the lease
	on its IP address.  This happens because the DHCP client cannot see
	unicast packets coming in from the DHCP server. The client then
	becomes hung and if it is not stopped and re-started before the
	lease expires the client host will continue to use the IP address.
	Once the IP address's lease has expired, the DHCP server may assign
	it to another client.

	Also, After renewing the lease on its IP address, the DHCP client
	stores a host name of "unknown" in the interface's DHC file.

	Deliverables:

	TCPIP$DHCP_CLIENT.EXE

	Reference:

	TCPIP_BUGS Note 3298

ECO 2 updates
-------------
21-Apr-2006	Alpha and IA64

	Problem:

	If the DHCP server were running on an interface that had an alias
	address assigned with a subnet different from its primary address,
	clients on the subnet of the primary interface address could
	experience problems contacting the server.
	
	Deliverables:

	TCPIP$DHCP_SERVER.EXE

	Reference:

	70-5-2890, TCPIP_BUGS Note 3447

15-Sep-2006	Alpha and IA64

	Problem:

	When DNS updates were enabled, the DHCP server would update the
	DNS server correctly only if the netmask for the client's network
	was 255.255.255.0.
	
	Deliverables:

	TCPIP$DHCP_SERVER.EXE

	Reference:

	70-5-2947, TCPIP_BUGS Note 3498

ECO 3 updates
-------------
24-Jan-2007	Alpha and IA64

	Problem:

	The DHCP client, when run in a cluster where the TCPIP$* data
	files were shared between cluster members, could incur RMS-E-FLK
	errors when running the TCPIP$$SETHOSTNAME.COM script's SET HOST
	and SET NOHOST commands.

	Deliverables:

	TCPIP$DHCP_CLIENT.EXE

	Reference:

	TCPIP_BUGS Note 3528

 4-Apr-2007	Alpha and IA64

	Problem:

	There was no way to disable the DHCP server on particular
	interfaces.  It always listened on all configured interfaces.
	
	Deliverables:

	TCPIP$DHCP_SERVER.EXE

	Reference:

	PTR 70-5-3005, QXCM1000365692

	Note:

	A new logical name TCPIP$DHCP_IGNOR_IFS specifies the names of
	the interfaces to be ignored.  If defined, the DHCP server will
	not listen on any ignored interfaces.

	For example:

	$ DEFINE /SYSTEM TCPIP$DHCP_IGNOR_IFS  "ie0, ie1"

10-Dec-2007	Alpha and IA64

	Problem:

	The DHCPSIGHUP command had to be issued twice in order to update
	the DHCP Debug Level.	

	Deliverables:

	TCPIP$DHCP_CLIENT.EXE
	TCPIP$DHCP_DBDUMP.EXE
	TCPIP$DHCP_SERVER.EXE
	TCPIP$DHCP_CLIENT_CONF.EXE
	TCPIP$DHCP_BPASCIITODBMOD.EXE

	Reference:

	75-117-53

---------------------------------------------------------------------------
Corrections for HP TCP/IP Services V5.5 LBROKER Images
---------------------------------------------------------------------------
ECO 1 updates
-------------
20-Dec-2004	Alpha and IA64

	Problem:

	Load Broker fails to process incoming metric data when
	under heavy load.

	Deliverables:

	TCPIP$LBROKER.EXE

	Reference:

	PTR 70-5-2685, TCPIP_BUGS Note 3243

---------------------------------------------------------------------------
Corrections for HP TCP/IP Services V5.5 POP Images
---------------------------------------------------------------------------
ECO 3 updates
-------------
19-Jun-2007	Alpha and IA64

	Problem:

	The version number returned by the POP "XTND STATS" command was
	hard-coded at build time rather than reflecting the current
	installed images.

	Deliverables:

	TCPIP$POP_SERVER.EXE

	Reference:

	75-118-363

---------------------------------------------------------------------------
Corrections for HP TCP/IP Services V5.5 IMAP Images
---------------------------------------------------------------------------
ECO 1 updates
-------------
17-Feb-2005	Alpha and IA64

	Problem:

	In a message, any line containing more than 255 characters
        (i.e. without intermediate CR/LF) got truncated to 255.  This
	was too short in many cases; the new line length limit is 2047.

	Deliverables:

	TCPIP$IMAP_SERVER.EXE

	Reference:

	PTR 70-5-2712, QXCM1000213788, TCPIP_BUGS Note 3257

ECO 2 updates
-------------
2-Mar-2006	Alpha and IA64

	Problem:

	The IMAP server intermittently exited with an ACCVIO.
	
	Deliverables:

	TCPIP$IMAP_SERVER.EXE

	Reference:

	70-5-2810, 70-5-2826, 70-5-2898

31-Mar-2006	Alpha and IA64

	Problem:

	The IMAP server intermittently exited when a user had more than
	25 empty folders.
	
	Deliverables:

	TCPIP$IMAP_SERVER.EXE

	Reference:

	70-5-2909

---------------------------------------------------------------------------
Corrections for HP TCP/IP Services V5.5 BIND9_SERVER Images
---------------------------------------------------------------------------
ECO 1 updates
-------------
13-Oct-2004	Alpha and IA64

	Problem:

	Some resolver clients do not get responses from the
	BIND server after a failover event when using the
	cluster alias.

	Deliverables:

	TCPIP$BIND_SERVER.EXE

	Reference:

	PTR 70-5-2631, TCPIP_BUGS Note 3219

ECO 2 updates
-------------
05-May-2006	Alpha and IA64

	Problem:

	The TCPIP$BIND_COMMON search list logical did not
	behave as a search list when used by the BIND server.
	
	Deliverables:

	TCPIP$BIND_SERVER.EXE
	TCPIP$BIND_CLUSTER_SETUP.COM

	Reference:

	Note 3457

13-Sep-2006	Alpha and IA64

	Problem:

	The BIND server, when multiple forwarders were available, was not
	particularly intelligent about selecting one.  It would continue
	to send queries to an unresponsive forwarder, sometimes taking so
	long that when it found a good one later in the list, the client's
	resolver had already given up.
	
	Deliverables:

	TCPIP$BIND_SERVER.EXE

	Reference:

	70-5-3003, TCPIP_BUGS Note 3497

19-Sep-2006	Alpha and IA64

	Problem:

	The TCPIP$BINDSETUP utility needed to conform to the new
	localhost database file name, LOOPBACK.DB.
	
	Deliverables:

	TCPIP$BINDSETUP.COM

	Reference:

	70-5-3006, TCPIP_BUGS Note 3500

17-Oct-2006	Alpha and IA64

	Problem:

	The ability to produce memory usage statistics for the BIND
	server was lost in V5.4 and needed to be restored.
	
	There is now a method to display the memory usage
	statistics for the BIND Server.  First, define the
	logical name:
	
	$ DEFINE /SYSTEM TCPIP$BIND_MEMSTATS 1
	
	TCPIP$BIND_MEMSTATS is an existence logical name.  The
	value does not matter, only whether it is defined.
	
	Use either the "rndc stats" command or the
	TCPIP SHOW NAME_SERVICE /STATISTICS command to send the
	memory usage statistics to the file TCPIP$BIND.STATS.
	The memstats information will complement the server
	Statistics Dump information that is normally sent to
	the file.
	
	Deliverables:

	TCPIP$BIND_SERVER.EXE

	Reference:

	70-5-3031, TCPIP_BUGS Note 3508

ECO 3 updates
-------------
 9-Aug-2007	Alpha and IA64

	Problem:

	Query ID's generated by the DNS server were vulnerable to
	cryptographic analysis.	

	Deliverables:

	TCPIP$BIND_SERVER.EXE

	Reference:

	TCPIP_BUGS Note 3608

---------------------------------------------------------------------------
Corrections for HP TCP/IP Services V5.5 NSLOOKUP Images
---------------------------------------------------------------------------
ECO 2 updates
-------------
30-Mar-2006	Alpha and IA64

	Problem:

	Using CTRL/C within the NSLOOKUP utility could trigger the
	following error message:

	fatal flex scanner internal error--end of buffer missed
	%NONAME-E-NOMSG, Message number 00000002

	Deliverables:

	TCPIP$NSLOOKUP.EXE

	Reference:

	3430, 75-109-1365

---------------------------------------------------------------------------
Corrections for HP TCP/IP Services V5.5 SSH Images
---------------------------------------------------------------------------
ECO 1 updates
-------------
 6-Jan-2005	Alpha and IA64

	Problem:

	When connected to a system running the TCP/IP Services SFTP server
	from a Linux SFTP client, an attempt to use the SFTP get command
        to copy a file from the server to the client hung if the file was
        greater than 98277 bytes in size.

	Deliverables:

	TCPIP$SSH_SFTP-SERVER2.EXE

	Reference:

	PTR 70-5-2567, TCPIP_BUGS Note 3247

13-Jan-2005	Alpha and IA64

	Problem:

	The SSH server was not deleting processes which run the
	TCPIP$SSH_SFTP-SERVER2.EXE sftp server image after
	it is finished.  With clients such as Hummingbird,
	child processes stayed around, consuming PGFLQUO,
	eventually causing quota exhaustion.

	Deliverables:

	TCPIP$SSH_SSHD2.EXE

	Reference:

	PTR 70-5-2693, TCPIP_BUGS Note 3272

 3-Mar-2005	Alpha and IA64

	Problem:

	OpenVMS SSH did not support mixed case passwords.

	Deliverables:

	TCPIP$SSH_SSHD2.EXE

	Reference:

	PTR 30-14-108, TCPIP_BUGS Note 3259

 3-Mar-2005	Alpha and IA64

	Problem:

	Flaws in the logic around calls to ssh_xfree() could result in
	errors like "Freeing block that is already freed".

	Deliverables:

	TCPIP$SSH_SSHD2.EXE

	Reference:

	PTR 30-13-380, TCPIP_BUGS Note 3262

 3-Mar-2005	Alpha and IA64

	Problem:

	<CTRL/C> was not possible during sftp2/scp filecopy.

	Deliverables:

	TCPIP$SSH_SCP2.EXE
	TCPIP$SSH_SFTP2.EXE

	Reference:

	PTR 30-14-116, TCPIP_BUGS Note 3263

 3-Mar-2005	Alpha and IA64

	Problem:

	OpenVMS SSH did not support use of CHANGEREQ message for
	password change in communication with non-VMS remote client
	or server.

	Deliverables:

	TCPIP$SSH_SSH2.EXE
	TCPIP$SSH_SSHD2.EXE

	Reference:

	PTR 30-14-170, TCPIP_BUGS Note 3265

 3-Mar-2005	Alpha and IA64

	Problem:

	Inaccurate listing for hostbased authentication in
	SSH*2_CONFIG. files.

	Deliverables:

	TCPIP$SSH_SSH2.EXE
	TCPIP$SSH_SSHD2.EXE

	Reference:

	PTR 30-14-176, TCPIP_BUGS Note 3266


 3-Mar-2005	Alpha and IA64

	Problem:

	OpenVMS SSH does not support secondary password for
	password authentication method.

	Deliverables:

	TCPIP$SSH_SSHD2.EXE

	Reference:

	PTR 70-5-2544, TCPIP_BUGS Note 3270

 3-Mar-2005	Alpha and IA64

	Problem:

	OpenVMS SSH does not support "$" character in username.

	Deliverables:

	TCPIP$SSH_SSHD2.EXE

	Reference:

	PTR 70-5-2602, TCPIP_BUGS Note 3271

 4-Mar-2005	Alpha and IA64

	Problem:

	Could not copy files larger than 4 gigabytes.
	Original problem  had been copying files larger
	than 2 gigabytes; these fixes extend copy to
	16 gigabytes (and beyond).

	Deliverables:

	TCPIP$SSH_SCP2.EXE (and friends)

	Reference:

	PTR 70-5-2477, TCPIP_BUGS Note 3269

 5-Mar-2005	Alpha and IA64

	Problem:

	Various signals received during code result in extraneous or
	cryptic signal messages.

	Deliverables:

	TCPIP$SSH_SSH2.EXE (and friends)

	Reference:

	PTR 30-13-339, TCPIP_BUGS Note 3261

 5-Mar-2005	Alpha and IA64

	Problem:

	The SSH server did not support password change requests
	for non-VMS clients when passwords were pre-expired.  This
	was a problem with captive accounts when there were no other
	secure method for changing passwords.

	Deliverables:

	TCPIP$SSH_SSHD2.EXE

	Reference:

	PTR 30-5-429, TCPIP_BUGS Note 3268

 6-Mar-2005	Alpha and IA64

	Problem:

	When crtl memory allocation routine returns null pointer,
	SSH code accvio's instead of exiting gracefully.

	Deliverables:

	TCPIP$SSH_SSHD2.EXE

	Reference:

	PTR 30-14-177, TCPIP_BUGS Note 3267

 7-Mar-2005	Alpha and IA64

	Problem:

	When an SCP client used the SSH version 1 SCP protocol to copy a
	file from the TCP/IP Services SSH server, the file was not copied
	and an error saying "protocol error: unexpected <newline>" was
	issued to the SCP client user.

	Although we do not support the SSH v1 protocol, we can return a
	more friendly error message when the operation fails.

	Deliverables:

	TCPIP$SSH_SSHD2.EXE

	Reference:

	PTR 70-5-2663, TCPIP_BUGS Note 3276

 8-Mar-2005	Alpha and IA64

	Problem:

	Auditing and other VMS-specific config options
	cannot be specified in SSH2_CONFIG. and SSHD2_CONFIG.
	Also, for auditing, the defaults do not work.

	Deliverables:

	TCPIP$SSH_SSHD2.EXE

	Reference:

	PTR 30-14-154, TCPIP_BUGS Note 3264

 8-Mar-2005	Alpha and IA64

	Problem:

	TCPIP V5.4 ECO 4 and earlier SSH client and and server do not
	properly handle the version check with OpenVMS remote at a later
	version, thus failing to recognize the server as OpenVMS.

	Deliverables:

	TCPIP$SSH_SSHD2.EXE

	Reference:

	PTR 30-14-157, TCPIP_BUGS Note 3273

14-Mar-2005	Alpha and IA64

	Problem:

	The sftp lcd and lpwd commands issue the error "PWD failed."

	Deliverables:

	TCPIP$SSH_SFTP2.EXE

	Reference:

	PTR 70-5-2652, TCPIP_BUGS Note 3278

19-Apr-2005	Alpha and IA64

	Problem:

	V5.5 / ssh 3.2.0 based code used for V5.4 ECO 4B
	did not handle password update interaction with
	peer at V5.4 ECO 4, V5.5 SSB, and some cases of
	V5.4 ECO 4B.  Note that even after the fixes
	detailed here, there are cases where a password update
	does not work, e.g., when a new server is identifying
	itself as V 3.2.0 and client is V5.4 ECO 4.

	Deliverables:

	TCPIP$SSH_SSHD2.EXE

	Reference:

	PTR 30-14-170, TCPIP_BUGS Note 3300

19-Apr-2005	Alpha and IA64

	Problem:

	An error in TCPIP$SSH_RUN.LOG indicated a timeout while locking
	the authority file, followed by a failure to run the desired
	X application in the newly-created SSH session.

	Deliverables:

	TCPIP$SSH_SSHD2.EXE

	Reference:

	PTR 70-5-2743, TCPIP_BUGS Note 3301

19-Apr-2005	Alpha and IA64

	Problem:

	It was not possible to cascade $ CREATE TERMINAL /DETACH
	commands from an SSH session (using x11 port forwarding).  That
	is, in a window created from the original session window, an
	attempt to create another detached terminal window would fail.

	Deliverables:

	TCPIP$SSH_SSHD2.EXE

	Reference:

	PTR 70-5-2690, TCPIP_BUGS Note 3302

21-Apr-2005	Alpha and IA64

	Problem:

	The intrusion records created when the intruder comes from a
	client other than the TCP/IP Services client are not sufficiently
	unique for some environments.  This means that one intruder on a
	remote host locks out all users from that host -- especially
	onerous in environments where multiple client hosts appear to be
	from the same remote IP address.

	Deliverables:

	TCPIP$SSH_SSHD2.EXE

	Reference:

	PTR 70-5-2737, TCPIP_BUGS Note 3304

22-Apr-2005	Alpha and IA64

	Problem:

	The TCP/IP Services SFTP server would only allow a remote client
	to "get" a file that has a record format of stream LF, fixed
	length or undefined.  Many OpenVMS applications produce files
	with variable length or VFC record formats, making it impossible
	to fetch such files using the TCP/IP Services SFTP server.

	Deliverables:

	TCPIP$SSH_SFTP-SERVER2.EXE

	Reference:

	PTR 70-5-2721, TCPIP_BUGS Note 3305

 7-May-2005	Alpha and IA64

	Problem:

	The TCP/IP Services for OpenVMS SFTP server did not honor the
	"-l", or "long format" option, when entered by the SFTP client.
	This problem occurred regardless of which SFTP client was used.

	Deliverables:

	TCPIP$SSH_SFTP-SERVER2.EXE

	Reference:

	PTR 70-5-2758, TCPIP_BUGS Note 3312

 9-May-2005	Alpha and IA64

	Problem:

	The SFTP client did not sense the terminal page size
	properly.  The screen output was forced to the default
	setting of 24 lines per page.

	Deliverables:

	TCPIP$SSH_SFTP2.EXE

	Reference:

	TCPIP_BUGS Note 3314

23-May-2005	Alpha and IA64

	Problem:

	Users of SCP and SFTP could not make use of group logical names
	on the SFTP server.  This problem occurred because the group
	logical name table in the SFTP server process points to the
	TCPIP$SSH account's group logical name table of the instead of
	the table of the account being used for the file transfer.

	Deliverables:

	TCPIP$SSH_SFTP-SERVER2.EXE

	Reference:

	PTR 70-5-2750, TCPIP_BUGS Note 3321

21-Jun-2005	Alpha and IA64

	Problem:

	If a host does not have file SYS$SHARE:DECW$SETSHODISSHR.EXE
	installed, client and server startup fail.  The situation
	among support/customers was: DECwindows Motif V1.3 installed,
	but not started.  A related problem can occur if pre-V1.3 is
	installed; those versions do not deliver that shareable image.

	Deliverables:

	TCPIP$SSH_SSHD2.EXE

	Reference:

	TCPIP_BUGS Note 3332

11-Aug-2005     Alpha and IA64

        Problem:

        VMS text editor and the DCL SEARCH command see SSH server
        log file messages like WARNING: Starting image in auxiliary
        server mode as two separate lines with the text of message
        on a different line from the "WARNING:" prefix.

        The DCL TYPE command functions properly by displaying one
        line.

        This behavior may cause some customer auditing procedures
        to fail.

        Solution:

        Write the warning message as a single line.

        Deliverables:

        All SSH images

        Reference:

        PTR 70-5-2844 / QXCM1000279748
        TCPIP_BUGS Note 3340

30-Aug-2005     Alpha and IA64

        Problem:

        The SSH client ignores any DNS AAAA records belonging to the remote
        host thus effectively disabling connecting via IPv6.

        Solution:

        Recognize DNS AAAA records.

        Deliverables:

        All SSH images

        Reference:

        TCPIP_BUGS Note 3342

15-Sep-2005     Alpha and IA64

        Problem:

        From some clients, such as the PuTTY client, when the
        username entered is other than all lowercase, publickey
        authentication fails.

        Solution:

        The SSH server now captures the original filename as sent
        from the client and uses it in authentication procedure.

        Deliverables:

        All SSH images 

        Reference: 

        PTR 70-5-2831 / QXCM1000245554
        TCPIP_BUGS Note 3349
        
14-Oct-2005     Alpha and IA64

        Problem:

        Regular expression syntax parsing not being done on
        for AllowHosts in sshd2_config.

        Solution:

        Regular expressions are now parsed using the "egrep"
        syntax. Variables to which this appies include AllowHost,
        DenyHosts, AllowUsers, and DenyUsers. (See examples in
        sshd2_config.) One OpenVMS extension was retained from
        previous versions: To specify allow all hosts, both of
        the following work:

        Standard regular expression egrep syntax:
               AllowHosts  .*

        OpenVMS extension:
               AllowHosts  *

        Note that this format is the only case in which the "*" is
        accepted in addition to the ".*". In longer expressions,
        both characters ".*" are still required.

        Deliverables:

        All SSH images

        Reference:

        PTR 70-5-2789 / QXCM1000232289
        TCPIP_BUGS Note 3357

16-Oct-2005     Alpha and IA64

        Problem:

        Manipulation of interactive and noninteractive login
        dates for SSH session sets off audit alarms.

        Solution:

        The audit alarms are now suppressed for date manipulation.

        Deliverables:

        All SSH images

        Reference:

        PTR 30-13-379
        TCPIP_BUGS Note 3358

2-Dec-2005      Alpha and IA64

        Problem:

        Fixed 512 record format files copied with scp and sftp
        VMS-to-VMS end up with stream_lf record format.

        Deliverables:

        All SSH images

        Reference:

        PTR 70-5-2833 / QXCM1000245977
        TCPIP_BUGS Note 3376

5-Nov-2005      Alpha and IA64

        Problem:

        The SFTP server causes auditing alarms in the operator's log.

        Solution:

        Condition causing the alarms corrected.

        Deliverables:

        All SSH images

        Reference:

        PTR 70-5-2866 / QXCM1000293876
        TCPIP_BUGS Note 3379

14-Mar-2006     Alpha and IA64

        Problem:

        SFTP file transfers do not preserve OpenVMS file attributes even
        when the SFTP client and server are both running the TCP/IP
        Services implementation of SFTP. Such file transfers should
        preserve a file's record format and file attributes and, where
        applicable the RMS MRS and LRL fields.

        Solution:

        When both the SFTP client and server are running the TCP/IP
        Services implementation of SFTP, file transfers preserve the
        following OpenVMS file attributes:

        o  Record format

        o  File attributes

        o  mrs and/or lrl (where applicable)

        The attributes are preserved regardless of the direction of the
        file's transfer: to client or to server.

        The preservation of these attributes supports seamless transfer of
        the following types of files:

          Variable length
          VFC
          Fixed length (e.g., images and backup savesets)
          Fortran CC
          Stream_LF

        Note: This functionality works for sequential files only. SFTP does
        not support direct transfer of OpenVMS indexed or relative files.
        To transfer a file with indexed or sequential organization perform
        the following steps:

          1) Create an encoded copy of the file with sequential
          organization with any one of the following options:
              A) Backup saveset
              B) Self-extracting image (such as from SPOOL COMPRESS
                /METHOD=DCX_AXPEXE)
              C) Zip archive
          2) Transfer the converted file.
          3) Convert back on the receiving end.

        Deliverables:

        All SSH images

        Reference:

        PTR 70-5-2904 / QXCM1000345070
        TCPIP_BUGS Note 3420

15-Apr-2006     Alpha and IA64

        Problem:

        SSH password change sequence did not check for password
        in history file, or for using same new password as old one.

        Solution:

        Password history is now checked, unless the username has
        the DISPWDHIS flag set.

        Deliverables:

        All SSH images

        Reference:

        PTR 70-5-2915
        TCPIP_BUGS Note 3440

11-Apr-2006     Alpha and IA64

        Problem:

        Under certain conditions clients on other operating systems
        would cause an existing file on the OpenVMS server to be
        overwritten on filecopy (instead of creating new version).

        Solution:

        A new version is created; for scp only the -k option is
        available to force an overwrite.

        Deliverables:

        All SSH images

        Reference:

        PTR 70-5-2896 / QXCM1000309789
        TCPIP_BUGS Note 3443

24-Apr-2006     Alpha and IA64

        Problem:

        Entries made in the TCPIP$ETC:IPNODES.DAT file are not seen by the
        SSH client.

        Solution:

        Condition interfering with reading of the IPNODES.DAT file
        has been corrected.

        Deliverables:

        All SSH images

        Reference:

        PTR 30-15-89
        TCPIP_BUGS Note 3449

25-Apr-2006     Alpha and IA64

        Problem:
              
        SSH file copy clients and servers have limited support for
        the ODS-5 file format.

        Solution:

        This problem has been corrected. Note that the following
        limitations apply to this fix:

        o  It addresses only problems with sftp ls/get/put and scp
           copy of files with extended filenames. ODS-5 syntax
           may work in other situations, but they are neither
           guaranteed nor supported.

        o  It is not intended to handle copying of files with
           extended file names to target directories on ODS-2
           volumes. In that case an error of the following type
           results:

           tcpip$ssh_scp2.exe: warning: open: ./afile,name.txt (dst):
           unspecified failure (server msg: 'syserr: bad file number,
           file: ./afile,name.txt')

           %TCPIP-E-SSH_FC_ERR_FAIL, undetermined error from sshfilexfer

        o  When wildcards are used in file specification not all
           files with ODS-5 extended file name may be retrieved.
           For example: sftp>get *.*;* retrieves all files,
           while sftp get afil*.txt does not get files with ODS-5
           characters:

           sftp> get *.*;*
           afile2.txt;1        |    8B | 0.0 kB/s | TOC: 00:00:01 | 100%
           afile^%name.txt;2   | 1008B | 1.0 kB/s | TOC: 00:00:01 | 100%
           afile^,name.txt;1   |    6B | 0.0 kB/s | TOC: 00:00:01 | 100%
           afile^^^%name.txt;1 |   12B | 0.0 kB/s | TOC: 00:00:01 | 100%
           AFILE__NAME.TXT;1   |   20B | 0.0 kB/s | TOC: 00:00:01 | 100%

           sftp> get afil*.txt
           afile2.txt          |    8B | 0.0 kB/s | TOC: 00:00:01 | 100%
           afile__name.txt     |   20B | 0.0 kB/s | TOC: 00:00:01 | 100%

        Deliverables:

        All SSH images

        Reference:

        PTR 30-15-68
        TCPIP_BUGS Note 3450

26-Apr-2006     Alpha and IA64

        Problem:

        SFTP2 image exits with status "normal" even after errors
        are encountered.

        Solution:
        The following DCL exit codes are now supported for batch
        procedure exit. Of these, only TCPIP$_SSH_FC_ERR_TGT_EXISTS
        is a new code:

        TCPIP$_SSH_FATAL "non-specific fatal error condition"
        TCPIP$_SSH_FC_OK "operation was successful"
        TCPIP$_SSH_FX_OK "the operation completed successfully"
        TCPIP$_SSH_INFORMATIONAL "ssh informational"
        TCPIP$_SSH_ERROR "non-specific error condition"
        TCPIP$_SSH_FX_EOF "the operation failed because of trying to read 
                at end of file"
        TCPIP$_SSH_FX_NO_SUCH_FILE "the requested file does not exist"
        TCPIP$_SSH_FX_PERM_DENIED "insufficient privileges to perform 
                the operation"
        TCPIP$_SSH_FX_FAILURE "the requested operation failed"
        TCPIP$_SSH_FX_BAD_MESSAGE "a badly formatted message was received; 
                error or incompatibility in the protocol implementation"
        TCPIP$_SSH_FX_NO_CONNECTION "connection has not been established 
                (yet)"
        TCPIP$_SSH_FX_CONNECTION_LOST "connection to the server was lost, 
                and the operation could not be performed"
        TCPIP$_SSH_FX_OP_UNSUPPORTED "operation is unsupported by the 
                fileserver"
        TCPIP$_SSH_FX_INVAL_RFMT "record format not supported"
        TCPIP$_SSH_FX_OUT_OF_MEMORY "out of dynamic memory"
        TCPIP$_SSH_FC_ERROR "error in ssh file transfer operation"
        TCPIP$_SSH_FC_ERR_DEST_NOT_DIR "destination is not directory or 
                does not exist"
        TCPIP$_SSH_FC_ERR_ELOOP "maximum symlink level exceeded"
        TCPIP$_SSH_FC_ERR_CONN_FAILED "connecting to host failed"
        TCPIP$_SSH_FC_ERR_CONN_LOST "connection broke for some reason"
        TCPIP$_SSH_FC_ERR_NO_SUCH_FILE "file doesn't exist"
        TCPIP$_SSH_FC_ERR_PERM_DENIED "no permission to access file"
        TCPIP$_SSH_FC_ERR_FAILURE "error in ssh file transfer operation"
        TCPIP$_SSH_FC_ERR_PROTO_MSMTCH "file transfer protocol mismatch"
        TCPIP$_SSH_FC_ERR_INVAL_RFMT "file record format invalid for copy"
        TCPIP$_SSH_FC_ERR_TGT_EXISTS "target file already exists"

        If multiple errors are encountered, exit status reflects
        the last error. The following logical names are available
        to control behavior for the new functionality. To use these
        names define them to have a value "TRUE" (case insensitive)
        or any nonzero numeric value.

        o  TCPIP$SFTP_ALWAYS_EXIT_NORMAL: preserves old behavior of
           sftp exiting with status $STATUS "%X00000001" (normal),
           no matter what errors occurred during a session.

        o  TCPIP$SSH_SFTP_BATCH_ABORT_ON_ERROR: by default an
           sftp batch procedure continues after any errors except
           for failure of a cd (change directory) command. This
           behavior is the same as that for the base UNIX code.
           Setting this logical enables the OpenVMS-specific
           behavior of the procedure exiting after the first error
           is encountered.
        
        Deliverables:

        All SSH images

        Reference:

        PTR 70-5-2922 / QXCM1000319249
        TCPIP_BUGS Note 3451

26-Apr-2006     Alpha and IA64

        Problem:

        SSH file transfer clients and server do not handle
        VMS-style wildcards.

        Solution:

        Many usages for VMS-style wildcards are now supported. The
        behavior, where possible, matches that for DCL commands
        such as $ COPY and $ DIRECTORY. For example, ls afile.*
        retrieves all versions of a file, through get afile.*
        retrieves only the highest version number. One extension
        to the standard VMS set is recognition of the ? in addition
        to the % to match a single character.

        Deliverables:

        All SSH images

        Reference:

        PTR 70-5-2794 / QXCM1000233861, 70-5-2848 / QXCM1000283230, 
            30-15-68 
        TCPIP_BUGS Note 3452

27-Apr-2006     Alpha and IA64

        Problem:

        Text display for Usage: does not match documentation
        or what is supported or tested.

        Solution:

        "Usage" text reflects what is implemented, and also matches
        information in any DCL help files.

        Deliverables:

        All SSH images

        Reference:

        PTR 30-15-2
        TCPIP_BUGS Note 3453

8-May-2006      Alpha and IA64

        Problem:

        Allow restrictions on access to SSH filecopy.

        Solution:

        The following methods are available to restrict users
        who have ssh access to a server from using scp or sftp
        for filecopy:

        1. Use one of the following options in the SSHD2_CONFIG. file:
           DisallowSftpServer
           Default: "no"
           "yes" disables sftp-server2 for all users

           SftpDenyUsers
           Default: empty string
           Interprets regular expressions in the same way that
           DenyUsers does.

           Note that SftpDenyUsers is used only if DisallowSftpServer
           is "no".

        2. If neither configuration restriction is used, the server 
           checks for the identifier TCPIP$SSH_FILECOPY_DISALLOWED 
           granted to the current user, in which case access to 
           sftp-server2 is denied.

           To create and grant this identifier, do the following
           from privileged account:

           $ MCR AUTHORIZE
           UAF> ADD /IDENTIFIER TCPIP$SSH_FILECOPY_DISALLOWED
           %UAF-I-RDBADDMSG, identifier TCPIP$SSH_FILECOPY_DISALLOWED 
           value %X8001009F added to rights database
           UAF> SHOW /IDENTIFIER TCPIP$SSH_FILECOPY_DISALLOWED
           Name                             Value           Attributes
           TCPIP$SSH_FILECOPY_DISALLOWED    %X8001009F
           UAF> GRANT TCPIP$SSH_FILECOPY_DISALLOWED USER1
           %UAF-I-GRANTMSG, identifier TCPIP$SSH_FILECOPY_DISALLOWED
           granted to USER1
           UAF> SHOW USER1

           Username: USER1                            Owner:  Default
           ...
           Identifier                         Value           Attributes
           TCPIP$SSH_FILECOPY_DISALLOWED    %X8001009F

        Deliverables:

        All SSH images
        TCPIP$MSG.EXE
        
        Reference:

        PTR 70-5-2911 / QXCM1000315205
        TCPIP_BUGS Note 3458

9-Jun-2006      Alpha and IA64

        Problem:

        ls for directory path where component other than file
        has ods-5 character does not find file.

        Not all combinations of wildcard use and ODS-5 work;
        e.g., after a cd to a subdirectory with ODS-5 characters,
        ls *.* and ls *.*;* may show no files.  Also, ls *.*;
        may not list the files with ODS-5 names.

        Also, ls and related comands may not work after a cd, even
        back to login directory.  This defect is also present in
        earlier versions; it was not fixed for this version.
        Example:

        sftp> cd COE_EFS1$:[JONES]
        COE_EFS1$:[JONES]
        sftp> ls moxie^\
        moxie^\
        fcr_opendir: /COE_EFS1$/JONES/moxie^\ (src): no such file
           (server msg: 'syserr: file specification syntax error, file:
           /COE_EFS1$/JONES/moxie^\')

        Deliverables:

        All SSH images

        Reference:

        PTR 30-15-68-2
        TCPIP_BUGS Note 3465

12-Jun-2006     Alpha and IA64

        Problem:

        Using SFTP to pull fixed length files with an odd-numbered record
        length, e.g., 773 bytes, from an OpenVMS system to a system running
        an operating system other than OpenVMS results in a corrupted file.

        Solution:

        This problem has been corrected.        

        Deliverables:

        All SSH images

        Reference:

        PTR 70-5-2904 / QXCM1000345070
        TCPIP_BUGS Note 3466

12-Jun-2006     Alpha and IA64

        Problem:

        When a user logs in with SSH and pastes from the paste buffer,
        characters can be lost.  If the user is running a text editor,
        the user receives a "data overrun" error.

        Solution:

        This problem has been corrected.

        Deliverables:

        All SSH images

        Reference:

        PTR 70-5-2675 / QXCM1000204672
        TCPIP_BUGS Note 3467

19-Jun-2006     Alpha and IA64

        Problem:

        "cd" to a logical name when coming from another operating system 
        stopped working.

        Deliverables:

        All SSH images

        Reference:

        PTR 75-109-1636
        TCPIP_BUGS Note 3470

20-Jun-2006     Alpha and IA64

        Problem:

        When doing an ls for a directory or search list with a
        large number of files, entering q at the prompt "<Press any
        key for more or q to quit>" results in apparent hang that
        cannot be interrupted with pressing CTRL/C.

        Solution:

        Pressing q now returns immediately to the sftp> prompt.
        Additional improvements for ls displays include the
        following:

        1. The display has no blank lines, but does include the q
           (or other character) entered after the prompt.

        2. To start an SFTP session with continuous display use the
           "-C" (Continuous display) option, e.g.:

           $ sftp "-C" yourremote

           Note that the double quotes are required. Within an SFTP
           session, use the td (toggle display) command to switch
           between prompted and continuous display.

        3. Long directory listings do not cause the %TCPIP-F-SSH_
           ALLOC_ERROR error.

        4. Pressing CTRL/C on continuous listings causes return to 
           the sftp> prompt.

          ________________________ Note ________________________

          In batch mode the default remains to suppress display
          of the prompt. You cannot force the display of the
          prompt in batch mode.

          If CTRL/C is entered at the "<Press any key...>"
          prompt, you may need to enter a "q" or a carriage
          return to return to the sftp> prompt. Note that
          entering CTRL/C at the sftp> prompt (followed by a
          carriage return) causes an exit to the DCL level.

        Deliverables:

        All SSH images

        Reference:

        PTR 70-5-2954 / QXCM1000338018
        TCPIP_BUGS Note 3472

18-Jul-2006     Alpha and IA64

        Problem:

        Wildcard * does not work if file already exists.

        Deliverables:

        All SSH images

        PTR 75-109-1799
        TCPIP_BUGS Note 3478

25-Jul-2006     Alpha and IA64

        Problem:

        Need extra <CR> after pressing <CTRL/Z>, also display
        of message "** Interrupt **" not consistent with other
        TCPIP components and VMS usage.

        The logical name TCPIP$SSH_SFTP_SUPPRESS_EXIT_MESSAGES
        is available to suppress the display of the following
        messages:
            - CTRL/Z -> ** Exit **
            - CTRL/Y -> ** Interrupt **
            - CTRL/C -> ** Cancel **

        Deliverables:

        All SSH images

        PTR 70-5-2976 / QXCM1000351504
        TCPIP_BUGS Note 3482
        
31-Aug-2006     Alpha and IA64

        Problem:

        Using SCP or SFTP to transfer a file larger than 2 gigabytes
        results in a corrupt file.

        Deliverables:

        All SSH images

        PTR 75-109-1623
        TCPIP_BUGS Note 3493

22-Aug-2006     Alpha and IA64

        Problem:

        sftp "put *.*;*" accvio's

        Deliverables:

        All SSH images

        PTR 75-117-3
        TCPIP_BUGS Note 3489

22-Aug-2006     Alpha and IA64

        Problem:

        ssh to account with expired password and pwdlifetime = 0
        still requires change in password, unlike telnet or set host.

        Deliverables:

        All SSH images

        PTR 70-5-2993
        TCPIP_BUGS Note 3488

28-Aug-2006     Alpha and IA64

        Problem:

        From PC client, specifically SSH, Inc., ability to
        navigate to subdirectories had regressed from a
        fix for PTR 70-5-2880.

        Deliverables:

        All SSH images

        PTR 70-5-2985
        TCPIP_BUGS Note 3490

28-Aug-2006     Alpha and IA64

        Problem:

        "ls -R" results in an error and no display of anything in
        subdirectories.

        Deliverables:

        All SSH images

        PTR 70-5-2995
        TCPIP_BUGS Note 3491

13-Sep-2006     Alpha and IA64

        Problem:

        "ls" of directory with ODS-5 extended filename
        fails to list ODS-5 extended files.

        Deliverables:

        All SSH images

        PTR 75-117-5
        TCPIP_BUGS Note 3495

25-Sep-2006     Alpha and IA64

        Problem:

        1. Actual idle timeout ~10% greater than configured IdleTimeOut.
        2. Activity at client after ~90% of IdleTimeOut does not reset
           timeout counter.

        Deliverables:

        All SSH images

        PTR 70-5-3016
        TCPIP_BUGS Note 3504

11-Oct-2006     Alpha and IA64

        Problem:

        SSH ACCVIO during validation of new password

        Deliverables:

        All SSH images

        PTR 70-5-3023
        TCPIP_BUGS Note 3506

11-Oct-2006     Alpha and IA64

        Problem:

        1. Old password ignored when sent by client.
        2. Not primary in case, but VMS client does not check
           for old password during password update prompting.

        Deliverables:

        All SSH images

        PTR 70-5-3024
        TCPIP_BUGS Note 3507

31-Oct-2006	Alpha and IA64

	Problem:

	1. Within SFTP, the "cd .." command did not work, and "ls *.*;"
	   did not work for directories.
	2. SFTP behavior was inconsistent for "cd" and "ls" when the
	   target directory did not allow full user access.
	3. For directories allowing READ+EXECUTE access, the "ls"
	   command sometimes resulted in an error message along with
	   a display of the appropriate filenames.
	4. For directories allowing EXECUTE access only, "ls" should
	   not list files, but it did list them (along with an error
	   message).  It should list a file only if that specific name
	   is specified by the user.

	Deliverables:

	All SSH images

	Reference:

	PTR 70-5-2965

	Note:

	The following are some differences from DCL or FTP behavior and
        messages:

	When an "ls" encounters a file for which attributes are
	not accessible to the user on the SFTP server, the
	following text is included in any message displayed:
	"no privilege for attempted operation".  For example:

		fcr_readdir_lstat: G-R.TXT;1 (src): no such file
		(server msg: 'platform cannot stat() filename: file
		does not exist or no privilege for attempted
		operation.')

	Like FTP and DCL, SFTP does not allow a general "ls"
	(with no filename specified) for a directory on the
	server to which the user has E(xecute) access only.
	However, unlike FTP or DCL, SFTP does not work for an "ls"
	followed by a specific filename in an E access directory.

	For certain files, mainly those that do not exist on the
	server, the following new client-based message is displayed
	instead of the standard message sent by the server:

		no such file (client msg: no such file or directory,
		or no privilege for attempted operation)

27-Nov-2006     Alpha and IA64

        Problem:

        SCP copy reports error "got EOF reading file" after otherwise
        successful copy to non-OpenVMS server system (reported in
        OpenSSH on Sun, seen also for Tru64, OpenSSH on linux).
        Not seen on VMS-to-VMS or with non-streamlf, non-fixed record
        format files. Problem with "put" equivalent only (no explicit
        "put" or "get" with scp).

        Deliverables:

        All SSH images

        PTR 70-5-3051
        TCPIP_BUGS Note 3516

ECO 3 updates
-------------
 5-Jan-2007	Alpha and IA64

	Problem:

	In SFTP and SCP, directory logical names were getting
	translated on the client system instead of being passed to
	the server.

	Deliverables:

	All SSH images

	Reference:

	PTR 30-15-136

	Note:

	Logical names entered through the SCP and SFTP clients should
	be translated on the server system.  For example, if the client
	and server systems have a different translation for the same
	system-wide logical name, the one on the server should be used.
	Note that because the SFTP server does not execute the
	SYS$SYLOGIN command procedure, some logical names available in
	interactive sessions are not available, e.g., SYS$LOGIN.

	If a user does not have access to the directory referenced by a
	logical name (e.g., TCPIP$SSH_HOME for a non-privileged account),
	a "cd" in SFTP will fail, as expected.

	Also note that from a non-OpenVMS client, no attempt is made
	to translate a string as a logical name; behavior depends on the
	client.  For example, from a Red Hat Linux system:

	sftp> cd name
	(no leading slash before "name") results in an attempt to move
	to the [.name] subdirectory of the current default location.
	sftp> cd /name
	results in an attempt to go to a device "name", with no
	directory specified, which fails.

	Current default: dev1:[user1]; dev1:[user2] does not exist:

	sftp> cd dirname
	sftp> pwd
	Remote working directory: /DEV1/user1/dirname

	sftp> cd /dev1
	Couldn't canonicalise: No such file or directory

	sftp> cd /dev1/user1
	sftp> pwd
	Remote working directory: /dev1/000000/user1

	sftp> cd /dev1/user2
	Couldn't stat remote file: No such file or directory

13-Feb-2007	Alpha and IA64

	Problem:

	If the TCPIP$SOCKET_TRACE logical name was defined, the SSH
	server could not complete authentication and all logins failed.

	Deliverables:

	All SSH images

	Reference:

	TCPIP_BUGS Note 3538

13-Feb-2007	Alpha and IA64

	Problem:

	The SSH server could generate an ACCVIO error when the SSH
	client used an existing SSH connection for a new SFTP session.

	Deliverables:

	All SSH images

	Reference:

	TCPIP_BUGS Note 3539

21-Feb-2007	Alpha and IA64

	Problem:

	When logging into OpenVMS with SSH, messages displaying the last
	interactive and last non-interactive login times were not
	displayed.  Neither was a message flagging the number of login
	failures since the last successful login.

	Deliverables:

	All SSH images

	Reference:

	TCPIP_BUGS Note 3541

 2-Mar-2007	Alpha and IA64

	Problem:

	X11 chaining with a TCP/IP Services host in the middle of the
	chain caused the X application to fail authentication.  For
	example, if host1 through host3 were OpenVMS systems:

	host1> SSH "+X" host2
	...snip...
	host2> SSH "+X" host3
	...snip...
	host3> RUN SYS$SYSTEM:DECW$CLOCK
	warning: X11 auth data does not match fake data.
	XIO: fatal IO error 65535 (network partner disconnected
	logical link) on X server "_WSA12:"

	Deliverables:

	All SSH images

	Reference:

	PTR 70-5-3083, TCPIP_BUGS Note 3544

18-Mar-2007	Alpha and IA64

	Problem:

	Public key authentication caused an ACCVIO error within the
	OpenVMS SSH server when attempted by a specific non-OpenVMS
	client.

	Deliverables:

	All SSH images

	Reference:

	PTR 70-5-3047

	Note:

	Some clients may attempt keyboard interactive client
	authentication, which may send a null username string.
	The new code should handle this situation; in case of
	errors, the workaround is to change or add the following
	line in the TCPIP$SSH_DEVICE:[TCPIP$SSH.SSH2]SSHD2_CONFIG.
	file:

	PreserveUserKeyCase no

14-Mar-2007	Alpha and IA64

	Problem:

	SFTP "put" to servers running Sterling or Tumbleweed software
	failed with errors such as "Operation unsupported" or "The
	requested operation cannot be performed because there
	is a file transfer in progress".

	Deliverables:

	All SSH images

	Reference:

	PTR 70-5-3040, 70-5-3049

 8-Mar-2007	Alpha and IA64

	Problem:

	SFTP sessions did not set the last non-interactive login time
	in the user's UAF record, which was inconsistent with FTP.
	
	Neither SFTP sessions nor single command mode SSH logins got
	an SSH-generated USER type accounting record, as do other
	interactive terminal logins.

	Deliverables:

	All SSH images

	Reference:

	TCPIP_BUGS Note 3552

 8-Mar-2007	Alpha and IA64

	Problem:

	When the Tectia SSH client was used and multiple file transfer
	windows were open, the SSH server could be sent into a tight
	loop.
	
	When using a client that multiplexed SFTP sessions over
	existing SSH connections, each time an SFTP session ended,
	the SSH server parent process (the process running
	TCPIP$SSH_SSHD2.EXE) was left with a link to a BG device that
	no longer existed, a waste of resources for the server process.

	Deliverables:

	All SSH images

	References:

	PTR 70-5-2972, TCPIP_BUGS Note 3557

28-Mar-2007	Alpha and IA64

	Problem:

	The ListenAddress SSH server configuration field is not
	supported on TCP/IP Services for OpenVMS.  Instead, the same
	effect can be achieved by using the command TCPIP SET
	SERVICE /ADDRESS.  However, this difference was not obvious
	to users.  A warning message, generated by the SSH server,
	was added to point the user to that command.

	Deliverables:

	All SSH images

	Reference:

	TCPIP_BUGS Note 3558

23-Mar-2007	Alpha and IA64

	Problem:

	The "-e" switch on the SSH_KEYGEN utility did not work.

	Deliverables:

	All SSH images

	Reference:

	TCPIP_BUGS Note 3560

 6-Apr-2007	Alpha and IA64

	Problem:

	When a password was expired and the UAF DisForce_Pwd_Change
	flag was set, the SSH server did not set the PWD_EXPIRED or
	PWD2_EXPIRED UAF flag to prevent subsequent logins should the
	user not change their password with SET PASSWORD.  This
	allowed circumvention of password expiration as users with
	expired passwords could continue to log in.
	
	When logging in with the PWD_EXPIRED or PWD2_EXPIRED UAF flag
	set, the SSH server did not issue a text warning to the client
	as they expected from using TELNET and other login methods:
	
	    Your password has expired; contact your system manager
	
	Instead, the SSH server cued three times for password, even if
	the password was entered correctly, and then disconnected.
	
	Note:
	
	If a user's account has the DisForce_Pwd_Change UAF flag set,
	and the user does not change their expired password during
	password-based login, any subsequent login (including SSH
	public key) will be rejected until the user's PWD_EXPIRED (or
	PWD2_EXPIRED) flag is reset by the system administrator.
	
	When logging in with the PWD_EXPIRED or PWD2_EXPIRED UAF flag
	set, the SSH server now correctly returns the text:
	
	    Your password has expired; contact your system manager
	
	However, some clients do not display the message.

	Deliverables:

	All SSH images

	Reference:

	TCPIP_BUGS Note 3569

25-Apr-2007	Alpha and IA64

	Problem:

	The SSH server faild to send an explanatory message back to the
	client during an attempted password change if the chosen
	password was too short.

	Deliverables:

	All SSH images

	Reference:

	PTR 70-5-3108

	Note:

	Once a password is entered, a message about the password being
	too short or in the history list is returned, or if the new
	password is good, the user is logged in.  The value of
	PasswordGuesses in sshd2_config is not checked for new password
	entry guesses.

18-Apr-2007	Alpha and IA64

	Problem:

	SSH access to Integrity ILO console resulted in the error:

	    warning: Authentication failed.
	    Disconnected; key exchange or algorithm negotiation
	    failed (Key exchange failed.)

	Deliverables:

	All SSH images

	Reference:

	PTR 70-5-3102

30-Apr-2007	Alpha and IA64

	Problem:

	Connecting from an OpenVMS SSH client to AIX OpenSSH server
	resulted in the following error message:

	   "Did not receive identification string from n.n.n.n"

	Deliverables:

	All SSH images

	Reference:

	TCPIP_BUGS Note 3576

	Note:

	The SSH client's modified behavior (sending an SSH protocol
	version string of "SSH-2.0" rather than "SSH-1.99") applies
	only when the new TCPIP$SSH_AIX_PATCH logical is defined in
	the SYSTEM table with a non-zero value.

11-Jun-2007	Alpha and IA64

	Problem:

	Attempts to log into a non-existent account via SSH with password
	authentication would cause an SSH server ACCVIO.
	
	Deliverables:

	All SSH images

	Reference:

	PTR 75-118-447, TCPIP_BUGS Note 3590

13-Jun-2007	Alpha and IA64

	Problem:
	
	The SSH server configuration parameter UserLoginLimit was ignored.
	
	Deliverables:

	All SSH images

	Reference:

	TCPIP_BUGS Note 3591

 5-Jul-2007	Alpha and IA64

	Problem:

	When using SSH in single command mode with the TCP/IP Services
	for OpenVMS SSH server, where the command being issued used X11
	forwarding (such as CREATE/TERMINAL/DETACH), the command would
	frequently fail with an error such as "X Toolkit Error: Can't
	Open display".
	
	When interactively logging into the TCP/IP Services for OpenVMS
	SSH server, every login incurred an unnecessary one second delay.
	
	Deliverables:

	All SSH images
	TCPIP$SSH_RCMD.COM

	Reference:

	QXCM1000437086, TCPIP_BUGS Note 3597

 3-Aug-2007	Alpha and IA64

	Problem:

	A potential security flaw affected password authentication
	within the SSH server, resulting in possible unauthorized
	access.
	
	Deliverables:

	All SSH images

	Reference:

	QXCM1000449074, TCPIP_BUGS Note 3605

 6-Aug-2007	Alpha and IA64

	Problem:

	SSH client diagnostic messages printed with the -d qualifier
	were not timestamped, making diagnosis of certain problems more
	difficult.
	
	Deliverables:

	TCPIP$SSH_SSH2.EXE

	Reference:

	TCPIP_BUGS Note 3606

13-Sep-2007	Alpha and IA64

	Problem:

	If SSH_KEYGEN was used from an account whose RIGHTSLIST
	identifier was missing, an ACCVIO occurred rather than
	a more graceful error message.
	
	Deliverables:

	All SSH images

	Reference:

	QXCM1000441218, TCPIP_BUGS Note 3613

14-Sep-2007	Alpha and IA64

	Problem:

	When an SSH client tried to open multiple interactive login
	sessions over one SSH TCP connection, the TCP/IP Services
	for OpenVMS SSH server looped or exited with an error,
	rather than gracefully rejecting the additional sessions.
	
	Deliverables:

	All SSH images

	Reference:

	QXCM1000456374, TCPIP_BUGS Note 3614

18-Sep-2007	Alpha and IA64

	Problem:

	When an SFTP client user issued a rename command for a file
	with an OpenVMS version number, an error was returned.  The
	file was not renamed.
	
	Deliverables:

	TCPIP$SSH_SFTP-SERVER2.EXE

	Reference:

	QXCM1000463757, TCPIP_BUGS Note 3615

28-Sep-2007	Alpha and IA64

	Problem:

	The SSH server did not provide a "password aging" message when
	the user logged into the system with a nearly expired password:

	WARNING - Your password expires on Saturday, 29-SEP-2007 08:10:14

	Deliverables:

	TCPIP$SSH_SSHD2.EXE

	Reference:

	QXCM1000446153, TCPIP_BUGS Note 3625

24-Oct-2007	Alpha and IA64

	Problem:

	During a forced password change, if the user tried to re-enter the
	old password as the new one, the SSH server would simply close the
	connection rather than displaying an error message and allowing
	the user to choose a different password.

	Deliverables:

	All SSH images

	Reference:

	QXCM1000459616, TCPIP_BUGS Note 3626

12-Nov-2007	Alpha and IA64

	Problem:

	An ACCVIO occurred in the SCP or SFTP client when the batch mode
	option ("-B") was used from a DCL procedure in a subprocess where
	SYS$OUTPUT or SYS$INPUT had been re-defined to point to a file.

	Deliverables:

	All SSH images

	Reference:

	TCPIP_BUGS Note 3631

 3-Dec-2007	Alpha and IA64

	Problem:

	During a forced password change, the SSH server did not perform
	weak password checking or system-dictionary checking on the
	proposed new password.
	
	Deliverables:

	All SSH images

	Reference:

	QXCM1000470479, TCPIP_BUGS Note 3634

10-Dec-2007	Alpha and IA64

	Problem:
	
	An SSH login via public key authentication could, if the target
	user had the DISFORCE_PWD_CHANGE flag set, improperly set the
	PWD_EXPIRED or PWD_EXPIRED2 flag, even though the expired
	password was not used.

	Deliverables:

	All SSH images

	Reference:

	QXCM1000751748, QXCM1000747350, QXCM1000751011, QXCM1000751748,
	TCPIP_BUGS Note 3636

14-Jan-2008	Alpha and IA64

	Problem:

	The LCD command in SFTP failed with a "CD failed" error if not
	yet connected to a remote sftp server, although it should still
	have been possible to change the local directory.  Also, the CD
	command returned the same error when an OpenVMS-style directory
	specification was used while connected to a non-OpenVMS server.

	Deliverables:

	All SSH images

	Reference:

	QXCM1000757137, TCPIP_BUGS Note 3639

---------------------------------------------------------------------------
Corrections for HP TCP/IP Services V5.5 failSAFE IP Images
---------------------------------------------------------------------------
ECO 1 updates
-------------
 4-Mar-2005	Alpha and IA64

	Problem:

	The UCP was permitted to call ACPCONTROL to create a
	zero-valued IP host address; this should be disallowed in
	order to avoid the resulting confusion.

	Deliverables:

	TCPIP$FAILSAFE.EXE

	Reference:

	PTR 70-5-2720, TCPIP_BUGS Note 3258

ECO 2 updates
-------------
1-Mar-2006	Alpha and IA64

	Problem:

	A customer was losing the default route during startup in
	one specific configuration.
	
	Deliverables:

	TCPIP$FAILSAFE.EXE

	Reference:

	70-5-2692

11-May-2006	Alpha and IA64

	Problem:

	Alignment faults were observed during failSAFE IP processing.
	
	Deliverables:

	TCPIP$FAILSAFE.EXE

	Reference:

	TCPIP_BUGS Note 3462

26-Jul-2006	Alpha and IA64

	Problem:

	FailSAFE IP would not read files in STREAM_LF format.
	
	Deliverables:

	TCPIP$FAILSAFE.EXE

	Reference:

	70-5-2692

2-Nov-2006	Alpha and IA64

	Problem:

	In some configurations, failSAFE IP would pick the wrong
	interface to monitor.  This was displayed on OPCOM and in the
	failSAFE IP log during startup.
	
	Deliverables:

	TCPIP$FAILSAFE.EXE

	Reference:

	70-5-3037, TCPIP_BUGS Note 3513

ECO 3 updates
-------------
31-Jan-2007	Alpha and IA64

	Problem:

	If the interface_list is not specified, then the default
	behavior should be to monitor *all* interfaces.  A previous
	ECO fix broke this default.

	Deliverables:

	TCPIP$FAILSAFE.EXE

	Reference:

	PTR 70-5-3074

 8-May-2007	Alpha and IA64

	Problem:

	With failSAFE IP, the default route was sometimes lost during
	a failover event.  The loss occurred only when an IPv6 address
	was configured.
	
	Deliverables:

	TCPIP$FAILSAFE.EXE

	Reference:

	75-118-364

19-Oct-2007	Alpha and IA64

	Problem:

	Under certain circumstances, only the first static route was
	reliably failing over.  This was typically the default route.
	
	Deliverables:

	TCPIP$FAILSAFE.EXE

	Reference:

	75-117-58

---------------------------------------------------------------------------
Corrections for HP TCP/IP Services V5.5 UCP Images
---------------------------------------------------------------------------
ECO 1 updates
-------------
 3-Nov-2004	Alpha and IA64

	Problem:

	Problems arose while generating db files when using
        the TCPIP CONVERT /UNIX BIND command.

	Deliverables:

	TCPIP$UCP.EXE

	Reference:

	PTR 70-5-2374, TCPIP_BUGS Note 3227

 3-Nov-2004	Alpha and IA64

	Problem:

	UCP allows illegal BIND Resolver search list (paths) to be
	defined.  These should be disallowed to avoid confusion.

	Deliverables:

	TCPIP$UCP.EXE

	Reference:

	PTR 70-5-2583, TCPIP_BUGS Note 3229

20-Nov-2004	Alpha and IA64

	Problem:

	Customers with only a TCPIP client license (or equivalent)
	were improperly denied the option to configure failSAFE IP.

	Deliverables:

	TCPIP$UCP.EXE

	Reference:

	PTR 70-102-2048, TCPIP_BUGS Note 3131

ECO 2 updates
-------------
28-Sep-2005	Alpha and IA64

	Problem:

	During startup of TCP/IP, the UCP created the interface
	addresses.  When it created an alias address, it would use the
	broadcast address from the previously configured interface.
	
	Deliverables:

	TCPIP$UCP.EXE

	Reference:

	70-5-2784, TCPIP_BUGS Note 3355

25-Apr-2005	Alpha and IA64

	Problem:

	The TCPIP SHOW CONFIGURATION NAME_SERVICE comamnd was triggering
	an audit event, when issued by a nonprivileged user, because it
	attempted to gain WRITE access to the TCPIP$CONFIGURATION.DAT
	file.
	
	Deliverables:

	TCPIP$UCP.EXE

	Reference:

	70-5-2882, QXCM1000302198

01-Jan-2006	Alpha and IA64

	Problem:

	Output from the TCPIP SHOW CONFIGURATION COMMUNICATION command
	was not pipe-friendly.
	
	Deliverables:

	TCPIP$UCP.EXE

	Reference:

	70-5-2775, QXCM1000229833

17-Mar-2006	Alpha and IA64

	Problem:

	The TCPIP SHOW ROUTE <dest>/mask command did not always work as
	expected.  In cases where mask length was greater than or equal to
	24, the response to this command was:
	
	%TCPIP-E-ROUTEERROR, error accessing routes database(TCPIP$ROUTE)
	-TCPIP-W-NORECORD, information not found
	
	Deliverables:

	TCPIP$UCP.EXE

	Reference:

	70-5-2925

26-Sep-2006	IA64 only

	Problem:

	Pressing CTRL/C during the output of a TCPIP SHOW HOST
	(/NOLOCAL) command could result in an ACCVIO.
	
	Deliverables:

	TCPIP$ACCESS_SHR.EXE

	Reference:

	75-118-17, TCPIP_BUGS Note 3503

10-Nov-2006	Alpha and IA64

	Problem:

	If the same TCPIP SET SERVICE command were entered twice, the
	second entry would add a new record to the service database
	rather than updating the existing one.
	
	Deliverables:

	TCPIP$ACCESS_SHR.EXE

	Reference:

	70-5-2886

ECO 3 updates
-------------
13-Apr-2007	Alpha and IA64

	Problem:

	While executing TCPIP$CONFIG.COM in an attempt to initially
	configure TCPIP, entering a very long domain name could
	trigger a failure, making it impossible to configure the
	system.  The underlying cause was a failing TCPIP SHOW
	CONFIGURATION COMMUNICATION /OUTPUT=filename command, which
	had an 80-character line length limitation.

	Deliverables:

	TCPIP$UCP.EXE

	Reference:

	PTR 70-5-3107

 8-May-2007	Alpha and IA64

	Problem:

	The TCPIP SHOW COMMUNICATION command truncates its output when
	the domain name is more than 29 characters long.

	Deliverables:

	TCPIP$UCP.EXE

	Reference:

	QXCM1000420508

18-May-2007	Alpha and IA64

	Problem:

	The SET NAME_SERVICE /INITIALIZE /CLUSTER command attempts to
	find the file TCPIP$BIND_RUNNING_*.DAT;* but fails because the
	semantics of the TCPIP$BIND_COMMON logical name have changed.

	Deliverables:

	TCPIP$UCP.EXE

	Reference:

	QXCM1000422519

29-May-2007	Alpha and IA64

	Problem:

	When used with the DCL command PIPE, the output from a TCPIP SHOW
	DEVICE_SOCKET command is not properly formatted.

	Deliverables:

	TCPIP$UCP.EXE

	Reference:

	QXCM1000421550

---------------------------------------------------------------------------
Corrections for HP TCP/IP Services V5.5 RMT Images
---------------------------------------------------------------------------
ECO 2 updates
-------------
22-Nov-2005	Alpha and IA64

	Problem:

	The RMT server did not work with Solaris clients.
	
	Deliverables:

	TCPIP$RMT.EXE

	Reference:

	70-5-2740, TCPIP_BUGS Note 3367

---------------------------------------------------------------------------
Corrections for HP TCP/IP Services V5.5 RPCGEN Images
---------------------------------------------------------------------------
ECO 2 updates
-------------
22-Nov-2005	Alpha and IA64

	Problem:

	RPCGEN generates C code, which contains calls to certain C RTL
	routines.  It was omitting the include file PMAP_CLNT.H that
	prototypes the pmap functions, so the compiler displayed the
	informational message %CC-I-IMPLICITFUNC when the resultant code
	was compiled.
	
	Also, when invoked WITHOUT the /HEADER qualifier, RPCGEN ignored
	lines in the input file that began with a % (percent sign).
	
	Deliverables:

	TCPIP$RPCGEN.EXE

	Reference:

	70-2-2870, 70-5-2871, Note 10773, TCPIP_BUGS Note 3368

---------------------------------------------------------------------------
Corrections for HP TCP/IP Services V5.5 R-Tools Images
---------------------------------------------------------------------------
ECO 2 updates
-------------
24-Nov-2005	Alpha and IA64

	Problem:

	The way RLOGIN was parsing its command line parameter was subject
	to break "RLOGIN 0".  Even though the library changes that
	trigger the failure have not yet been incorporated into the V5.5
	maintenance stream, the parsing was made more robust.
	
	Deliverables:

	TCPIP$RLOGIN.EXE

	Reference:

	30-15-107

07-Dec-2005	Alpha and IA64

	Problem:

	The way RSH was parsing its command line parameter was subject to
	break "RSH 0".  Even though the library changes that trigger the
	failure have not yet been incorporated into the V5.5 maintenance
	stream, the parsing was made more robust.
	
	Deliverables:

	TCPIP$RSH.EXE

	Reference:

	75-109-934

20-Feb-2006	Alpha and IA64

	Problem:

	The RCP command always returned an error status when the /LOG
	option was used, even if the command completed successfully.
	
	Deliverables:

	TCPIP$RCP.EXE

	Reference:

	70-5-2908, QXCM1000314037

07-Mar-2006	Alpha only

	Problem:

	Use of the /ESCAPE_CHARACTER qualifier on the RSH command might
	trigger an ACCVIO.
	
	Deliverables:

	TCPIP$RSH.EXE

	Reference:

	30-15-115

12-May-2006	Alpha and IA64

	Problem:

	RCP could not locate a file when the current directory was set to
	a search list.
	
	Deliverables:

	TCPIP$RCP.EXE

	Reference:

	75-109-1366

---------------------------------------------------------------------------
Corrections for HP TCP/IP Services V5.5 TCPIP$CONFIG Procedure
---------------------------------------------------------------------------
ECO 2 updates
-------------
01-Dec-2005	Alpha and IA64

	Problem:

	White-space characters could be introduced via TCPIP$CONFIG.COM's
	way of specifying the domain name.  This, in turn, affected
	delivery or reception of mail via SMTP.
	
	Deliverables:

	TCPIP$CONFIG.COM

	Reference:

	70-5-2838, QXCM1000247548

12-Jan-2006     Alpha and IA64

        Problem:

        Default for question about creating new server host key from
        TCPIP$CONFIG.COM when enabling ssh was always be "Y".
        If both files exist for the key, default should be "N".

        Deliverables:

        TCPIP$CONFIG.COM

        Reference:

        PTR 30-13-156
        TCPIP_BUGS Note 3388

ECO 3 updates
-------------
 8-May-2007	Alpha and IA64

	Problem:

	TCPIP$CONFIG did not detect the presence of a network device
	whose controller letter was out of alphabetical sequence.  For
	example, EIB0 was detected only if EIA0 also existed.  If EIB
	was by itself, the EI controller did not appear at all in the
	interface menu.
	
	Deliverables:

	TCPIP$CONFIG.COM

	Reference:

	75-118-22

---------------------------------------------------------------------------
Corrections for HP TCP/IP Services V5.5 TCPTRACE/TCPDUMP Images
---------------------------------------------------------------------------
ECO 2 updates
-------------
03-Mar-2006	Alpha and IA64

	Problem:

	When using the TCPTRACE /PACKETS=n command, the specified packet
	count was not accurately measured and enforced.
	
	Deliverables:

	TCPIP$TRACE.EXE

	Reference:

	70-5-2899

ECO 3 updates
-------------
 6-Feb-2007	Alpha and IA64

	Problem:

	Even when given invalid command line arguments, TCPDUMP would
	exit with a success status.  It should exit with something more
	descriptive, such as %SYSTEM-E-ABORT (condition code 42).

	Deliverables:

	TCPIP$TCPDUMP.EXE

	Reference:

	PTR 70-5-3072

---------------------------------------------------------------------------
Corrections for HP TCP/IP Services V5.5 SNMP Images
---------------------------------------------------------------------------
ECO 2 updates
-------------
17-Mar-2006	Alpha and IA64

	Problem:

	The SNMP polling interval could not be changed; a value specified
	in the TCPIP$SNMP_POLL_TIME logical name was ignored.
	
	Deliverables:

	TCPIP$HR_MIB.EXE
	TCPIP$OS_MIBS.EXE

	Reference:

	70-5-2814, 70-5-2929, QXCM1000240649, QXCM1000321350

---------------------------------------------------------------------------
Corrections for HP TCP/IP Services V5.5 LOCKD Images
---------------------------------------------------------------------------
ECO 2 updates
-------------
8-Aug-2006	Alpha and IA64

	Problem:

	LOCKD temporary files were not being removed from
	SYS$SYSDEVICE:[TCPIP$NFSLCK] when they were no longer needed.
	The files were named LOCKDxxxxPID.;1, where xxxx was a unique
	series of letters and PID was the ID of the LOCKD process.
	
	The files were zero blocks in size, but the customer was
	concerned about the effect of leaving these files unchecked
	in a production environment.
	
	Deliverables:

	TCPIP$LOCKD_RUN.COM

	Reference:

	70-5-2973, Note 10956, TCPIP_BUGS Note 3486