X-Spam-Check-By: sourceware.org Date: Thu, 15 Mar 2007 12:00:16 -0400 (EDT) From: Igor Peshansky Reply-To: cygwin@cygwin.com To: "Charles D. Russell" cc: cygwin@cygwin.com Subject: RE: Accessing remote PC (ssh?) In-Reply-To: <45F9633C.2070904@bellsouth.net> Message-ID: References: <45F9633C.2070904@bellsouth.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On Thu, 15 Mar 2007, Charles D. Russell wrote: > Dave Korn wrote: > > > You already answered your own question. Set up sshd. It's "the > > Cygwin way". :-) > > When ssh and sshd are installed and configured by means of the scripts > supplied in the cygwin documentation, are static IP addresses required, > or is DHCP supported? Sshd does not care about the IP of the machine it's running on. All it does is listen on a port. Ssh stores the hostname/IP in ~/.ssh/known_hosts. If the IP changes, ssh may prompt you to accept the host keys again (although this mostly happens if using raw IPs to connect). In short, DHCP is not a problem. Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ pechtcha@cs.nyu.edu | igor@watson.ibm.com ZZZzz /,`.-'`' -. ;-;;,_ Igor Peshansky, Ph.D. (name changed!) |,4- ) )-,_. ,\ ( `'-' old name: Igor Pechtchanski '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! Freedom is just another word for "nothing left to lose"... -- Janis Joplin -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/