|
osdir.com mailing list archive |
|
Subject: Starting OpenSSH client on a windows machine from a batch file - msg#00027List: network.openssh.generalFirst time poster; please forgive me any protocol transgressions. I am using openssh to secure a Synergy (mouse and keyboard sharing) connection between two machines on the same desk. I can start ssh fine if I enter the following command into a cmd promt or even straight from the 'Run..' dialogue: ssh -f -N -L 24800: <ssh server>:24800 <ssh server> With this port re-direction in place I then point the Synergy client at localhost and a secure connection is made and everything works fine. To make the process easier for my users - for some of whom starting the command promt is a bit too technical - I would like to either have the secure connection run at startup or have a batch file for the user to click on but I cannot get the ssh command above to run like this. >From a batch file it repeatedly runs the command, never connecting, until it >runs out of memory space. Many thanks, in advance, for your time. Stu Thread at a glance:
Previous Message by Date: click to view message previewInteroperability with OpenSSH3.4p1 and OpenSSH4.3p2Hi, I am working on an SSH implementation that has to connect to a SSH server. I find that the length of the DH modulus contained in SSH2_MSG_KEX_DH_GEX_GROUP (as defined by RFC 4419) message sent by the server for a 2048-bit DH key scenario is 399 bytes as opposed to 256 bytes. This is causing trouble with the client as the length is uncharacteristic of the known DH group 14 . However for a scenario of a 1024-bit key, as expected a 128 byte modulus is sent by the server in the SSH2_MSG_KEX_DH_GEX_GROUP message. Could some one explain this deviation from standard? Am i missing the math involved in the size of the modulus that is sent across? Please clarify, Regards, Naveen __________________________________________________________ Yahoo! India Answers: Share what you know. Learn something new http://in.answers.yahoo.com/ Next Message by Date: click to view message previewIncreasing the line buffer/memory size of SSH?Is there any way to increase the number of lines that SSH stores in its buffer? Right now the limit on my SSH (3.1.0) seems to vary between displaying the last 430-480 lines. -- View this message in context: http://www.nabble.com/Increasing-the-line-buffer-memory-size-of-SSH--tf3237539.html#a8998363 Sent from the SSH (Secure Shell) mailing list archive at Nabble.com. Previous Message by Thread: click to view message previewInteroperability with OpenSSH3.4p1 and OpenSSH4.3p2Hi, I am working on an SSH implementation that has to connect to a SSH server. I find that the length of the DH modulus contained in SSH2_MSG_KEX_DH_GEX_GROUP (as defined by RFC 4419) message sent by the server for a 2048-bit DH key scenario is 399 bytes as opposed to 256 bytes. This is causing trouble with the client as the length is uncharacteristic of the known DH group 14 . However for a scenario of a 1024-bit key, as expected a 128 byte modulus is sent by the server in the SSH2_MSG_KEX_DH_GEX_GROUP message. Could some one explain this deviation from standard? Am i missing the math involved in the size of the modulus that is sent across? Please clarify, Regards, Naveen __________________________________________________________ Yahoo! India Answers: Share what you know. Learn something new http://in.answers.yahoo.com/ Next Message by Thread: click to view message previewIncreasing the line buffer/memory size of SSH?Is there any way to increase the number of lines that SSH stores in its buffer? Right now the limit on my SSH (3.1.0) seems to vary between displaying the last 430-480 lines. -- View this message in context: http://www.nabble.com/Increasing-the-line-buffer-memory-size-of-SSH--tf3237539.html#a8998363 Sent from the SSH (Secure Shell) mailing list archive at Nabble.com. Loading Comments...
|
|
