• AES encrypted private key file format used for OpenSSH version 5.4 and higher is now supported.
• Random screen freezing problem on some Windows OS versions has been fixed.
• This version also includes other minor enhancements and bug fixes.

• File listing in SSH2 remote copy now shows symbolic link information.
• Unexpected timeouts during high-speed (40+ MB/s) SSH2 remote copy has been fixed.
• SSHpf now properly handles remote port forwarding.
• Improved SSHpf SOCKS proxy server mode (dynamic port forwarding). SSHpf now handles SOCKS requests much faster.
• Improved X11 forwarding.
• Clicking middle mouse button now copies current text selection to clipboard and then sends to server. If no text selection is made, Token2Shell sends the text currently available in clipboard.

• Restoring last window position and size now correctly works even if Token2Shell is closed while minimized.
• Improved terminal control code handling.

• Line Sender now supports using <F5> and <Shift>+<F5> keyboard shortcuts. <F5> sends currently highlighted line and <Shift>+<F5> sends all text. These shortcuts work even when the line sending mode is disabled.
• This version also addresses Token2Shell memory access violation error on some Windows 7 computers when Token2Shell is exited while an SSH session is still active.

• New features and enhancements are added to Line Sender.
   
  • Sending text only to sessions on main window or detached panes is now possible.
  • Text content can now be loaded from or saved to a file.
  • Edit control now supports line bookmarking and highlights the current line.
  • Line Sender now maintains input focus even after pressing <Ctrl> + <Tab> for session switching.
  

  For more information about Line Sender, please visit:
  http://choung.net/handbooks/Token2Shell/line-sender

• You can now keep connection alive with MSG_IGNORE for SSH sessions. (Token2Shell.SSHpf now also supports keeping connection alive with MSG_IGNORE.)
  

  When this option is selected, Token2Shell sends a data packet that will be ignored by the server. Hence it will not interfere with the application you are running from server, yet it will create enough data traffic for connection idle monitors; preventing them from closing the connection.

• SSH2 Remote Copy now supports choosing a destination folder via selection dialog for file uploading.
  

  TIP: With minimal changes to your server login script, you can let Token2Shell automatically keep track of your current server directory path for SSH2 Remote Copy. For additional information, please visit
  http://choung.net/handbooks/ssh2-remote-copy.

While in an SSH2 session, you can upload or download files simply by drag-and-dropping them to Token2Shell or selecting them from a list.

In order to let Token2Shell automatically obtain your current server directory path, you need to adjust your login script, and we now have added a BASH shell example:

• SSH2 Remote Copy
  http://choung.net/handbooks/ssh2-remote-copy

• Session tab has been re-designed to improve the visibility of currently selected session.
• You now have an option to display Address Book entry name as session tab title.
  
• Token2Shell now sends right-click and wheel-scroll events to server in XTerm mouse tracking mode. (You need to press <Shift> key if you wish to access Token2Shell right-click pop-up menu.)

• AES counter(CTR) mode with 128, 192 and 256 bit key is now supported.

• You can now use external cryptographic engines for RNG, AES and SHA1.

  SSH protocol uses encryptions to achieve security, and the encryptions require complex computations. If your computer has a 2GHz or faster processor, the built-in cryptographic engine in Token2Shell should be able to easily provide 10+ MB/s file transfer speed over 100 Mbps network. However, in gigabits network, complex cryptographic computations become a bottleneck for faster speed.

  If you have hardware or instruction-level cryptographic support from your CPU or installed an encryption add-on card, you can now significantly improve the performance of Token2Shell with this new option. (Please note that the encryptions also happen at the server, thus your server must also be able to handle the cryptographic load adequately.)

  

  Please note that in order for Token2Shell to use an external cryptographic engine, it must support API set by Microsoft for Cryptographic Service Providers.

  Related information about instruction-level cryptographic support from CPU:

  » VIA Processors

  • VIA PadLock Security Initiative
    http://www.via.com.tw/en/initiatives/padlock/index.jsp
  • VIA PadLock Cryptographic Service Provider
    http://www.via.com.tw/en/support/via-security-software.jsp

  » Intel/AMD Processors

  • CPUs with AES Instruction Set
    http://en.wikipedia.org/wiki/AES_instruction_set
  
  

• Token2Shell now natively supports widely used proxy servers such as HTTP and SOCKS.

• You can now assign a macro file to an address book entry.

  Assigned macro file will be executed after connected to the server. If you have setup Auto Login, it will be processed before executing the macro file.

• Token2Shell installer now properly handles version update for Windows Vista with UAC(User Account Control) enabled.

  If you have purchased and applied your license for Token2Shell, upgrading to a new version is as simple as running the new installer over the existing version. The installer will detect the currently installed version and only update the necessary components while preserving the existing settings including your license information.

• This version also includes minor bug fixes and enhancements.

• Login Agent now supports SSH keyboard-interactive user authentication method.

  If your server uses SSH keyboard-interactive user authentication method, the server may ask different login questions every time you request an access. In such case, the new caching mechanism used in Login Agent for "keyboard-interactive" is ineffective. However, if the required login questions are the same for each login, you need to answer them only once. All future questions are answered automatically by Login Agent.

• Token2Shell.SSHpf now supports dynamic port forwarding (SOCKS 4/5).

  You can now create an SSH tunnel and use it as a local SOCKS server that supports version 4 and 5. For example, if you created a dynamic port forwarding on port number 1080, you can set other applications such as Web browser or email client to use that tunnel by configuring them to use the SOCKS server at "localhost" or "127.0.0.1" on port number 1080.

  
  
  
• You can now set Line Sender to maintain separate content for each session.

  When you select the new option "Maintain separate content for each session" under [ Tools ] » [ Options ] » [ Text Windows ] » [ Line Sender ], Token2Shell will switch the content of the Line Sender according to the currently selected session.

  
  
  
• "Auto Send When Idle" feature now has a new option "Apply to all sessions". When this option is selected, "Auto Send When Idle" settings will be applied to all current and future sessions.
  
  
• This version also includes minor bug fixes and enhancements.

If you have been using one of our previous terminal emulation products (SecureToken, Token2 Plus, mToken, mToken Lite) and wish to transfer address book entries and configuration settings to Token2Shell or Token2Shell/Mobile, you can now use the setup migration tool.