Token2Shell/MD version 10.1.0 now available on Windows Store

  • Private keys in PuTTY file format can now be imported directly; you just need to select ‘.ppk‘ files.

    If the private key file is encrypted, you need to enter its passphrase. It’ll then be converted and re-encrypted using the same passphrase in OpenSSH format that Token2Shell/MD uses.

  • While importing OpenSSH private keys, public key files are now automatically created if you don’t provide them.

    Token2Shell/MD natively uses OpenSSH private key file format. Thus if you select private and public key file pairs in OpenSSH format, they are simply copied and used as they are. However, if you only have a private key file in OpenSSH format, you can now just select that file while importing; Token2Shell/MD automatically creates its corresponding public key (if the file is encrypted, you need to enter its passphrase as its corresponding pubic key is derived from the original private key values).

    Please note that OpenSSH public key files are only recognized when they are named as their corresponding private key file name plus ‘.pub‘. For example, if your private key file is named ‘my.key‘, its public key file must be named ‘my.key.pub‘.

  • AltGr modifier key in some keyboard layouts (ex. Icelandic keyboard) is now properly handled.
  • Font size change is now correctly applied when a new terminal session is started.
  • Fixed connection problems with Dropbear (https://matt.ucc.asn.au/dropbear/dropbear.html) SSH server and its related software (ex. OpenWRT (https://openwrt.org)).
  • Fixed title bar menu handling in Tablet mode.