Additional information about the new options for Line Sender is available at http://choung.net/handbooks/Token2Shell/line-sender-options.
The following lists the key features added to
Token2Shell version 6.1.0 for Windows 2000/XP/Vista/7.
Token2Shell already supports detaching a session tab from its main window. A detached session screen behaves like a floating dockable pane; it can be docked or grouped together with other detached sessions. Also, unlike traditional multi-session programs where each session window cannot be placed outside of the main window, the floating session panes in Token2Shell can be placed anywhere on your desktop screen.
In the new version, Token2Shell now also supports detaching 4 session tabs all at once and form a 2x2 docked floating pane. In order to use this new feature, simply press <Shift> key while double-clicking the session tab you wish to detach. Token2Shell will then automatically detach the next three session tabs and form a 2x2 floating pane. The new version also supports right-click popup menu for detaching session tabs.
When you do a Slow Paste (<Shift>+<Alt>+<Ins>) in Token2Shell, Token2Shell sends the clipboard-stored text line by line at a preconfigured interval. In the new version, Token2Shell supports additional options for setting that interval.
In the new version, you now have options for setting up pausing time or trigger text. Setting up those options is much like creating a macro script with a common '#wait' or '#waitfor' command line. For example, if you set the interval mode to 'Time' and enter '2000' for 'Line Sending Interval', Token2Shell sends each line and pause for 2 seconds before sending the next one. If you set the mode to 'Text' and enter 'myserver command prompt %' for 'Trigger Text', Token2Shell will only send the next line when it sees that text from the server response.
For additional information about '#wait' and '#waitfor' script commands, please visit
http://choung.net/handbooks/Token2Shell/command-macro.
The new version now supports creating RSA and DSA private keys suitable for SSH2 sessions within Login Agent. The file format used for those keys is compatible with OpenSSH. (Please note that if you update a private key in Login Agent, it will be overwritten in OpenSSH format regardless of its original file format.)
When you add a password or passphrase to a private key, Login Agent will save the key using AES encryption. OpenSSH version 5.4 and higher uses the same encryption, but if you are using an older version, it will not be able to decrypt the new format. Thus if you need to transfer your AES encrypted private key to an OpenSSH server older than version 5.4, you may need to remove the encryption before uploading, and have it encrypted again from the server.
Login Agent now also supports copying the public key of the private key it holds to clipboard. You can use the clipboard copied text to wherever the content of an OpenSSH public key file is expected.
To show our appreciation to our users, we are offering a free upgrade to all Token2Shell version 5 customers for the newly released version 6. At the same time, we'll be adding one more license free of charge to each upgrade. For example, if you had purchased 1 license of Token2Shell version 5, your new activation code will be setup for 2 licenses. (Please note that this upgrade offer is only for existing customers who already have a Token2Shell license key.)
You don't need to send us any application form for this upgrade. You already have all the necessary information to activate the new version. For detailed instruction, please visit http://choung.net/order/license-activation#t2s-v5-upgrade.
Thank you again for all your support of our software!
Long at last, it's here! The following summarizes the key features added to version 6 of Token2Shell for Windows 2000/XP/Vista/7.
Ch1.Gateway supports all the connection methods found in Token2Shell. So even the device that only supports serial port connection can be accessed over an SSH connection via Token2Shell and Ch1.Gateway!
The method for applying your license to Token2Shell has been changed. You now only need to enter "User ID" and "Activation Code". Your license key will then automatically be downloaded from our activation server.
For additional information about the new software activation process, please visit http://choung.net/order/license-activation.
For more information about Line Sender, please visit:
http://choung.net/handbooks/Token2Shell/line-sender
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
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:
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.
