login about faq

Tectia Client/Server, Server for IBM z/OS and ConnectSecure 6.3.8 were released on October 8. What's new in these releases?

asked Oct 08 '13 at 15:07

SSH%20KB's gravatar image

SSH KB ♦
509249246237


Tectia Client/Server, Server for IBM z/OS, ConnectSecure 6.3.8 are maintenance releases introducing the following bug fixes:

Tectia Client

  • All Platforms: Fixed the ssh-keygen-g3 option -m/--generate-moduli-file.

  • All platforms: Fixed a problem that caused Tectia Client applications (e.g. sshg3/sftpg3/scpg3) to fail intermittently when ssh-broker-g3 was used in the run-on-demand mode.

  • All Platforms: Fixed a problem in agent forwarding with certificates. When multiple sessions were open to a remote server and in those sessions connections to other remote server(s) were initiated, agent forwarding would forward certificates only for one of the connections.

  • Windows: Fixed Tectia command-line clients to assume default window size if they cannot obtain a proper value from the system.

  • Windows: Fixed Tectia command-line clients to properly show authentication prompts in nested connections. Previously, when a user had a terminal session to Tectia Server on Windows running in terminal mode "Stream" and within that session the user started a new Tectia Client connection (from the host running Tectia Server), the authentication prompts were not shown properly.

Tectia ConnectSecure

  • All Platforms: Fixed the ssh-keygen-g3 option -m/--generate-moduli-file.

  • All Platforms: Fixed a problem that blocked FTP-SFTP conversion connections. If an FTP-SFTP conversion connection got stuck at a certain stage while establishing the session, all consecutive FTP-SFTP conversion connections were blocked.

  • All platforms: Fixed a problem that caused Tectia Client applications (e.g. sshg3/sftpg3/scpg3) to fail intermittently when ssh-broker-g3 was used in the run-on-demand mode.

  • All Platforms: Fixed a problem in agent forwarding with certificates. When multiple sessions were open to a remote server and in those sessions connections to other remote server(s) were initiated, agent forwarding would forward certificates only for one of the connections.

  • Windows: Fixed Tectia command-line clients to assume default window size if they cannot obtain a proper value from the system.

  • Windows: Fixed Tectia command-line clients to properly show authentication prompts in nested connections. Previously, when a user had a terminal session to Tectia Server on Windows running in terminal mode "Stream" and within that session the user started a new Tectia Client connection (from the host running Tectia Server), the authentication prompts were not shown properly.

Tectia Server

  • All Platforms: Fixed the ssh-keygen-g3 option -m/--generate-moduli-file.

  • All Platforms: In the past, when a version exchange failure occurred, Tectia Server only generated audit message '403 Version_exchange_failure'. Now it also generates audit message '402 Disconnect' (if allowed by the server configuration). Additionally, a new field 'Session-Id' was added to audit message 403.

  • Windows: Tectia Server Configuration GUI now allows more than 1000 rules on pages Connections and Encryption, Authentication, and Services.

Tectia Server for IBM z/OS

  • All Platforms: Fixed the ssh-keygen-g3 option -m/--generate-moduli-file.

  • All Platforms: Fixed a problem that blocked FTP-SFTP conversion connections with Tectia SOCKS Proxy. Previously, if an FTP-SFTP conversion connection got stuck at a certain stage while establishing the session, all consecutive FTP-SFTP conversion connections were blocked.

  • All Platforms: Fixed a problem that caused Tectia Client applications (e.g. sshg3/sftpg3/scpg3) to fail intermittently when ssh-broker-g3 was used in the run-on-demand mode.

  • All Platforms: Fixed a problem in agent forwarding with certificates. When multiple sessions were open to a remote server and in those sessions connections to other remote server(s) were initiated, agent forwarding would forward certificates only for one of the connections.

  • z/OS: Fixed a failure that occurred if the file transfer resume used by Tectia Clients was attempted when getting an MVS data set. Note that the value of STAGING now needs to be set to YES for the checksum/checkpoint file transfer resume to work.

  • z/OS: Tectia clients and server will now create a correct output file when transferring text data from a MVS dataset to a POSIX file with \r\n line delimiters. Previously (since 6.3.6 release) several hundred bytes of data could be missing in the output file if the file was larger than about 32000 bytes. This type of transfer is specified by using a MVS dataset name and the attributes TRANSFER_FILE_LINE_DELIMITER=MVS and TRANSFER_LINE_DELIMITER=DOS for the source file.

  • z/OS: Dynamic allocation is not failing anymore for existing cataloged dataset, when residing in another volume than specified (site VOLUMES=).

For further information about the products and changes between the different versions, and instructions on how to update the product, see the customer documentation and release notes at SSH product documentation web page.

link

answered Oct 08 '13 at 15:10

SSH%20KB's gravatar image

SSH KB ♦
509249246237

Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or __italic__
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Tags:

×69
×60
×49
×34
×31

Asked: Oct 08 '13 at 15:07

Seen: 11,210 times

Last updated: Oct 08 '13 at 15:10

All user contributed content licensed under the cc-by-sa license.
Powered by OSQA.