HISTORY.TXT 7.6 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181
  1. SecureCRT(R) 5.5 (Official) -- April 5, 2007
  2. Copyright (C) 1995-2007 VanDyke Software, Inc.
  3. All rights reserved.
  4. This file contains a SecureCRT product history. It includes lists
  5. of new features, changes, and bug fixes sorted by release. For a
  6. product description, installation notes, registration information,
  7. and contact information, please refer to Readme.txt (downloaded
  8. with this installation).
  9. Changes in SecureCRT 5.5 (Official) -- April 5, 2007
  10. ----------------------------------------------------
  11. Changes:
  12. - SSH2: The SSH_IGNORE message is only shown in trace output when
  13. the session's trace level is set to a value greater than one.
  14. Changes in SecureCRT 5.5 (Beta 4) -- March 27, 2007
  15. ---------------------------------------------------
  16. Bug fixes:
  17. - VT100 line-drawing characters were not displayed correctly under
  18. Windows Vista or when the East Asian language pack was installed.
  19. - The word delimiter characters session setting did not work
  20. correctly for tabbed sessions.
  21. - If the log file name or custom log data substitution %h (2-digit
  22. hour) was used between 03/11/07 and 03/31/07 or 10/28/07 and
  23. 11/03/07, the hours could have been off by an hour.
  24. - SSH2: SecureCRT crashed when attempting to convert a file that was
  25. not a private key to OpenSSH format.
  26. Changes in SecureCRT 5.5 (Beta 3) -- March 15, 2007
  27. ---------------------------------------------------
  28. New features:
  29. - SSH1/SSH2: Added support for optionally making SecureCRT the
  30. default URL handler for SSH1 and SSH2.
  31. - SSH2: Added support for exporting public keys from X.509
  32. certificates.
  33. Changes:
  34. - SSH1/SSH2: Added a command-line option (/Z 0) which turns off
  35. compression.
  36. - SSH2: In order to be compliant with the IETF draft
  37. draft-saarenmaa-ssh-x509-00.txt, the SHA1 hash algorithm is used
  38. by default with X.509 RSA host keys and public keys.
  39. - SSH2: Additional certificate information is shown in the trace
  40. output and the certificate error dialog when attempting to use
  41. an X.509 certificate for authentication.
  42. Bug fixes:
  43. - The escape sequence to turn off line wrap mode was honored even
  44. though the option "Enable line wrap mode switching" was off.
  45. Changes in SecureCRT 5.5 (Beta 2) -- February 27, 2007
  46. ------------------------------------------------------
  47. Changes:
  48. - The default font has been changed to "Lucida Console" due to a
  49. Windows Vista compatibility issue. This change only affects new
  50. installations of SecureCRT.
  51. - It is now possible to change the passphrase for an OpenSSH style
  52. private key.
  53. - When the Disconnect custom string is logged, an end of line is
  54. appended.
  55. Bug fixes:
  56. - If the "Open in a tab" option was off in the Connect dialog and
  57. multiple sessions were selected after choosing the "Connect in
  58. Tabs" menu item, the sessions were not opened in tabs.
  59. - If the specified log file was a valid path, but did not have a
  60. filename and the "Prompt for filename" option was not set, when
  61. logging started, an error that the specified file could not be
  62. created was reported.
  63. - After choosing to integrate SecureCRT and SecureFX, if privileges
  64. were not sufficient to write to the registry, it was possible to
  65. repeatedly be prompted to integrate.
  66. - SSH1: If an SSH1 session was disconnected while a terminal window
  67. size change was in progress, SecureCRT could crash.
  68. - SSH2: Attempting to generate a DSA key that was not a multiple of
  69. 64 resulted in an Unknown Application Error.
  70. - SFTP: Under certain circumstances, ASCII files being transferred
  71. in an SFTP tab were corrupted.
  72. Changes in SecureCRT 5.5 (Beta 1) -- February 8, 2007
  73. -----------------------------------------------------
  74. New features:
  75. - Windows Vista support.
  76. - Added a script recorder, which generates VB scripts. When
  77. "Start Recording Script" is selected from the Script menu, all
  78. keystrokes in the current session are recorded until "Stop
  79. Recording Script" is selected.
  80. - A set of sessions can be launched automatically on startup by
  81. specifying folders or multiple sessions as auto sessions.
  82. - Added the ability to insert custom data to log files. Custom
  83. data can be inserted when a session connects, disconnects, or
  84. on each line. Substitution parameters for session, date, and
  85. time information are supported. Additionally, there is an
  86. option to log only custom data.
  87. - When ANSI color is being used, it is now possible to use a color
  88. scheme, which allows the background to be something other than
  89. black and the foreground to be something other than white.
  90. - Added script function GetScriptTab, which returns the tab from
  91. which the script was started.
  92. - Added new custom menu item MENU_TAB_LIST1, which causes all the
  93. tabbed sessions to be displayed in the menu.
  94. - SFTP: Added "ascii" and "binary" command options to the SFTP tab.
  95. - SSH2: Added support for generating OpenSSH format keys and for
  96. converting VanDyke format private keys to OpenSSH format.
  97. - SSH2: Added a global option to cache passwords for SSH2
  98. sessions.
  99. - SSH2: Added support for zlib@openssh.com compression. With this
  100. compression method, compression does not start until after
  101. authentication, which prevents unencrypted passwords from being
  102. cached by the zlib library.
  103. Changes:
  104. - By default, Internet Explorer 7 disables Telnet through a
  105. registry setting. Added support for overriding this setting
  106. so that SecureCRT can be set as the default Telnet application.
  107. Administrator privileges are required in order to override the
  108. setting. Versions of Internet Explorer prior to 7 are not
  109. affected by this change.
  110. - When multiple sessions are opened from the "Connect" dialog, if
  111. the "Open in a tab" setting is off, the sessions are opened in
  112. tabs in a new window.
  113. - The chat window can now be toggled when SecureCRT is maximized
  114. or full screen.
  115. - When creating a session, if the Terminal, VT100, or VT102 font
  116. is selected, the "Use Unicode line-drawing characters" will be
  117. unchecked.
  118. - The "Save connected folder state" option was moved from the
  119. "Connect" dialog to the "General" page in the "Global Options"
  120. dialog.
  121. - Files with .VBE extension are included in the Script Files
  122. filter in the "Select Script to Run" dialog.
  123. Bug fixes:
  124. - Under certain circumstances, text was highlighted incorrectly
  125. after highlighted text had been pasted into a session.
  126. - Under certain circumstances, when SecureCRT got an error and
  127. became unresponsive, the Migration wizard ran.
  128. - It was not possible to cancel out of the "Global Options" dialog
  129. if an incorrect status indicator width or minimum tab width was
  130. entered.
  131. - When using send string functionality with a mapped key, \p
  132. (pause) did not work correctly.
  133. - If the specified log file was a valid path, but did not have a
  134. filename and the "Prompt for filename" option was not set, when
  135. logging started, an error that the specified file could not be
  136. created was reported.
  137. - If a script that connected to a session was run in a tabbed
  138. session that had been disconnected, the script hung.
  139. - The script function ConnectInTab used the default session font
  140. instead of the specified session's font.
  141. - The /SCRIPT command-line argument was not honored when /T was
  142. used and the session was opened in a tab other than the first
  143. tab.
  144. - SSH1: The command-line option /I pubkeyfile command-line option
  145. did not work with /SSH1.
  146. - SSH2: Under certain circumstances, using a SOCKS proxy caused
  147. the Secure Shell transport to hang.