For more information about Line Sender, please visit:
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.
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
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:
AES counter(CTR) mode with 128, 192 and 256 bit key is now supported.
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:
|Token2Shell now natively supports widely used proxy servers such as HTTP and SOCKS.|
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.
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.
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.
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.
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.
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:
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.
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.
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
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:
Link to the post at MoDaCo regarding Token2Shell/Mobile:
(Requires MoDaCo account to download the files.)
Click here to read our original post about the RC versions.
The following entries have been added to online handbooks,
"Token2Shell & Token2Shell/Mobile":