RE: 2 ssh servers on 1 ip
Amos, Two things: 1.I just forget: you also need to add second line in ~/.ssh/config file"StrictHostKeyChecking no" line. It will not ask to accept key anymore. 2. My solution is totally unsecured, but it is very useful in case of automatic testing scripts, or Internal server connections. 10x Alex From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Amos ShapiraSent: Thursday, October 19, 2006 4:03 AMTo: Israel Linux Mailing listSubject: Re: 2 ssh servers on 1 ip On 19/10/06, Alexander Cheskis [EMAIL PROTECTED] wrote: Hi, I personally add following string in my ~/.ssh/config file "UserKnownHostsFile=/dev/null" Then you get asked to accept the remote host key every time you access it and loose the option to notice if/when the remote host's key is changed (which could be an indication of an attack). The previous solution suggested of configuring ssh through its config file looks like the ideal one to me.--Amos
Re: 2 ssh servers on 1 ip
A trivial solution would be to access each one of them through a different hostname which you've added to /etc/hosts. Erez D wrote: hi i have one ip on the internet, but two ssh servers. so i did port forwarding: port 501 - host1:22, port 502 - host2:22 the problem is that my local ssh client (openssh/linux) assumes they are the same computer and is not happy with them having different certificates (so i am blocked from one of them unless i delete the line from ~/.ssh/... ) is there a way around this ? erez. = To unsubscribe, send mail to [EMAIL PROTECTED] with the word unsubscribe in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
Re: 2 ssh servers on 1 ip
On Wednesday October 18 2006 16:31, Erez D wrote: hi i have one ip on the internet, but two ssh servers. so i did port forwarding: port 501 - host1:22, port 502 - host2:22 the problem is that my local ssh client (openssh/linux) assumes they are the same computer and is not happy with them having different certificates (so i am blocked from one of them unless i delete the line from ~/.ssh/... ) is there a way around this ? Get a free domain name from a dynamic ip service like DynDNS and connect by the hostname? OK, so I haven't tried setting up two ssh servers on one IP, but it should work. -- Sincerely Yours, Michael Vasiliev unfair competition, n.: Selling cheaper than we do. = To unsubscribe, send mail to [EMAIL PROTECTED] with the word unsubscribe in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
Re: 2 ssh servers on 1 ip
ssh -p 501 -o HostKeyAlias=host1.home.net [EMAIL PROTECTED] ssh -p 502 -o HostKeyAlias=host2.home.net [EMAIL PROTECTED] man ssh_config for more details :-) On 10/18/06, Erez D [EMAIL PROTECTED] wrote: hi i have one ip on the internet, but two ssh servers. so i did port forwarding: port 501 - host1:22, port 502 - host2:22 the problem is that my local ssh client (openssh/linux) assumes they are the same computer and is not happy with them having different certificates (so i am blocked from one of them unless i delete the line from ~/.ssh/... ) is there a way around this ? erez. = To unsubscribe, send mail to [EMAIL PROTECTED] with the word unsubscribe in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
RE: 2 ssh servers on 1 ip
Hi, I personally add following string in my ~/.ssh/config file "UserKnownHostsFile=/dev/null" 10x Alex From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Erez DSent: Wednesday, October 18, 2006 4:31 PMTo: Israel Linux Mailing listSubject: 2 ssh servers on 1 ip hii have one ip on the internet, but two ssh servers.so i did port forwarding: port 501 - host1:22, port 502 - host2:22the problem is that my local ssh client (openssh/linux) assumes they are the same computer and is not happy with them having different certificates (so i am blocked from one of them unless i delete the line from ~/.ssh/... )is there a way around this ?erez.
Re: 2 ssh servers on 1 ip
On 19/10/06, Alexander Cheskis [EMAIL PROTECTED] wrote: Hi, I personally add following string in my ~/.ssh/config file UserKnownHostsFile=/dev/nullThen you get asked to accept the remote host key every time you access it and loose the option to notice if/when the remote host's key is changed (which could be an indication of an attack). The previous solution suggested of configuring ssh through its config file looks like the ideal one to me.--Amos