In order to ssh into a SuSE 9.0 box from Windows using PuTTY, you have to select "Connection - SSH - Preferred SSH Protocol Version - 2" to ssh into the box. Is there anything on the SSH server that I can change so that I don't have to manually select the SSH version to use everytime? Thanks, Chris
You can save that setting for each entry in Putty. Just put in the hostname, choose port 22 then go down on you left and choose SSH and set it to ver. 2. Now go back and save that host entry. It should use ver. 2 each time you log on. <<JAV>> ---------- Original Message ----------- From: "Chris Purcell" <suse@cjp.us> To: <suse-linux-e@suse.com> Sent: Thu, 4 Mar 2004 15:17:25 -0500 (EST) Subject: [SLE] PuTTY & SuSE 9.0
In order to ssh into a SuSE 9.0 box from Windows using PuTTY, you have to select "Connection - SSH - Preferred SSH Protocol Version - 2" to ssh into the box. Is there anything on the SSH server that I can change so that I don't have to manually select the SSH version to use everytime?
Thanks, Chris
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com ------- End of Original Message -------
Joe Polk said:
You can save that setting for each entry in Putty. Just put in the hostname, choose port 22 then go down on you left and choose SSH and set it to ver. 2. Now go back and save that host entry. It should use ver. 2 each time you log on.
Joe, I'm about to deploy about 30 SuSE workstations across the country as a demo for a project. If everything works out, this could turn into 200 SuSE workstations. Since they are workstations, they use DHCP and don't have static IPs. Also, it would be more work to set PuTTY up with each workstation saved as a host. I really need a server-side solution. Thanks, Chris
You can set PuTTY to default to SSH2. Matthew -----Original Message----- From: Chris Purcell [mailto:suse@cjp.us] Sent: 04 March 2004 20:43 To: listuser@javelinux.com Cc: suse-linux-e@suse.com Subject: Re: [SLE] PuTTY & SuSE 9.0 Joe Polk said:
You can save that setting for each entry in Putty. Just put in the hostname, choose port 22 then go down on you left and choose SSH and set it to ver. 2. Now go back and save that host entry. It should use ver. 2 each time you log on.
Joe, I'm about to deploy about 30 SuSE workstations across the country as a demo for a project. If everything works out, this could turn into 200 SuSE workstations. Since they are workstations, they use DHCP and don't have static IPs. Also, it would be more work to set PuTTY up with each workstation saved as a host. I really need a server-side solution. Thanks, Chris -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Matthew Stringer said:
You can set PuTTY to default to SSH2.
Matthew
It's not just PuTTY. WinSCP does the same thing (sort of). Does anybody have a server-side solution for this? Can anyone explain to me why it does this to begin with? Does it only allow SSH v2 connections by default? I thought that editing the /etc/ssh/sshd_config file so that it says "Protocol 1,2" would fix it, but it doesn't do anything. Thanks, Chris
Thursday Mar 4 at 3:42pm, Chris Purcell wrote:
Joe Polk said:
You can save that setting for each entry in Putty. Just put in the hostname, choose port 22 then go down on you left and choose SSH and set it to ver. 2. Now go back and save that host entry. It should use ver. 2 each time you log on.
Joe, I'm about to deploy about 30 SuSE workstations across the country as a demo for a project. If everything works out, this could turn into 200 SuSE workstations. Since they are workstations, they use DHCP and don't have static IPs. Also, it would be more work to set PuTTY up with each workstation saved as a host. I really need a server-side solution.
You can still do it on the PuTTY side. Define a session, selecting protocol = SSH, Preferred SSH protocol = 2 only, and anything else you want to be default, give the session a name (say, "ssh2suse") and save it. Then when Putty starts, double-click on ssh2suse to bring up the session, and enter the host name or IP address you want to connect to and click "Open" Jim Cunning
Joe, I'm about to deploy about 30 SuSE workstations across the country as a demo for a project. If everything works out, this could turn into 200 SuSE workstations. Since they are workstations, they use DHCP and don't have static IPs. Also, it would be more work to set PuTTY up with each workstation saved as a host. I really need a server-side solution.
You can still do it on the PuTTY side. Define a session, selecting protocol = SSH, Preferred SSH protocol = 2 only, and anything else you want to be default, give the session a name (say, "ssh2suse") and save it. Then when Putty starts, double-click on ssh2suse to bring up the session, and enter the host name or IP address you want to connect to and click "Open"
Jim Cunning
Jim, thanks, I'll do this as a last resort if I can't figure something else out on the server-end. Chris
On Thu, Mar 04, 2004 at 04:07:08PM -0500, Chris Purcell wrote:
You can still do it on the PuTTY side. Define a session, selecting protocol = SSH, Preferred SSH protocol = 2 only, and anything else you want to be default, give the session a name (say, "ssh2suse") and save it. Then when Putty starts, double-click on ssh2suse to bring up the session, and enter the host name or IP address you want to connect to and click "Open" Jim Cunning
I realize that this is still a client-side solution, but it might expedite the client configuration: http://the.earth.li/~sgtatham/putty/0.54/htmldoc/Chapter4.html#4.21 It is designed to add the configuration to the registry every time you run PuTTY, and then remove it again when PuTTY is closed, but could easily be changed to just install your configuration when you put PuTTY on each client -- Jesse
On Thursday 04 March 2004 21:17, Chris Purcell wrote:
In order to ssh into a SuSE 9.0 box from Windows using PuTTY, you have to select "Connection - SSH - Preferred SSH Protocol Version - 2" to ssh into the box. Is there anything on the SSH server that I can change so that I don't have to manually select the SSH version to use everytime?
This in itself I don't understand already. As far as I understand sshd, it supports both protocol version. Perhaps you should check in your /var/log/ files (like /var/log/messages) to see why it will not connect using protocol 1. I just tried it on my SuSE 8.2 box with ssh -1 and ssh -2, and both worked without any trouble. Is it just PuTTY, or does ssh -1 localhost not work for you either? Regards, Pieter Hulshoff
In order to ssh into a SuSE 9.0 box from Windows using PuTTY, you have to select "Connection - SSH - Preferred SSH Protocol Version - 2" to ssh into the box. Is there anything on the SSH server that I can change so that I don't have to manually select the SSH version to use everytime?
This in itself I don't understand already. As far as I understand sshd, it supports both protocol version. Perhaps you should check in your /var/log/ files (like /var/log/messages) to see why it will not connect using protocol 1. I just tried it on my SuSE 8.2 box with ssh -1 and ssh -2, and both worked without any trouble. Is it just PuTTY, or does ssh -1 localhost not work for you either?
Regards,
Pieter Hulshoff
Yes, it doesn't work with v1 at all on SuSE 9.0, but it works fine on SuSE 8.2. sx270:/etc/ssh # ssh -l 1 localhost Permission denied (publickey,keyboard-interactive). sx270:/etc/ssh # In /var/log/messages, these are the errors generated from the failed PuTTY logins using ssh v1... Mar 4 16:14:01 sx270 sshd[2717]: Failed password for root from ::ffff:192.0.1.60 port 4997 Mar 4 16:14:04 sx270 sshd[2717]: Connection closed by ::ffff:192.0.1.60 When you try to connect from localhost using "ssh -l 1", these are the errors generated in /var/log/messages... Mar 4 16:15:17 sx270 sshd[2746]: Illegal user 1 from ::1 Mar 4 16:15:17 sx270 sshd[2746]: input_userauth_request: illegal user 1 Mar 4 16:15:17 sx270 sshd[2746]: Failed none for illegal user 1 from ::1 port 32786 ssh2 Mar 4 16:15:17 sx270 sshd[2746]: Postponed keyboard-interactive for illegal user 1 from ::1 port 32786 ssh2 Mar 4 16:15:19 sx270 sshd[2746]: Failed keyboard-interactive/pam for illegal user 1 from ::1 port 32786 ssh2 Mar 4 16:15:19 sx270 sshd[2746]: error: PAM: System error Mar 4 16:15:19 sx270 sshd[2746]: Failed keyboard-interactive for illegal user 1 from ::1 port 32786 ssh2 Mar 4 16:15:19 sx270 sshd[2746]: error: PAM: System error Mar 4 16:15:19 sx270 sshd[2746]: Failed keyboard-interactive for illegal user 1 from ::1 port 32786 ssh2 Mar 4 16:15:19 sx270 sshd[2746]: Connection closed by ::1 Thanks, Chris
On Thursday 04 March 2004 22:14, Chris Purcell wrote:
sx270:/etc/ssh # ssh -l 1 localhost
Why would you want to try username 1? Try ssh -1 localhost. It forces the use of Protocol 1, just like ssh -2 localhost forces the use of Protocol 2.
Mar 4 16:15:17 sx270 sshd[2746]: Illegal user 1 from ::1
There you have it: you can't log in using username 1. :) Regards, Pieter Hulshoff
sx270:/etc/ssh # ssh -l 1 localhost
Why would you want to try username 1? Try ssh -1 localhost. It forces the use of Protocol 1, just like ssh -2 localhost forces the use of Protocol 2.
Mar 4 16:15:17 sx270 sshd[2746]: Illegal user 1 from ::1
There you have it: you can't log in using username 1. :)
Regards,
Pieter Hulshoff
lol, I guess that makes sense:) Its been a long day, I guess I should proof-read my posts before I send them, huh? Okay, so I can ssh locally using v1, but cannot ssh from a Windows host using PuTTY ssh v1. ssh v1 from another Linux hosts works fine. I have some more information --> just found that you CAN ssh to a SuSE 9 box using PuTTY ssh v1, if the SuSE box is a default install that hasn't been updated. After I confirmed that it worked on a default install, I ran a YOU update and rebooted the workstation. After the reboot and updates, I'm having the same problem where I can't ssh in using Putty ssh v1. One of the YOU updates is breaking the OpenSSH server somehow. Chris
Thursday Mar 4 at 4:49pm, Chris Purcell wrote:
sx270:/etc/ssh # ssh -l 1 localhost
Why would you want to try username 1? Try ssh -1 localhost. It forces the use of Protocol 1, just like ssh -2 localhost forces the use of Protocol 2.
Mar 4 16:15:17 sx270 sshd[2746]: Illegal user 1 from ::1
There you have it: you can't log in using username 1. :)
Regards,
Pieter Hulshoff
lol, I guess that makes sense:) Its been a long day, I guess I should proof-read my posts before I send them, huh?
Okay, so I can ssh locally using v1, but cannot ssh from a Windows host using PuTTY ssh v1. ssh v1 from another Linux hosts works fine.
I have some more information --> just found that you CAN ssh to a SuSE 9 box using PuTTY ssh v1, if the SuSE box is a default install that hasn't been updated. After I confirmed that it worked on a default install, I ran a YOU update and rebooted the workstation. After the reboot and updates, I'm having the same problem where I can't ssh in using Putty ssh v1. One of the YOU updates is breaking the OpenSSH server somehow.
Take a look at /etc/sshd_config before and after the update. In particular, look at the Protocol line. The default on my system is: #Protocol 2,1 It may be that the line has been uncommented on yours, and possibly only allows v2, e.g., "Protocol 2" Jim Cunning
Take a look at /etc/sshd_config before and after the update. In particular, look at the Protocol line. The default on my system is: #Protocol 2,1
It may be that the line has been uncommented on yours, and possibly only allows v2, e.g., "Protocol 2"
I already tried this and every combination of that Protocol directive...in my third post I wrote... "I thought that editing the /etc/ssh/sshd_config file so that it says "Protocol 1,2" would fix it, but it doesn't do anything." I thought that would fix it too, but it doesn't seem to do anything. Chris
participants (6)
-
Chris Purcell -
Jesse -
Jim Cunning -
Joe Polk -
Matthew Stringer -
Pieter Hulshoff