Replies: 11 comments 6 replies
-
|
WindTerm was designed to make it easier to use without having to memorize and type a lot of command-line arguments. Please read Port Forwarding (Tunnel) and Network Proxy / Jump Server, I think they might be what you want. If you have any further needs, don't hesitate to let me know. BTW: |
Beta Was this translation helpful? Give feedback.
-
|
No, the ssh tunnel and proxy parameters do not work because the proxycommand parameter allows calling a third party program to initiate the connection like wstunnel or proxytunnel with windows or netcat[nc] with linux/mac for example. Making an ssh tunnel using websockets is common to bypass a proxy that only lets https pass through port 443. Whether it's to ssh into remote servers, an ssh tunnel to make rdp or do reverse ssh, there are so many possibilities (...) I think leaving a field allowing to enter optional ssh arguments could allow [geeks like me] to have the best ssh options because there would be a lot of options to put in a UI. FYI, my putty sessions that use proxycmd parameter [alias proxycommand in ssh arguments] don't work with windterm. So I would be very interested in having a field to manually add options to the ssh command because your program is quite fantastic and highly configurable and that's fine |
Beta Was this translation helpful? Give feedback.
-
|
Yes, although the current design can meet the needs of most people, it cannot completely replace the functions of If I add a |
Beta Was this translation helpful? Give feedback.
-
|
The ssh api documentation on https://api.libssh.org/, indicates that the ssh_options_get() function https://api.libssh.org/stable/group__libssh__session.html allows to pass this type of parameters If we consider adding a field named something like "ssh command with user options : ", it would then be implicit that all the parameters present in this field would be transmitted to this function, with beforehand an evaluation of the variables %var% for windows $var for linux. There is some programming example on GitHub for this, unfortunately my level of programming will not be enough to help you anymore So, yes I think this should work as the ssh_options_get() function seems to be able to handle this need Hope that answered your question |
Beta Was this translation helpful? Give feedback.
-
|
Thank you, actually So if your OS is // libssh 0.9.6 src/socket.c:873
#ifndef _WIN32
/**
* @internal
* @brief executes a command and redirect input and outputs
* @param command command to execute
* @param in input file descriptor
* @param out output file descriptor
*/
void
ssh_execute_command(const char *command, socket_t in, socket_t out)
{
const char *args[] = {"/bin/sh", "-c", command, NULL};
/* Prepare /dev/null socket for the stderr redirection */
int devnull = open("/dev/null", O_WRONLY);
if (devnull == -1) {
SSH_LOG(SSH_LOG_WARNING, "Failed to open /dev/null");
exit(1);
}
/* redirect in and out to stdin, stdout */
dup2(in, 0);
dup2(out, 1);
/* Ignore anything on the stderr */
dup2(devnull, STDERR_FILENO);
close(in);
close(out);
execv(args[0], (char * const *)args);
exit(1);
}
...
#endif // _WIN32 |
Beta Was this translation helpful? Give feedback.
-
|
Generally I need this functionality WITH Windows ;-(( Previously I used the ssh port via cygwin which allowed me to do this, but since the availability of openssh 8.x on Windows (via the download on the microsoft site), I use this version. I think the sources for the cygwin (and openssh 8.x) ssh client library can be found at https://www.cygwin.com/cgi-bin2/package-grep.cgi?grep=openssh&arch=x86_64 For the moment I go through a cmd.exe command line to launch my openssh client from winterm ;-)) Indeed, one solution would be to pass the string to an executable hosted on the host system by performing I/O redirection if I understand your code correctly, although I'm not a programming expert |
Beta Was this translation helpful? Give feedback.
-
|
I have been reading the relevant code of putty's Both |
Beta Was this translation helpful? Give feedback.
-
|
Yes, I use this feature of putty and it works perfectly for my needs. Yes, I agree with you, it wouldn't be a good idea to weigh down/penalize winterm with cygwin. |
Beta Was this translation helpful? Give feedback.
-
|
Sorry for the late reply. I need to take care of some stuff recently. I have completed the |
Beta Was this translation helpful? Give feedback.
-
|
Sorry, I forgot to explain how to use it. After downloading, open the session's settings dialog and set |
Beta Was this translation helpful? Give feedback.
-
|
Hello, I will test this today. Can you tell me how windows variables should be %MyVar% or Ok, I tried without passing variables and Ok, if in proxycommand I call a program with a windows path like c:\Tools\Common\wstunnel.exe, I get "The session is disconnected" and the log is empty. If I put C:/Tools/Common/wstunnel.exe, I have "Unknown error" but I don't see any error in the log An idea ? |
Beta Was this translation helpful? Give feedback.
-
|
I just found the explanation ! If my command is "C:/Personnel/Tools/common/wstunnel.exe -vvv" (where -vvv is the verbosity level, it doesn't work). I think there is a problem with the output of the proxycommand command. It is played before the ssh session, is that why it is not visible in the log even in debug mode? If I remove -vvv it's work ! ;-)) Last note : I failed to get a windows variable evaluated in the proxycommand line by trying these combinations : %MyVar% (windows mode), In any case thank you for this version which improves this part |
Beta Was this translation helpful? Give feedback.
-
|
If you set the In Also I added a The development of |
Beta Was this translation helpful? Give feedback.
-
|
Sorry for my late reply too For wstunnel verbosity, look at what happens for terminal redirection as it happens BEFORE the ssh connection. I don't know how WINDTERM reacted in this specific case. Thanks for the implementation tips for the variables, I'll wait for the next pre-release to test this. Tunnel operation mode, not working properly
I hope that the libssh will allow the Windows version to evolve with the same functionalities that we have with the openssh version available in command line https://github.com/PowerShell/openssh-portable like I told you in our previous conversation |
Beta Was this translation helpful? Give feedback.
-
|
At present, the Thank you for pointing out the problem with |
Beta Was this translation helpful? Give feedback.
-
|
I have done and released the WindTerm_2.4.0_Prerelease_2 version. Now you can customize environment variables. Please try it out and see if it meets your needs. The two problems with |
Beta Was this translation helpful? Give feedback.
-
|
I just tested this new prerealse 2 version I tried declaring the windows variables in the box list and couldn't get them to work with the proxycommand line. wstunnel's -vv option always causes the same error For the tunnel functionality, when I try to activate the tunnel on an existing session (with proxycommand) I have the message "waiting to open" which never ends and it does not work. Personally, I think the idea that passing the additional parameters for the ssh command in a dedicated field would be easier for the user experience. Indeed, it is quite confusing to go to a menu to activate a tunnel option and, in my case, I would have to declare several tunnels to manage to do both a dynamic port and port forwarding for the same session. In any case, I now use WINDTERM every day in personal and professional environments. |
Beta Was this translation helpful? Give feedback.
-
I need to pass additional arguments to ssh like proxycommand.
Currently I have to go through a cmd or powershell command line to make ssh connections in certain situations: ssh tunnels with proxycommand allowing to bypass corporate or hotel proxy. In this case, I no longer have the possibility of using the sftp since the original shell is not ssh
Could you consider adding an additional field in the ssh template in order to add options / arguments to pass to the ssh command?
Some examples :
ssh options to bypass a corporate proxy with windows authentication :
ssh user@server -D 10998 -o proxycmd "wstunnel.exe -vvv -L stdio:%host:%port --httpProxy=%USERDOMAIN%\%USERNAME%:%PROXYPASS%@%prxy%:%prxyport% wss: //gateway.mydomain.fr"To make an ssh tunnel for an RDP session with port forwarding
ssh user@server -NL 2222:my-windows:3389 -o proxycmd "wstunnel.exe -vvv -L stdio:%host:%port --httpProxy=%USERDOMAIN%\%USERNAME%:%PROXYPASS%@%prxy% :%prxyport% wss://gateway.mydomain.frIf you could evaluate windows variables like %USERDOMAIN%%USERNAME%:%PROXYPASS%@%prxy% :%prxyport% that would be just wonderful! (For security reasons, I do not leave my username and password in configuration files)
Beta Was this translation helpful? Give feedback.
All reactions