• 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.viaarena.com/default.aspx?PageID=22&DSCat=161&DCatType=1

  » 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.

• 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/Mobile now natively supports widely used proxy servers such as HTTP and SOCKS.

• 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.

  We are not currently aware of any Windows Mobile device that has cryptographic hardware. But, the future devices with such hardware should be able to give you improved file transfer speed and longer battery life when paired with Token2Shell/Mobile.

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

• 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.

• 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/Mobile 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.

• 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.

This version fixes the license activation problem for certain users. If you are using version 5.0.1 and already have successfully applied your license key to Token2Shell, you do not really need to update your current version.

Token2Shell and Token2Shell/Mobile v5.0.1 are now available for download. These new versions feature minor bug fixes and enhancements.

In Token2Shell/Mobile, you can now switch between the key-sets of Keybar with stylus. Moving stylus upward from the inside of Keybar to the main screen changes the current key-set. In order to close Keybar without sending a key, do the same movement for the 'pin' button area, i.e., far right end of the Keybar.

You can now place your order online for Token2Shell and Token2Shell/Mobile. For previous version owners, additional information about upgrading is available at the following page:

• Upgrade Information

Please use the following download links to tryout the new versions. We'll be updating our sites throughout the next few weeks to add more information (pricing, ordering/upgrading and etc.) about the new official releases.

• Token2Shell v5.0.0
  for Windows 2000/XP/Vista
  (Single Lic.: $54.00 (USD), Bundle Package with Token2Shell/Mobile: $89.00 (USD))
  Go to Token2Shell download page.

• Token2Shell/Mobile v5.0.0
  for Windows Mobile Professional/Classic/Standard
  (Single Lic.: $49.95 (USD), Bundle Package with Token2Shell: $89.00 (USD))
  Go to Token2Shell/Mobile download page.

The following lists some of the noticeable changes made in the official releases since the last release candidate version 1:

• Session screens are no longer blocked by the file transfer status window. The file transfer status is now displayed on a separate free-floating pane. The status pane can also be docked with other panes or to the main window.
• "Login Agent" is added. When "Login Agent" is enabled, Token2Shell caches passwords and decrypted private keys for SSH sessions. Hence, you do not need to enter your password repeatedly to log into the same server. For cached private keys, you can also enable "Agent Forwarding" option. This "Agent Forwarding" feature is compatible with the "public-key" user authentication method of OpenSSH servers.

• Main screen now properly resizes based on the state of on-screen-keyboard.
• Scrollbars are completely removed from the virtual screen mode. On touch-screen devices, you can now access off-screen area or previous text buffer by drag-and-scroll with stylus or finger.
• "Login Agent" is added. When this feature is enabled, it works just like the feature of "Login Agent" on Token2Shell for Windows 2000/XP/Vista.

You can now download and test the release candidate versions of Token2Shell and Token2Shell/Mobile from MoDaCo, one of the best Windows Mobile community sites:

• MoDaCo (http://www.modaco.com/)
  

  Link to the post at MoDaCo regarding Token2Shell/Mobile:
  http://www.modaco.com/content/windows-mobile...
  (Requires MoDaCo account to download the files.)

Click here to read our original post about the RC versions.