Re: Openssh compatibility problem?

2009-01-03 Thread Michael Makuch
Charles Wilson wrote: 2) In some recent release the default hosts.allow has been modified to ALL : PARANOID : deny sshd: ALL If there is a mismatch, then (a) there is a DNS misconfiguration, or (b) somebody is trying to spoof/hack you. In your case, I'd guess DNS misconfiguration. I see. I

Re: Openssh compatibility problem?

2009-01-03 Thread Michael Makuch
Charles Wilson wrote: Michael Makuch wrote: This is not a compatibility problem between cygwin/openssh versions. I am now seeing the problem just trying to ssh from plum to plum (an XP box). It seems that openssh 5.1 on cygwin is loaded with problems. Anyone have it working? Anyone able to get

Re: Openssh compatibility problem?

2009-01-03 Thread Michael Makuch
Michael Makuch wrote: Recently installed latest cygwin and can't ssh to it from older openssh rev. Is there a known compatibility problem? 3 systems: plum, oak, pecan I can ssh from pecan to oak. I cannot ssh from pecan to plum, it appears to timeout. Versions of the 3 systems: plum $

Openssh compatibility problem?

2008-12-30 Thread Michael Makuch
Recently installed latest cygwin and can't ssh to it from older openssh rev. Is there a known compatibility problem? 3 systems: plum, oak, pecan I can ssh from pecan to oak. I cannot ssh from pecan to plum, it appears to timeout. Versions of the 3 systems: plum $ uname -a CYGWIN_NT-5.1 plum

setup.exe q's

2004-09-27 Thread Michael Makuch
i) I read a page on cygwin.com that says "$ setup.exe --help" will display optional command line args, yet it doesn't appear to do so? ii) Is there any way to skip the md5 checking of packages when setup starts up? Yes, I understand the risk of skipping that step but it'd be nice to be able to get