Token2Shell v5.2.0 for Windows 2000/XP/Vista released.


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

    Cryptographic Engine Option

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


  • Token2Shell now natively supports widely used proxy servers such as HTTP and SOCKS. Proxy Server Option
  • You can now assign a macro file to an address book entry.
    Startup Macro File Option

    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.