Hi Victor
//For SSH1//
in your /etc/ssh_config - if ListenAddress is not equal to 0.0.0.0 (listen
on all ports) then change this to replect the new IP.
// For SSH2//
in your /etc/ssh2/ssh2_config - if ListenAddress is not equal to 0.0.0.0
(listen on all ports) then change this to replect the new IP.
That should be it (I think).
When users connect the next time, they will be warned that the key has
changed, and that someone may be tapping them.
If connecting from another linux box, to get rid of this message, they will
have to remove the entry from ~/.ssh/known_hosts -- I find it easier to
simply delete this file.
I think most win32 ssh apps will ask if they should accept the new key, and
just save it.
If I'm wrong on any point (not entirely sure that you don't have to
regenerate the host servers keys), I'd love to hear about it, as I'm making
a similar move soon.
Rgds
Ben
----- Original Message -----
From: "Victor Magnani" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, April 09, 2001 3:53 PM
Subject: Changing IP's
> Hi all,
>
> New to the list. We run ssh on a linux server, and we need to change the
> IP of the box. I was wondering if there are any implications with using
> SSH aftert changing the IP of the machine. Is the license in any way
> connected to the IP address of the machine? Is there anything we would
> need to do after changing the IP to make sure ssh continues to work
> smoothly?
>
> Thanks in advance
>
> Victor Magnani
> The College of Staten Island
