VanDyke Software heeft donderdag versie 6.2.2 van SecureCRT uitgebracht. SecureCRT is, simpel gezegd, een zeer uitgebreide versie van Putty; een client voor remote control, file-transfer en data-tunneling met behulp van ssh. Dit is een methode om een beveiligde verbinding tussen twee computers op te zetten, waarbij zowel de data als een deel van het ip-verkeer wordt versleuteld. Nieuw in versie 6.2 is onder andere de mogelijkheid om de instellingen van meerdere sessies tegelijkertijd aan te passen. Verder zijn de loggingfuncties uitgebreid en kan er voor de authenticatie nu van een public key of een smartcard gebruik gemaakt worden. Sinds versie 6.2 zijn er twee opvolgers geweest, die voornamelijk bugfixes bevatten. Welke dat zijn kan hieronder worden gevonden:
Changes in SecureCRT 6.2.2:
Changes:Bug fixes:
- Added support for administratively prohibiting checking for updates from within SecureCRT.
- SecureCRT could crash if a session showing elapsed time was connected and the Windows system date or time was set to a value in the past.
- If a session that required a password was cloned, the password had to be entered again.
- When the session option "Use Windows copy and paste hotkeys" was set, the hotkeys for Find and Select All did not work.
- If the path in the "Select File to Send as ASCII" dialog was changed, it was not remembered the next time that dialog was displayed. It is now remembered until SecureCRT exits.
- The installer did not honor LICENSE_FILE or CONFIG_FOLDER_PATH entries that were specified in an ANSWERFILE.
- Silent installs did not add the program to the Start menu or the list of installed programs in the Windows Control Panel.
- Telnet: If a logon script that did not send an initial carriage return was specified for a session, a carriage return (OxOD) was sent in a separate packet during authentication, which caused authentication to fail if the server used line mode.
- SSH2: Previously, the default GEX preferred key size was changed from 2046 to 2048. However, the GSSAPI GEX maximum key size was still 2046, which caused the server to report an error and disconnect the session when GSSAPI GEX was used.
Changes in SecureCRT 6.2.1:
Bug fixes:
- SecureCRT could not be installed on systems where InstallShield custom actions do not work.
- If a license with a maintenance date in the format MM-DD-YY was entered, SecureCRT crashed.
- Under Vista, the mouse wheel did not scroll if the system used the MS Explorer Mouse driver.
- Function and arrow keys did not work correctly with servers that expect all the characters in escape sequences to be sent in the same packet.
- In a session with the "Retain size and font" option set, if the window was resized so that it was smaller than the logical rows and columns, the wrong text was highlighted during a find operation.
- If a session was opened in a new window and the window was closed prior to authentication completing, authentication prompts continued to be displayed.
- In the Keymap Editor, if a key was selected and a keymap that mapped that key was loaded, the keymap assignment display was not updated.
- In the Connect dialog, a session that was copied could not be pasted more than two times.
- If the Visual Studio 2008 DLLs were not in the side-by-side cache, MFC90.DLL errors were written to the event viewer when SecureCRT ran.
- SSH1/SSH2: If an RSA key with a passphrase was added in the Manage Agent Keys dialog and the wrong passphrase was entered, the incorrect error "The key packet is corrupt, damaged, or incompatibly formatted" was reported and was still reported after the correct passphrase was entered.
:strip_exif()/i/1395652959.png?f=thumbmedium)
:strip_icc():strip_exif()/u/289675/crop6401bf2c85501_cropped.jpg?f=community){kind=small}
:strip_icc():strip_exif()/u/114881/LinuxvsFreebsd2613.jpg?f=community){kind=small}
