Feedback

Please feel free to leave any comment

15 comments:

  1. Stephane LaurencelleJanuary 4, 2017 at 8:42 AM

    Hello,

    I have been using winsshterm since october 2016 before that i was using mobaxterm product but now that i discover this product i switch to it 100%.

    The feature i was using in mobaxterm have been integrate by Patrick after talking with him about those.
    features:
    multi exec
    multi paste
    more split Windows
    reconnect/disconnect option
    move tab to another Windows

    he implement them in a record time and they all work like a charm and he event make them more flexible then in mobaxterm product.

    Thanks a lot Patrick for all the good works and new features.

    Really appreciated it.

    Stephane

    ReplyDelete
    Replies
    1. Many thanks to you too, Stephane. You gave me new ideas and helped make WinSSHTerm better.

      Delete
  2. I have been trying WinSSHterm for awhile and it's a good product. I like to know if you can add few more updates such as:
    1) Add a function to kill all process (sessions) - When I have 4 or more sessions open and there is no easy way to get rid of all sessions.
    2) Add a simple Quick Connection Toolbar: Protocol, Host, Login, password, session (if needed by user)- Allows user to log into a server quickly
    3) Add a function to load scripts and able to send it to all sessions.
    4) Add the ability to Import/Export Sessions in the File Menu.

    ReplyDelete
  3. 4) Add the ability to Import/Export Sessions in the File Menu. - (You have created “connections.xml” file that stores all saved server connections but like to able to import/export the file inside the WinSSHTerm application)

    ReplyDelete
    Replies
    1. Thanks for your feedback. It would be great if you could use the contact form, so I can email you back and we can talk about your points.

      Delete
    2. Release 1.9.0 will have support for shared connections, which can be loaded by multiple users and also exported.

      Delete
  4. Thanks a lot for your great tool. Featurerequest for you: add please some stored password encryption, maybe with master-password like WinSCP do.

    ReplyDelete
    Replies
    1. Thanks, I'll think about your suggestion. For now, I recommend everyone who needs maximum security to use public key authentication in combination with Pageant. This way there is no need to store passwords.

      Delete
    2. From release 1.9.0 on all passwords will be AES encrypted.

      Delete
  5. The path to SSH keys + log file currently do not recognise Windows environment variables. e.g. %USERPROFILE%.

    If they did, then it would make sharing WinSSHTerm config with colleagues easier.

    https://technet.microsoft.com/en-us/library/cc749104(v=ws.10).aspx

    ReplyDelete
    Replies
    1. Thanks, the shared connections file will support a limited set of template variables. You can use these to set custom paths, passwords, SSH users,... for each user.

      Tip: If you put your SSH keys somewhere inside your WinSSHTerm folder, only the relative path will be stored.

      Delete
  6. Hello,

    When trying to use this to connect to a brocade switch, I get the following warning:
    "The first key-exchange algorithm supported by the server is diffie-hellman-group1-sha1, which is below the configured warning threshold. Do you want to continue with this connection?"

    When I click Yes, it connects, but seconds later, it disconnects with the following error:

    "Server sent disconnect message type 2 (protocol error): 'Service is not known'"

    I can connect fine using putty.exe alone, but not with WinSSHTerm.exe. I looked for the threshold setting but cannot find one. Any idea on how to get past this?

    ReplyDelete
    Replies
    1. Hello, could you try to connect to your switch using putty.exe, with X11 forwarding enabled (Connection->SSH->X11->Enable X11 forwarding) and see if you get the same error?

      Delete
    2. Hi, yes, i get the exact same error when i enabled it in putty as you asked. I then opened Putty again, loaded the WinSSHTerm saved session, unchecked that option, and saved it. That seems to have fixed the issue. Thanks for leading me to the light.

      Delete
    3. Thanks for your feedback. There will be an option to disable X11 forwarding in release 1.9.1.

      Delete