Cookies op Tweakers

Tweakers maakt gebruik van cookies, onder andere om de website te analyseren, het gebruiksgemak te vergroten en advertenties te tonen. Door gebruik te maken van deze website, of door op 'Ga verder' te klikken, geef je toestemming voor het gebruik van cookies. Je kunt ook een cookievrije versie van de website bezoeken met minder functionaliteit. Wil je meer informatie over cookies en hoe ze worden gebruikt, bekijk dan ons cookiebeleid.

Meer informatie

Door , , reacties: 9, views: 3.564 •
Bron: VanDyke Software, submitter: DDX

SecureCRT logo (75 pix) VanDyke Software heeft na vijf bètareleases nu de final van versie 7.1 van SecureCRT uitgebracht. SecureCRT is, simpel gezegd, een uitgebreide versie van Putty. Iets minder simpel gesteld is het een client voor remote control, file transfers en datatunneling met behulp van ssh. Ssh 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. SecureCRT is beschikbaar voor Windows, Linux en OS X en een licentie kost honderd dollar. Hieronder is te vinden wat er allemaal is veranderd sinds versie 7.0.3.

Changes in SecureCRT 7.1

Bug fixes:
  • If a connected session was cloned and the terminal protocol of the cloned session was changed and then the original session was cloned again, SecureCRT crashed.

Changes in SecureCRT 7.1 (Beta 5)

Changes:
  • Mac: The permissions on the installer have been modified so that users other than the one who installed the application can run it.
  • Mac: Improved the look of the button bar on the Retina display.
Bug fixes:
  • SSH2: If an SFTP connection failed due to an "open channel" error, the SFTP tab incorrectly showed the connection status as connected.
  • Windows: If a tabbed session was renamed so that it contained an ampersand, two ampersands were displayed in the tab, and the session name in the Activator did not contain any ampersands.
  • Mac: If an application had been installed and then uncleanly uninstalled, SecureCRT crashed on startup.
  • Mac/Linux: If the session option "Synchronize view to size" was set and the SecureCRT window was maximized and the font was small enough so that more than the maximum number of columns could fit in the terminal window, SecureCRT crashed.

Changes in SecureCRT 7.1 (Beta 4)

Changes:
  • Added support for the Cursor Horizontal Absolute (CHA) escape code to the VT100 and ANSI emulations.
  • Mac: Improved the look of the toolbar icons on the Retina display.
Bug fixes:
  • SecureCRT could crash if CTRL+TAB was used to cycle through the tabbed sessions and then the sessions were closed using CTRL+F4 without ever releasing the CTRL key.
  • If the global option "CTRL+TAB switches to most recently used tabbed or tiled session" was set, the application window title did not get updated when a session tab was closed and a different session become the active tab.
  • Windows: SecureCRT crashed after "+++" was typed into a TAPI session.

Changes in SecureCRT 7.1 (Beta 3)

Bug fixes:
  • When a dependent firewall session's option "Display logon prompts in terminal window" was set, the parent session's username was used instead when the dependent firewall session connected.
  • When a dependent firewall session connected, the dependent session's specified authentication method was not used.
  • Windows: If a session was logging to a file and then logging was stopped, the log file's parent folder could not be renamed or deleted.
  • Windows: If the administrative option to disallow saving passwords was set and a password was specified on the command line, it was not used.
  • Mac: The connection status icon and session name overlapped in the session tab when there was not enough room to display both.

Changes in SecureCRT 7.1 (Beta 2)

Changes:
  • When the "Scroll to bottom on output" session option is off, the session never scrolls to the bottom. Previously, if less than a screen was scrolled back, the session always scrolled to the bottom on new output.
  • Added support for extended packets in Kermit, which allows ASCII files to be transferred and improves transfer performance.
  • Line drawing for Korean language fonts was improved.
  • A session using VT220 emulation ignores DEL characters received from the remote system.
  • If the global option "CTRL+TAB switches to most recently used tab" is set, when a tabbed session is closed, focus goes to the previously active tab instead of the most recently opened tab.
Bug fixes:
  • Scripts that attempted to connect an ad hoc session using a protocol flag such as "/SSH2" reported the following error: The default session is not valid with the "/S" command-line flag.
  • If the font of a connected session was changed, the session's rows and columns were not adjusted.
  • When the SecureCRT window regained focus, an extra mouse click was required before being able to select text.
  • The authentication prompt was displayed every time a host disconnected and reconnected, which resulted in multiple authentication prompts being displayed when authentication timed out.
  • When SecureCRT was integrated with SecureFX, if a dependent session firewall was specified and then the session protocol was changed, the firewall field did not get updated on the protocol page.
  • Mac: After several days of constant use, especially with a lot of switching into and out of full screen mode, the toolbar could disappear.
  • Mac: The Connect bar disappeared after going into and out of full screen mode.
  • Mac: The minimum tab width global option was not honored.
  • Linux: Loading an incompatible plugin could cause SecureCRT to crash.

Changes in SecureCRT 7.1 (Beta 1)

New features:
  • On Mac and Linux, added the ability to tile sessions within the SecureCRT application window. Sessions can be tiled or cascaded. Scripts can use the "Tab" object to work with tiled sessions.
  • Added support for dependent sessions so that a connection can be made to a jump host or SSH gateway before the session is connected.
  • Added support for the Kermit file transfer protocol. Binary and ASCII transfers are supported.
  • SSH2 on Windows: Added support for SHA1 in RSA signatures, which allows X.509 certificates to be used in FIPS mode and other settings where MD5 cannot be used.
  • A button action can be sent to all connected tabbed or tiled sessions by pressing SHIFT+ on the button.
  • Added a character send delay option to wait for a text prompt.
  • Added a new logging substitution variable "%P", which inserts the session's port.
  • Added the ability to copy ANSI text to the clipboard, which allows attributes such as color and font to be preserved on the clipboard.
  • Added support for sending Xterminal escape sequences for CTRL+ keys.
  • Added the ability to specify ANSI colors for individual sessions in addition to the global option.
  • Windows: Added support for the Wyse label line.
  • Linux: Added support for printing.
Changes:
  • Improved scrolling performance when the session options "Jump scroll" and "Minimize drawing" are set.
  • Changed the protocol NO-OP to send decimal code 241 instead of 0.
  • When the escape sequence "CSI ?3l" is received, the data is added to the scrollback buffer before the screen is cleared.
  • Mac: The default font is now 11-point Menlo. This change only affects new installations.
Bug fixes:
  • SecureCRT could crash when attempting to clone a session connected to a device that does not support multiple connections if prompts for both sessions were displayed at the same time.
  • If a tab was manually closed and then was closed by a script, SecureCRT crashed.
  • SecureCRT could crash if it was tunneling through a SOCKS proxy on a laptop and the laptop was closed.
  • The password prompt was displayed every time a host disconnected, due to the session timing out, and reconnected automatically.
  • The cursor went below the session window if the chat window was displayed and the number of session rows was larger than the session window height.
  • If a machine had two monitors and the main SecureCRT window was dragged to the second monitor and maximized, when a session with the inital position located on the first monitor was opened and switched to fullscreen mode, the main window got moved to the first monitor.
  • In the "Connect" dialog, if a new folder was given the same name as an existing folder except for different capitalization, after exiting and restarting SecureCRT, both folders were gone.
  • If a key was mapped to VT_KEYPAD_ENTER, the key did not work when the terminal was in newline substitution mode.
  • SSH2: The global option "Cache session password" was not honored for keyboard interactive authentication.
  • SSH2: If a session was configured to use password and X.509 public-key authentication, if the key was signed, but failed, the same key was sent again instead of sending the next key.
  • Windows: If a terminal session channel could not be opened because of a resource shortage, an error was displayed and the terminal area was not displayed correctly.
  • Windows: The application icon was not removed from the Program group during an uninstall.
  • Windows: If "Connect" was selected from the Activator and "Quick Connect" was selected from the "Connect" dialog, the connection was not made.
  • Mac, Linux: Copying text from an RDP session caused SecureCRT to hang.
  • Mac: SHIFT and CONTROL keys did not work with the Chinese input methods sougou and QIM.
  • Mac: When Romaji was the selected language Input Source, the CONTROL key behaved like the COMMAND key.
  • Mac: When "Make Alias" was used to create a desktop shortcut, if the shortcut name contained a ".", the shortcut did not work.
  • Mac: When a Telnet connection failed, a "Broken pipe" error was displayed.

SecureCRT in Ubuntu screenshot (620 pix)

Versienummer:7.1
Releasestatus:Final
Besturingssystemen:OS X, Linux, Windows 8, Windows Server 2012, Windows Server 2008, Windows Vista, Windows Server 2003, Windows XP, Windows 7
Website:VanDyke Software
Download:http://www.vandyke.com/download/securecrt/download.html
Licentietype:Shareware

Reacties (9)

dus putty maar dan voor 100 dollar.... nou keuze is voor mij wel duidelijk. :Y)

persoonlijk denk ik dat als je toch een ssh verbinding wil maken je dit beter zou kunnen doen van uit een linux client. dan werk je tenminste in een (naar mijn inzicht) zeer degelijk terminal venster. vind het venster van putty in 1 woord: prut.

[Reactie gewijzigd door coolkil op 3 mei 2013 11:21]

Dus... Je vindt SecureCRT niets omdat het 100 dollar kost terwijl putty gratis is... En vervolgens zeg je dat je putty prut vindt.

Is het idee wel eens bij je opgekomen dat SecureCRT wel iets meer features biedt dan putty? Je zegt hetzelfde als "Word is een dure versie van notepad, en notepad is prut".

Ben met je eens dat ik ook liever gewoon een linux- of osx-terminal heb, dat is voor mij voldoende... Vind het ook onbegrijpelijk dat Windows standaard geen ssh client heeft. Maar SecureCRT is wel ont-zet-tend uitgebreid, en als je het dagelijks nodig hebt, z'n geld zeker wel waard.
Ik gebruikte voorheen ook Putty. Alleen toen moest ik steeds meer en meer in SSH doen, dan komt het toch een beetje tekort. Dus overgestapt op Xshell, is ook gratis voor thuisgebruik.

Grote voordeel voor mij is tabbed sessions.

http://www.netsarang.com/products/xsh_overview.html
Een alternatief voor SecureCRT, als je toch geld aan het uitgeven bent, is ZOC. Ik gebruik het nu enkele jaren en ben zeer tevreden over de mogelijkheden.
mRemoteNG of Putty Connection Manager (beide in combinatie) met Putty, zijn gratis en hebben ook tabbed sessies. Beide bevallen prima.
Mijn alternativen om vanaf msWindows ssh te gebruiken:
SSH Secure Shell (TM), versie 3.2.9 doet het al 10 jaar perfect (zie www.ssh.com) Inclusief file-transfer en heel eenvoudig extra terminals naar de overkant opzetten.
Putty gebruik ik niet rechtstreeks maar vanuit/via VisionAPP. Eigelijk vooral omdat VisionApp als basis voor rdp en vnc sessies gebruikt wordt.

En baas boven baas: command line ssh in een cygwin omgeving. Dat werkt onder msWindows gewoon het zelfde als onder unix varianten.
In PuTTY kan je niet rechtstreeks een IPv6 IP-adres opgeven (dit geeft namelijk een foutmelding), wel een hostname dat naar zo een IPv6 adres wijst. Kan dat met dit programma wel? Zou namelijk handig zijn voor IPv6 adressen zonder hostname, en voor link-local adressen.
Vergeet niet dat SecureCRT een ontzettend uitgebreide scripting taal in zich heeft waarmee je heel veel geautomatiseerde acties kunt laten uitvoeren. Dat ben ik nog niet in andere programma's tegengekomen.

Op dit item kan niet meer gereageerd worden.



Populair:Apple iPhone 6Samsung Galaxy Note 4Assassin's Creed UnityFIFA 15Motorola Nexus 6Call of Duty: Advanced WarfareApple WatchWorld of Warcraft: Warlords of Draenor, PC (Windows)Microsoft Xbox One 500GBDesktops

© 1998 - 2014 Tweakers.net B.V. Tweakers is onderdeel van De Persgroep en partner van Computable, Autotrack en Carsom.nl Hosting door True

Beste nieuwssite en prijsvergelijker van het jaar 2013