Process Software SSH for OpenVMS (PSCSSH) V3.0 Release Notes June 2025 This document contains a list of new features and bug fixes that have been made since SSH for OpenVMS V2.4. Revision/Update Information: This document supersedes the SSH for OpenVMS V2.4 Release Notes Unpublished - all rights reserved under the copyright laws of the United States No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any language or computer language, in any form or by any means electronic, mechanical, magnetic, optical, or otherwise without the prior written permission of: Process Software, LLC P.O. Box 922 Framingham, MA 01701 USA Voice: +1 508 879 6994; FAX: +1 508 879 0042 info@process.com Process Software, LLC ("Process") makes no representations or warranties with respect to the contents hereof and specifically disclaims any implied warranties of merchantability or fitness for any particular purpose. Furthermore, Process Software reserves the right to revise this publication and to make changes from time to time in the content hereof without obligation of Process Software to notify any person of such revision or changes. o Alpha AXP, AXP, MicroVAX, OpenVMS, VAX, VAX Notes, VMScluster, and VMS are registered trademarks of Hewlett-Packard Corporation. o Kerberos. Copyright © 1989, DES.C and PCBC_ENCRYPT.C Copyright © 1985, 1986, 1987, 1988 by Massachusetts Institute of Technology. Export of this software from the United States of America is assumed to require a specific license from the United States Government. It is the responsibility of any person or organization contemplating export to obtain such a license before exporting. WITHIN THAT CONSTRAINT, permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of M.I.T. not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. M.I.T. makes no representations about the suitability of this software for any purpose. It is provided "as is" without express or implied warranty. o MultiNet is a registered trademark of Process Software. o Secure Shell (SSH). Copyright © 2000. This License agreement, including the Exhibits (Agreement), effective as of the latter date of execution (Effective Date), is hereby made by and between Data Fellows, Inc., a California corporation, having principal offices at 675 N. First Street, 8th floor, San Jose, CA 95112170 (Data Fellows) and Process ii Software, LLC, having a place of business at 959 Concord Street, Framingham, MA 01701 (OEM). o TCPware is a registered trademark of Process Software. o UNIX is a trademark of UNIX System Laboratories, Inc. o All other trademarks, service marks, registered trademarks, or registered service marks mentioned in this document are the property of their respective holders. o Copyright ©1997, 1998, 1999, 2000 Process Software Corporation. All rights reserved. Printed in USA. o Copyright ©2000, 2001, 2002, 2004, 200, 2024 Process Software, LLC. All rights reserved. Printed in USA. o If the examples of URLs, domain names, internet addresses, and web sites we use in this documentation reflect any that actually exist, it is not intentional and should not be considered an endorsement, approval, or recommendation of the actual site, or any products or services located at any such site by Process Software. Any resemblance or duplication is strictly coincidental. iii ________________________________________________________________ Contents ________________________________________________________________ CHAPTER 1 INTRODUCTION 1-1 __________________________________________________________ 1.1 TYPOGRAPHICAL CONVENTIONS 1-1 __________________________________________________________ 1.2 OBTAINING TECHNICAL SUPPORT 1-2 1.2.1 Before Contacting Technical Support 1-3 1.2.2 Sending Electronic Mail 1-5 1.2.3 Calling Technical Support 1-5 1.2.4 Contacting Technical Support by Fax 1-6 __________________________________________________________ 1.3 OBTAINING ONLINE HELP 1-6 __________________________________________________________ 1.4 ACCESSING THE SSH FOR OPENVMS PUBLIC MAILING LIST 1-6 __________________________________________________________ 1.5 PROCESS SOFTWARE WORLD WIDE WEB SERVER 1-7 __________________________________________________________ 1.6 OBTAINING SOFTWARE PATCHES OVER THE INTERNET 1-7 __________________________________________________________ 1.7 DOCUMENTATION COMMENTS 1-8 __________________________________________________________ 1.8 NOTE CONCERNING KERBEROS V5 1-9 __________________________________________________________ 1.9 NOTE CONCERNING VAX V5.5-2 1-9 __________________________________________________________ 1.10 NOTE: CONCERNING SSH SESSIONS 1-9 iii Contents ________________________________________________________________ CHAPTER 2 CHANGES AND ENHANCEMENTS 2-1 __________________________________________________________ 2.1 SSH FOR OPENVMS V3.0 INSTALLATION NOTE 2-1 __________________________________________________________ 2.2 NEW FEATURES 2-1 ________________________________________________________________ CHAPTER 3 DOCUMENTATION UPDATES 3-1 __________________________________________________________ 3.1 PSCSSH V3.0 3-1 __________________________________________________________ 3.2 CORRECTIONS TO THE PSCSSH V3.0 DOCUMENTATION 3-1 ________________________________________________________________ CHAPTER 4 KNOWN BUGS/ISSUES 4-1 ________________________________________________________________ TABLES 1-1 Typographical Conventions 1-1 1-2 System Information 1-4 2-1 PSCSSH Logicals defined and used by PSCSSH 2-2 2-2 PSCSSH Logicals that control how PSCSSH works 2-3 2-3 SFTP logicals are primarily used only by the SFTP server. 2-5 iv _______________________________________________________ 1 Introduction These Release Notes describe the changes and enhancements made to the PSCSSH (formerly SSH for OpenVMS) product in version 3.0. This chapter describes conventions used in the SSH for OpenVMS documentation set and the various methods to contact and receive technical support. o For information about product changes and enhancements in the SSH for OpenVMS V3.0 Consolidated Distribution, refer to Chapter 2 of these Release Notes. o For information about changes to the documentation set, refer to Chapter 3 of these Release Notes. __________________________________________________________ 1.1 Typographical Conventions Examples in these Release Notes use the following conventions: ________________________________________________________________ Table 1-1 Typographical Conventions _______________________________________________________ Convention_______Example__________Meaning______________ Angle brackets Represents a key on your keyboard. Angle brackets Indicates that you with a slash hold down the key labeled or while simultaneously pressing another key; in this example, the A key. 1-1 Introduction Typographical Conventions ________________________________________________________________ Table 1-1 (Cont.) Typographical Conventions _______________________________________________________ Convention_______Example__________Meaning______________ Square brackets [FULL] Indicates optional choices; you can enter none of the choices, or as many as you like. When shown as part of an example, square brackets are actual characters you should type. Underscore or file_name or Between words in hyphen file-name commands, indicates the item is a single ___________________________________________element._____________ __________________________________________________________ 1.2 Obtaining Technical Support Process Software provides technical support if you have a current Maintenance Service Agreement. If you obtained SSH for OpenVMS from an authorized distributor partner, you receive your technical support directly from them. You can contact Technical Support by: o Sending electronic mail (Section 1.2.2) o Calling Technical Support (Section 1.2.3) o Faxing a description of your problem to the Technical Support Group (Section 1.2.4) 1-2 Introduction Obtaining Technical Support _____________________________ 1.2.1 Before Contacting Technical Support Before you call, or send email or a fax: 1 Verify that your Maintenance Service Agreement is current. 2 Read the online Release Notes completely. 3 Have the following information available: o Your name o Your company name o Your email address o Your voice and fax telephone numbers o Your Maintenance Contract Number o OpenVMS architecture o OpenVMS version o SSH for OpenVMS layered products and versions 4 Have complete information about your configuration, error messages that appeared, and problem specifics. 5 Be prepared to let a development engineer connect to your system, either with TELNET or by dialing in using a modem. Be prepared to give the engineer access to a privileged account to diagnose your problem. You can obtain information about your OpenVMS architecture, OpenVMS version, SSH for OpenVMS version, and layered products with the SSH for OpenVMS SSHCTRL VERSION command and some VMS DCL commands. Execute the following commands on a fully loaded system and email the output to support@process.com: 1-3 Introduction Obtaining Technical Support $ sshctrl version SSHCTRL-S-SSHCTRLVERS, This is SSHCTRL V1.0 $ show system/noprocess OpenVMS V8.4-2LH1 on node BEANS 16-JUL-2024 13:49:19.16 Uptime 0 03:08:21 $ write sys$output f$getsyi("arch_name") Alpha $ In this example: The machine or system architecture is Alpha. The OpenVMS version is V8.4-2LH1. The PSCSSH version is V3.0. Use the following table as a template to record the relevant information about your system: ________________________________________________________________ Table 1-2 System Information _______________________________________________________ Your System Required_Information_______________Information_________ Your name Company name Your email address Your voice and fax telephone numbers System architecture VAX or Alpha OpenVMS version _________SSH_for_OpenVMS_version________________________________ Please provide information about installed SSH for OpenVMS applications and patch kits, by sending a copy of MULTINET:SSH_VERSION.; file. 1-4 Introduction Obtaining Technical Support _____________________________ 1.2.2 Sending Electronic Mail For many questions, electronic mail is the preferred communication method. Technical Support via electronic mail is available to customers with a current support contract. Send electronic mail to support@process.com. At the beginning of your mail message, include the information listed in Section 1.2.1. Continue with the description of your situation and problem specifics. Include all relevant information to help your Technical Support Specialist process and track your electronic support request. Electronic mail is answered within the desired goal of two hours, during our normal business hours, Monday through Friday from 8:30 a.m. to 5:00 p.m., United States Eastern Time. _____________________________ 1.2.3 Calling Technical Support For regular support issues, call 800-394-8700 or 508- 628-5074 for support Monday through Friday from 8:30 a.m. to 7:00 p.m., United States Eastern Time. For our customers in North America with critical problems, an option for support 7 days per week, 24 hours per day is available at an additional charge. Please contact your Account Representative for further details. Before calling, have available the information described in Section 1.2.1. When you call, you will be connected to a Technical Support Specialist. Be prepared to discuss problem specifics with your Technical Support Specialist and to let that person connect to your system. If our Support Specialists are assisting other customers and you are put on hold, please stay on the line. Most calls are answered in less than five minutes. If you cannot wait for a Specialist to take your call, please take advantage of our automatic call 1-5 Introduction Obtaining Technical Support logging feature by sending email to support@process.com (see the Section on Sending Electronic Mail). _____________________________ 1.2.4 Contacting Technical Support by Fax You can send transmissions directly to Technical Support at 508-879-0042. Before faxing comments or questions, complete the steps in Section 1.2.1 and include all your system information at the beginning of your fax message. Continue with the description of your situation and problem specifics. Include all relevant information to help your Technical Support Specialist process and track your fax support request. Faxed questions are answered Monday through Friday from 8:30 a.m. to 7:00 p.m., United States Eastern Time. __________________________________________________________ 1.3 Obtaining Online Help Extensive information about SSH for OpenVMS is provided in the SSH for OpenVMS help library. For more information, enter the following command: $ HELP SSH __________________________________________________________ 1.4 Accessing the SSH for OpenVMS Public Mailing List Process Software maintains two public mailing lists for SSH for OpenVMS customers: o Info-SSH@process.com o SSH-Announce@process.com The Info-SSH@process.com mailing list is a forum for discussion among SSH for OpenVMS system managers and programmers. Questions and problems regarding SSH for OpenVMS can be posted for a response by any of the subscribers. To subscribe to Info-SSH, send a mail message with the word SUBSCRIBE in the body to Info- SSH-request@process.com. 1-6 Introduction Accessing the SSH for OpenVMS Public Mailing List You can retrieve the Info-SSH archives by anonymous FTP to ftp.multinet.process.com. The archives are located in the directory [MAIL_ARCHIVES.INFO-SSH]. The SSH-Announce@process.com mailing list is a one-way communication (from Process Software to you) used to post announcements relating to SSH for OpenVMS (patch releases, product releases, etc.). To subscribe to SSH- Announce, send a mail message with the word SUBSCRIBE in the body to SSH-Announce-request@process.com. __________________________________________________________ 1.5 Process Software World Wide Web Server Electronic support is provided through the Process Software web site which you can access with any World Wide Web browser; the URL is http://www.process.com (select SSH for OpenVMS) or use the URL http://www.process.com/techsupport/ssh.html __________________________________________________________ 1.6 Obtaining Software Patches over the Internet Process Software provides software patches in save set and ZIP format on its anonymous FTP server, ftp.multinet.process.com. For the location of software patches, read the .WELCOME file in the top-level anonymous directory. This file refers you to the directories containing software patches. Enter the following at the FTP prompt: FTP.MULTINET.PROCESS.COM>CD [.PATCHES.SSHxxx] FTP.MULTINET.PROCESS.COM>GET update_filename In these commands: emailaddress is your email address in the standard user@host format xxx is the version of SSH for OpenVMS you want to transfer update_filename is the name of the file you want to transfer 1-7 Introduction Obtaining Software Patches over the Internet To transfer files from Process Software directly to an OpenVMS system, you can use the GET command without any other FTP commands. However, if you need to transfer a software patch through an intermediate non-OpenVMS system, use BINARY mode to transfer the files to and from that system. In addition, if you are retrieving the software patch in save set format, make sure the save set record size is 2048 bytes when you transfer the file from the intermediate system to your OpenVMS system. o If you use the GET command to download the file size from the intermediate system, use the FTP RECORD- SIZE 2048 command before transferring the file. o If you use the PUT command to upload the file to your OpenVMS system, log into the intermediate system and use the FTP quote site rms recsize 2048 command before transferring the file. Process Software also supplies UNZIP utilities for OpenVMS VAX and Alpha for decompressing ZIP archives in the [PATCHES] directory. To use ZIP format kits, you need a copy of the UNZIP utility. The following example shows how to use UNZIP utility, assuming you have copied the appropriate version of UNZIP.EXE to your current default directory: $ UNZIP := $SYS$DISK:[]UNZIP.EXE $ UNZIP filename.ZIP Use VMSINSTAL to upgrade your SSH for OpenVMS system with the software patch. __________________________________________________________ 1.7 Documentation Comments Your comments about the information in these Release Notes can help us improve the documentation. If you have corrections or suggestion for improvement, please let us know. 1-8 Introduction Documentation Comments Be as specific as possible about your comments: include the exact title of the document, version, date, and page references as appropriate. You can send your comments by email to techpubs@process.com or mail them to: Process Software P.O. Box 922 Framingham, MA 01701 Attention: Marketing Director You can also fax your comments to us at 508-879-0042. Your comments about our documentation are appreciated. __________________________________________________________ 1.8 Note Concerning Kerberos V5 SSH for OpenVMS supports Kerberos V5. Kerberos V5 requires Kerberos for HP OpenVMS. VMS V8 systems are distributed with Kerberos V5, and pre-V8 systems (OpenVMS VAX V7.3 and OpenVMS AXP v7.2-3, 7.3-*) can download Kerberos V5 from the HP website. The Kerberos V5 applications can also run with any Kerberos V5 compliant Key Distribution Center (KDC) software. __________________________________________________________ 1.9 Note Concerning VAX V5.5-2 You must install the DEC C 6.0 backport library on all OpenVMS VAX v5.5-2 systems prior to using SSH. This is the AACRT060.A file. You can find the ECO on the SSH for OpenVMS CD in the following directory: VAX55_DECC_ RTL.DIR. __________________________________________________________ 1.10 Note: Concerning SSH Sessions For each active SSH session two(2) channels are used. Please adjust the CHANNELCNT parameter to account for this usage. 1-9 _______________________________________________________ 2 Changes and Enhancements This chapter describes the changes and enhancements made for PSCSSH V3.0. __________________________________________________________ 2.1 SSH for OpenVMS V3.0 Installation Note SSH for OpenVMS V3.0 installations may only be performed from a random-access device (e.g., disk or CD-ROM). If the SSH for OpenVMS V3.0 installation is attempted from a sequential-access device (e.g., magtape or TKxx cartridge), the installation will fail. If the distribution savesets have been copied to a sequential-access device (for transporting them, for example), they must be copied to a disk for installation. __________________________________________________________ 2.2 New Features This update contains numerous new features, enhancements, and fixes over the original SSH for OpenVMS V2.4 release. Customers who have kept up with the ECO releases have most of these changes already. This release is primarily a rebranding release to provide catch-up so new customers don't also have to install an ECO kit to get current. This release adds support for running on OpenVMS X86_64 V9.2-3 or later. With this release, the product is now known as PSCSSH. Previous releases used the directory tree for our MultiNet product, and logical names and commands matched the MultiNet counterparts. All of that has changed. The product is now installed into a simpler PSCSSH tree, and all logical names are prefixed with "PSCSSH_". 2-1 Changes and Enhancements New Features To see the very long list of actual changes to the product over the years since the V2.4 release, please visit this webpage: https://multinet.process.com/scripts/eco/eco_tlb.com?SSHB-053_A056 PSCSSH uses the following logicals. Not all logicals are defined. Many can be defined to change the behavior of the SSH client and the SSH server. ________________________________________________________________ Table 2-1 PSCSSH Logicals defined and used by PSCSSH _______________________________________________________ PSCSSH The location of the PSCSSH installation. PSCSSH_ROOT The rooted location of the PSCSSH installation. PSCSSH_COMMON The location of the common PSCSSH directory. PSCSSH_EXE The location of the architecture- specific executables. PSCSSH_HELP The location of the PSCSSH online help library. PSCSSH_LOCAL The location of the node-specific files. PSCSSH_LOCAL_ROOT The rooted location of the node- specific files. PSCSSH_SSH2_HOSTKEY_ The location of the system-level DIR host-key files. PSCSSH_SSH2_ The location of the system-level KNOWNHOSTS_DIR known-hosts files. SSH2_DIR Location of the node-specific SSH2 files. SSH_DIR Location of the node-specific SSH1 files. SSH_EXE A synomym for PSCSSH_EXE: that is used by some components. 2-2 Changes and Enhancements New Features ________________________________________________________________ Table 2-1 (Cont.) PSCSSH Logicals defined and used by PSCSSH _______________________________________________________ SSH_LOG Logical of the node-specific session log files. SSH_MAX_SESSIONS Specifies the maximum number of simultaneous SSH sessions that _______________________________are_allowed._____________________ ________________________________________________________________ Table 2-2 PSCSSH Logicals that control how PSCSSH works _______________________________________________________ SSH_NEW_STATUS_CODES By default, the SSH applications return UNIX-style status codes. Defining this logical causes them to return status codes that are more VMS-like. SSH_VMS_ONLY_STATUS Defines whethers status codes are VMS-style or UNIX-style. The value is a boolean that defaults to false. SSH_LOG_ACCEPTS Defined to log accepted connections to SSH_LOG_MBX SSH_LOG_REJECTS Defined to log rejected connections to SSH_LOG_MBX SSH_STEP_THROUGH_ For RADIUS server lookups, this RADIUS_ADDRESSES controls whether or not all IP addresses returned from the server are tried. By default, only the first address is used. SSH_COMMAND_OLD_ Controls how termination status STYLE is obtained from subsystems and servers. SSH2_HOSTKEY_DIR Specifies the location of the system-level host key directory. SSH_KEYGEN2_MIN_PW_ Specifies the minimum passphrase LEN length for private keys. 2-3 Changes and Enhancements New Features ________________________________________________________________ Table 2-2 (Cont.) PSCSSH Logicals that control how PSCSSH works _______________________________________________________ SSH_CMD_FILE_DIR Specifies the location used for temporary command files created by SFTP, SCP, and the PUBLICKEY Assistant. The default location is SYS$LOGIN:[.SSH2]. SSH_SERVER_PIPE_SIZE Specifies the size in bytes (minimum 1024) of the pipe that SSHD uses to send data to SFTP_ SERVER and Publickey Server. SSH_PIPE_SIZE Specifies the size in bytes (minimum 1024) of the pipe that SFTP/SCP/PUBLICKEY Assistant use to pass data to SSH to be conveyed to remote systems. SSH_NO_LEADING_ Controls whether or not a leading SPACE_NEWLINE space (blank line) is presented when starting a subsystem. SSH2_SERVER_DEBUG_ If defined, causes the SSHD NOCR log file to use only linefeeds between lines. The default is that each line is terminated with a carriage-return/linefeed pair. SSH_USE_OLD_EXPIRED_ Determine hows expired-password PASSWORD_SCHEME updates are done. The default is to use SSH protocol calls. This logical allows the use of an alternate method by starting a session just to change the password. SSH_WARN_CHILD_EXIT If defined, the child (SSH) status is returned to the terminal when running SFTP/SCP/etc. SSH_ACCESS_USE_LOCAL If defined, causes SSH to use VMS local access mask instead of the network access mask. 2-4 Changes and Enhancements New Features ________________________________________________________________ Table 2-2 (Cont.) PSCSSH Logicals that control how PSCSSH works _______________________________________________________ SSH_DONT_SAVE_ If defined, the group name is not _________GROUPNAME_____________used_when_checking_rights_lists._ ________________________________________________________________ Table 2-3 SFTP logicals are primarily used only by the SFTP server. _______________________________________________________ SFTP_IDLE_TIMEOUT Specified the number of seconds before an idle SFTP_SERVER will exit on its own. The default is 75 seconds. SFTP_VMS_MODE_BY_ This boolean value determines DEFAULT whether or not the /VMS qualifier is to be used by default for the SFTP client. The default is false. SFTP_USE_SRI_ If defined, SRI encoding is ENCODING_ON_ODS5 forced on ODS-5 disks. By default, SRI encoding is not used for ODS-5 disks. SFTP_STAT_ Controls whether or not the DESTINATION_FILE destination file is STATed before an open is attempted. The default value is true. Defineing as false allows SFTP to work with Sterling Commerce's Enterprise:Connect. SFTP_STAT_ Similar to SFTP_STAT_DESTINATION_ DESTINATION_ FILE, except if refers to the DIRECTORY destination directory. SFTP_DEFAULT_SIZE If defined, SFTP does not attempt to set the size of the file to truncate an existing file. 2-5 Changes and Enhancements New Features ________________________________________________________________ Table 2-3 (Cont.) SFTP logicals are primarily used only by the SFTP server. _______________________________________________________ SFTP_SEND_CREATE_ Specifies a boolean value to ATTRIBUTES control whether or not source file attributes are sent as part of the create operation. The default is false. SFTP_MAXIMUM_ Specifies the maximum SFTP PROTOCOL_VERSION protocol version supported. The default is 3. Other are values that may be specified are 2 and 4. SFTP_DEFAULT_GROUP Specifies the default group used in attributes when SFTP protocol version is 4 or greater. SFTP_DEFAULT_SIZE Specifies the default size when the SFTP server doesn't return the size of a file. SFTP_NEWLINE_STYLE Specifies the newline style to use for text files when undefined: UNIX and VMS get ' SFTP_TRANSLATE_VMS_ Specifies which file types FILE_TYPES will be translated to stream by default. The default value is 7, which is all files. Other values are 1 for fixed files, 2 for variable-length (normal VMS text files), and 4 for variable- length, fixed control files. SFTP_IGNORE_SSH_FXF_ Specifies a boolean to control TRUNC whether or not a file open should observe the truncate flag. The default is false. SFTP_MAX_PRE_ Specifies the maximum size to ALLOCATION pre-allocate for a file when the size of the file being copied is known. 2-6 Changes and Enhancements New Features ________________________________________________________________ Table 2-3 (Cont.) SFTP logicals are primarily used only by the SFTP server. _______________________________________________________ SFTP_OPEN_AS_BINARY Controls whether or not files are opened as binary files instead of stream. The default value is false, which means files are opened as streams. SFTP_DONT_TRUNCATE Specifies whether or not files are truncated as part of an fsetstat operation. The default is false. SFTP_CASE_ When defined, file names are INSENSITIVE treated case-insensitively (lowercase is assumed). SFTP_ADD_ODS5_CARETS Specifies a boolean value to control whether or not carets are added to the displayed name for ODS5 devices. The default is false. SFTP_REMOVE_ODS5_ Specifies a boolean value CARETS to control whether or not decc$translate_vms is used to remove quoting characters on ODS- 5 disks. The default is false. SFTP_HANDLE_ODS5_ Synonym for SFTP_ADD_ODS5_CARETS CARETS and SFTP_REMOVE_ODS5_CARETS. SFTP_ODS2_SRI_ Specifies a boolean value to ENCODING control whether or not file names are SRI-encoded on ODS-2 disks. The default is false. SFTP_FALLBACK_TO_CBT Specified a boolean value to control whether or not a VMS contiguous file will be opened as "contiguous, best try" if insufficient space is available for contiguous. The default value is false. 2-7 Changes and Enhancements New Features ________________________________________________________________ Table 2-3 (Cont.) SFTP logicals are primarily used only by the SFTP server. _______________________________________________________ SFTP_FILE_ESTIMATE_ Specifies the size in blocks THRESHOLD to use as an estimate for VMS Variable and Variable with Fixed control files. SFTP_VMS_ALL_ Specifies a boolean value to VERSIONS control whether or not all versions of a file are displayed in directory listings. The default value is false. SFTP_RETURN_ALQ Specifies a boolean value to control whether or not the allocation quantity is included in VMS characteristics when copying between VMS systems. Note that some files force it. The default value is false. SFTP_SET_VMS_ Specifies a boolean value to PROTECTION control whether VMS protection attributes are included in transfers between VMS systems. The default value is true. SFTP_DEFAULT_FILE_ Specifies a boolean value to TYPE_REGULAR force file types from Unknown to Regular when attributes don't specify the file type. The default value is false. SFTP_SEND_VENDOR_ID Specifies a boolean value that controls whether the SFTP client sends vendor id information when establishing a connection to the SFTP server. The default value is true. 2-8 Changes and Enhancements New Features ________________________________________________________________ Table 2-3 (Cont.) SFTP logicals are primarily used only by the SFTP server. _______________________________________________________ SFTP_DIRECTORY_WITH_ Specifies a boolean value to CREATION_DATE control whether or not the SFTP client displays the file creation date in directory listings when the date is present. The string "unknown" will be used when the attributes don't include a create time. The default value is false. SFTP_ALWAYS_SEND_ Specifies a boolean value to VMS_INFORMATION control whether or not VMS attributes are returned to a VMS client. The default value is true. SCP2_VMS_MODE_BY_ This is the SCP version of SFTP_ DEFAULT VMS_MODE_BY_DEFAULT. SSH_PUBLICKEY_ Specifies how long the publickey SERVER_IDLE_TIMEOUT server should allow itself to be idle. SSH_SCP_SERVER_DEBUG Specifies the debug level for the SCP Server. SSH_PUBLICKEY_ Specifies the debug level for the SERVER_DEBUG publickey server. SSH_SFTP_SERVER_ Specified the debug level used DEBUG for debugging the SFTP Server. If defined, debug information is written to SYS$LOGIN:SFTP- SERVER.LOG. A value between 2 and 6 can be specified to control how much debugging information is _______________________________logged.__________________________ 2-9 _______________________________________________________ 3 Documentation Updates This chapter contains a summary of changes to the documentation for PSCSSH V3.0. __________________________________________________________ 3.1 PSCSSH V3.0 o Changed the product name from "SSH for OpenVMS" to "PSCSSH" and the version number to V3.0. __________________________________________________________ 3.2 Corrections to the PSCSSH V3.0 documentation 3-1 _______________________________________________________ 4 Known Bugs/Issues The following are known bugs and issues with PSCSSH V3.0. o The SFTP2 and SCP2 client programs do not properly operate when SFTP protocol version 2 is in use. Very few implementations are still using protocol version 2, most are using verion 3 or version 4. 4-1