Token2Shell/Mobile

Token2Shell/Mobile v5.3.1 for Windows Mobile released.

  • Memory access violation error with dynamic port forwarding (SOCKS 4/5) in Token2Shell.SSHpf/Mobile has been fixed.
  • Improved terminal control code handling.

Token2Shell/Mobile v5.3.0 for Windows Mobile released.

  • A new type of Keybar is added for touch-screen based Windows Mobile devices. The new Keybar has the same set of buttons as the original, but it has larger button area and doesn't block keyboard inputs while it's visible.

    For additional information about the new Keybar, please visit:
    http://choung.net/handbooks/Token2Shell/Mobile/keybar

  • Token2Shell/Mobile now properly handles SSH connection checking packets from OpenSSH servers with ClientAliveInterval option turned on.

Directory path synchronization in BASH shell

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:

Token2Shell/Mobile v5.2.1 for Windows Mobile released.

  • Token2Shell/Mobile "Internet Connection Manager" has been improved for automatically establishing cellular phone carrier's Internet data connection if Wi-Fi or other local network is unavailable.
  • Edit control on property scroll now maintains input state.
  • This version also includes other minor enhancements and bug fixes.

Token2Shell/Mobile v5.2.0 for Windows Mobile released.

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

Token2Shell/Mobile v5.1.0 for Windows Mobile released.

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

Setup migration tool v1.0 released.

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.

More information is available at:
http://choung.net/handbooks/setup-migration-tool

Token2Shell and Token2Shell/Mobile v5.0.1 released.

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.

Official versions of Token2Shell and Token2Shell/Mobile are now available for download.

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))

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

» Token2Shell for Windows 2000/XP/Vista
  • 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.
» Token2Shell/Mobile for Windows Mobile
  • 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.