Getting cygwin-X client running with debian server.
Hi, Just a tip for newbies (like me) that try to get cygwin-X running with debian server. Apparantly the debian server's sshd default setting is not to forward X11. The error message I then get on my x-client is Can't open display. So the following setting in /etc/ssh/sshd_config is needed: X11Forwarding yes Now I can login to the server with ssh -y -l user host And can startup e.g. my favourite editor nedit on the client. I didn't find this info in the faq, hence this note. Kind regards, Wout _ 12move ADSL vanaf 18,95 euro! GRATIS modem, GEEN aansluitkosten en GEEN datalimiet! Ga nu naar http://adsl.12move.nl
src/winsup/cygwin ChangeLog fhandler_disk_file.cc
CVSROOT:/cvs/src Module name:src Changes by: [EMAIL PROTECTED] 2005-04-16 12:53:49 Modified files: winsup/cygwin : ChangeLog fhandler_disk_file.cc Log message: * fhandler_disk_file.cc (fhandler_base::utimes_fs): Drop touching ChangeTime. Patches: http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/winsup/cygwin/ChangeLog.diff?cvsroot=srcr1=1.2841r2=1.2842 http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/winsup/cygwin/fhandler_disk_file.cc.diff?cvsroot=srcr1=1.118r2=1.119
src/winsup/cygwin ChangeLog environ.cc
CVSROOT:/cvs/src Module name:src Changes by: [EMAIL PROTECTED] 2005-04-16 13:11:40 Modified files: winsup/cygwin : ChangeLog environ.cc Log message: * environ.cc (environ_init): Don't set traverse checking as default. Patches: http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/winsup/cygwin/ChangeLog.diff?cvsroot=srcr1=1.2842r2=1.2843 http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/winsup/cygwin/environ.cc.diff?cvsroot=srcr1=1.113r2=1.114
src/winsup/doc ChangeLog cygwinenv.sgml
CVSROOT:/cvs/src Module name:src Changes by: [EMAIL PROTECTED] 2005-04-16 13:16:25 Modified files: winsup/doc : ChangeLog cygwinenv.sgml Log message: * cygwinenv.sgml: Add new words for (no)traverse option. Patches: http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/winsup/doc/ChangeLog.diff?cvsroot=srcr1=1.89r2=1.90 http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/winsup/doc/cygwinenv.sgml.diff?cvsroot=srcr1=1.17r2=1.18
src/winsup/cygwin ChangeLog grp.cc security.cc ...
CVSROOT:/cvs/src Module name:src Changes by: [EMAIL PROTECTED] 2005-04-16 15:21:48 Modified files: winsup/cygwin : ChangeLog grp.cc security.cc security.h Log message: * security.h (cygsidlist::addfromgr): Allow duplicate entries. (get_server_groups): Declare new function. * security.cc (is_group_member): Simplify. (get_server_groups): New function. (get_initgroups_sidlist): Call get_server_groups. (verify_token): Allow token when supplementary sids are not in /etc/group but are in the token. Streamline the code. * grp.cc (initgroups32): New implementation. (getgroups32): Handle case where the supplementary groups are set. Patches: http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/winsup/cygwin/ChangeLog.diff?cvsroot=srcr1=1.2843r2=1.2844 http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/winsup/cygwin/grp.cc.diff?cvsroot=srcr1=1.96r2=1.97 http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/winsup/cygwin/security.cc.diff?cvsroot=srcr1=1.182r2=1.183 http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/winsup/cygwin/security.h.diff?cvsroot=srcr1=1.62r2=1.63
src/winsup/cygwin ChangeLog fhandler_disk_file ...
CVSROOT:/cvs/src Module name:src Changes by: [EMAIL PROTECTED] 2005-04-16 17:17:33 Modified files: winsup/cygwin : ChangeLog fhandler_disk_file.cc path.cc Log message: * fhandler_disk_file.cc (fhandler_base::utimes_fs): Ignore ERROR_NOT_SUPPORTED to workaround Win9x weirdness. * path.cc (symlink_info::check): Remap ERROR_INVALID_FUNTION to ERROR_FILE_NOT_FOUND for the same reason. Patches: http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/winsup/cygwin/ChangeLog.diff?cvsroot=srcr1=1.2844r2=1.2845 http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/winsup/cygwin/fhandler_disk_file.cc.diff?cvsroot=srcr1=1.119r2=1.120 http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/winsup/cygwin/path.cc.diff?cvsroot=srcr1=1.361r2=1.362
winsup/cygwin fhandler.h fhandler_disk_file.cc ...
CVSROOT:/cvs/uberbaum Module name:winsup Changes by: [EMAIL PROTECTED] 2005-04-17 00:12:14 Modified files: cygwin : fhandler.h fhandler_disk_file.cc fhandler_fifo.cc pinfo.cc Log message: Actually check in files. Patches: http://sources.redhat.com/cgi-bin/cvsweb.cgi/winsup/cygwin/fhandler.h.diff?cvsroot=uberbaumr1=1.239r2=1.240 http://sources.redhat.com/cgi-bin/cvsweb.cgi/winsup/cygwin/fhandler_disk_file.cc.diff?cvsroot=uberbaumr1=1.120r2=1.121 http://sources.redhat.com/cgi-bin/cvsweb.cgi/winsup/cygwin/fhandler_fifo.cc.diff?cvsroot=uberbaumr1=1.8r2=1.9 http://sources.redhat.com/cgi-bin/cvsweb.cgi/winsup/cygwin/pinfo.cc.diff?cvsroot=uberbaumr1=1.168r2=1.169
Where is source for dos2unix
Where is the source code for dos2unix? The executable is in the cygutils-1.2.7-1 tarball, but the source code is not in the cygutils-1.2.7-1-src tarball. Is this just an error with this version. Should I look in an earlier version of cygutils? -- Brian Salter-Duke (Brian Duke) [EMAIL PROTECTED] Post: 626 Melbourne Rd, Spotswood, VIC, 3015, Australia Phone 03-93992847. http://members.iinet.net.au/~linden1/brian/ -- 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/
Re: Where is source for dos2unix
Brian Salter-Duke wrote:
Where is the source code for dos2unix? The executable is in the
cygutils-1.2.7-1 tarball, but the source code is not in the
cygutils-1.2.7-1-src tarball. Is this just an error with this version.
Should I look in an earlier version of cygutils?
u2d, d2u, and conv are all the same binary with different names:
$ md5sum -b /usr/bin/{d2u,u2d,conv}.exe
850b9a5fac0e26ea5b00ec87e6cf344b */usr/bin/d2u.exe
850b9a5fac0e26ea5b00ec87e6cf344b */usr/bin/u2d.exe
850b9a5fac0e26ea5b00ec87e6cf344b */usr/bin/conv.exe
The source to conv is in the cygutils source package.
Brian
--
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/
Re: sshd problems
dear john thanks a lot for your help; i write you here some answers at your indications - On the cygwin machine itself, can you ssh localhost? If you can't do that then sshd still has a - problem. If you can connect to localhost that proves that sshd is running okay on the cygwin - machine. - yes, ssh localhost works fine, (but isn't it working with loopback device instead of eth0??) - If you use the -v option you will get debug information that can be of help. Use this command: - ssh -v host_name - - where host_name is the name of the machine. If you're trying to connect to the cygwin - machine the command would be: - - ssh -v localhost - - You'll see lots of debug information. - - Once you can connect locally to the cygwin machine, then you can start solving the problems - from the Linux box. that's what happens from the cygwin machine ssh -v localhost OpenSSH_4.0p1, OpenSSL 0.9.7f 22 mar 2005 debug1: Reading configuration data /etc/ssh_config debug1: Connecting to localhost [127.0.0.1] port 22. debug1: Connection established. debug1: identity file /home/user/.ssh/identity type -1 debug1: identity file /home/user/.ssh/id_rsa type -1 debug1: identity file /home/user/.ssh/id_dsa type -1 debug1: Remote protocol version 1.99, remote software version OpenSSH_4.0 debug1: match: OpenSSH_4.0 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_4.0 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server-client aes128-cbc hmac-md5 none debug1: kex: client-server aes128-cbc hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(102410248192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug1: Host 'localhost' is known and matches the RSA host key. debug1: Found key in /home/user/.ssh/known_hosts:2 debug1: ssh_rsa_verify: signature correct debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey, password,keyboard-interactive debug1: Next authentication method: publickey debug1: Trying private key: /home/user/.ssh/identity debug1: Trying private key: /home/user/.ssh/id_rsa debug1: Trying private key: /home/user/.ssh/id_dsa debug1: Next authentication method: keyboard-interactive debug1: Authentications that can continue: publickey, password,keyboard-interactive debug1: Next authentication method: password [EMAIL PROTECTED]'s password: debug1: Authentication succeeded (password). debug1: channel 0: new [client-session] debug1: Entering interactive session. Last login: from * that's what happens when I try ssh from linux machine (LM) to the cygwin machine(CM) ssh -v [EMAIL PROTECTED] machine OpenSSH_3.9p1, OpenSSL 0.9.7a Feb 19 2003 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: Connecting to ip_cgwin machine [ip_cgwin machine] port 22. debug1: connect to address ip_cgwin machine port 22: Connection timed out ssh: connect to host ip_cgwin machine port 22: Connection timed out I also add the ssh from the CM to ip_CM ssh -v ip_cgwin machine OpenSSH_4.0p1, OpenSSL 0.9.7f 22 mar 2005 debug1: Reading configuration data /etc/ssh_config debug1: Connecting to ip_cgwin machine [ip_cgwin machine] port 22. debug1: Connection established. debug1: identity file /home/user/.ssh/identity type -1 debug1: identity file /home/user/.ssh/id_rsa type -1 debug1: identity file /home/user/.ssh/id_dsa type -1 debug1: Remote protocol version 1.99, remote software version OpenSSH_4.0 debug1: match: OpenSSH_4.0 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_4.0 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server-client aes128-cbc hmac-md5 none debug1: kex: client-server aes128-cbc hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(102410248192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug1: Host 'ip_cygwin_machine' is known and matches the RSA host key. debug1: Found key in /home/user/.ssh/known_hosts:3 debug1: ssh_rsa_verify: signature correct debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey, password,keyboard-interactive debug1: Next authentication method: publickey debug1: Trying private key: /home/user/.ssh/identity debug1: Trying private key: /home/user/.ssh/id_rsa debug1: Trying private key: /home/user/.ssh/id_dsa debug1: Next authentication method: keyboard-interactive debug1: Authentications that can continue: publickey,
Re: sshd problems
dear larry thanks a lot for your answer; I don't understand very well your suggestion: I wrote: -$ nedit .ssh/known_hosts - -here I canceled lines rlative to cygwin machine and tried again: - -$ ssh [EMAIL PROTECTED] -ssh: connect to host port 22: Connection timed out -$ ssh [EMAIL PROTECTED] -ssh: connect to host port 22: Connection timed out -$ - -Please, have you got any idea??? You answered: Is sshd still running? If you were running it in debug mode, it won't be now. Restart it. If it is running, I suggest stopping it and adding debug flags (-d -d -d) to the sshd service and restarting. This will generate debug information in the log that should be helpful. -Yes sshd was running(i also tried today) I do not understand te secon suggestion(I'm not an expert): how can I know I'm running sshd in debug mode? how do I add debug flags to the service? Anyway i got some debug info in another way(-v flag): here I try ssh from cygwin machine to itself: ssh -v localhost OpenSSH_4.0p1, OpenSSL 0.9.7f 22 mar 2005 debug1: Reading configuration data /etc/ssh_config debug1: Connecting to localhost [127.0.0.1] port 22. debug1: Connection established. debug1: identity file /home/user/.ssh/identity type -1 debug1: identity file /home/user/.ssh/id_rsa type -1 debug1: identity file /home/user/.ssh/id_dsa type -1 debug1: Remote protocol version 1.99, remote software version OpenSSH_4.0 debug1: match: OpenSSH_4.0 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_4.0 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server-client aes128-cbc hmac-md5 none debug1: kex: client-server aes128-cbc hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(102410248192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug1: Host 'localhost' is known and matches the RSA host key. debug1: Found key in /home/user/.ssh/known_hosts:2 debug1: ssh_rsa_verify: signature correct debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey, password,keyboard-interactive debug1: Next authentication method: publickey debug1: Trying private key: /home/user/.ssh/identity debug1: Trying private key: /home/user/.ssh/id_rsa debug1: Trying private key: /home/user/.ssh/id_dsa debug1: Next authentication method: keyboard-interactive debug1: Authentications that can continue: publickey, password,keyboard-interactive debug1: Next authentication method: password [EMAIL PROTECTED]'s password: debug1: Authentication succeeded (password). debug1: channel 0: new [client-session] debug1: Entering interactive session. Last login: from * that's what happens when I try ssh from linux machine (LM) to the cygwin machine(CM) ssh -v [EMAIL PROTECTED] machine OpenSSH_3.9p1, OpenSSL 0.9.7a Feb 19 2003 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: Connecting to ip_cgwin machine [ip_cgwin machine] port 22. debug1: connect to address ip_cgwin machine port 22: Connection timed out ssh: connect to host ip_cgwin machine port 22: Connection timed out I also add the ssh from the CM to ip_CM ssh -v ip_cgwin machine OpenSSH_4.0p1, OpenSSL 0.9.7f 22 mar 2005 debug1: Reading configuration data /etc/ssh_config debug1: Connecting to ip_cgwin machine [ip_cgwin machine] port 22. debug1: Connection established. debug1: identity file /home/user/.ssh/identity type -1 debug1: identity file /home/user/.ssh/id_rsa type -1 debug1: identity file /home/user/.ssh/id_dsa type -1 debug1: Remote protocol version 1.99, remote software version OpenSSH_4.0 debug1: match: OpenSSH_4.0 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_4.0 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server-client aes128-cbc hmac-md5 none debug1: kex: client-server aes128-cbc hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(102410248192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug1: Host 'ip_cygwin_machine' is known and matches the RSA host key. debug1: Found key in /home/user/.ssh/known_hosts:3 debug1: ssh_rsa_verify: signature correct debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey, password,keyboard-interactive debug1: Next authentication method: publickey debug1: Trying private key: /home/user/.ssh/identity debug1: Trying private key: /home/user/.ssh/id_rsa debug1: Trying private key:
Re: sshd problems
dear larry thanks a lot for your answer; I don't understand very well your suggestion: I wrote: -$ nedit .ssh/known_hosts - -here I canceled lines rlative to cygwin machine and tried again: - -$ ssh [EMAIL PROTECTED] -ssh: connect to host port 22: Connection timed out -$ ssh [EMAIL PROTECTED] -ssh: connect to host port 22: Connection timed out -$ - -Please, have you got any idea??? You answered: Is sshd still running? If you were running it in debug mode, it won't be now. Restart it. If it is running, I suggest stopping it and adding debug flags (-d -d -d) to the sshd service and restarting. This will generate debug information in the log that should be helpful. -Yes sshd was running(i also tried today) I do not understand te secon suggestion(I'm not an expert): how can I know I'm running sshd in debug mode? how do I add debug flags to the service? Anyway i got some debug info in another way(-v flag): here I try ssh from cygwin machine to itself: ssh -v localhost OpenSSH_4.0p1, OpenSSL 0.9.7f 22 mar 2005 debug1: Reading configuration data /etc/ssh_config debug1: Connecting to localhost [127.0.0.1] port 22. debug1: Connection established. debug1: identity file /home/user/.ssh/identity type -1 debug1: identity file /home/user/.ssh/id_rsa type -1 debug1: identity file /home/user/.ssh/id_dsa type -1 debug1: Remote protocol version 1.99, remote software version OpenSSH_4.0 debug1: match: OpenSSH_4.0 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_4.0 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server-client aes128-cbc hmac-md5 none debug1: kex: client-server aes128-cbc hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(102410248192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug1: Host 'localhost' is known and matches the RSA host key. debug1: Found key in /home/user/.ssh/known_hosts:2 debug1: ssh_rsa_verify: signature correct debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey, password,keyboard-interactive debug1: Next authentication method: publickey debug1: Trying private key: /home/user/.ssh/identity debug1: Trying private key: /home/user/.ssh/id_rsa debug1: Trying private key: /home/user/.ssh/id_dsa debug1: Next authentication method: keyboard-interactive debug1: Authentications that can continue: publickey, password,keyboard-interactive debug1: Next authentication method: password [EMAIL PROTECTED]'s password: debug1: Authentication succeeded (password). debug1: channel 0: new [client-session] debug1: Entering interactive session. Last login: from * that's what happens when I try ssh from linux machine (LM) to the cygwin machine(CM) ssh -v [EMAIL PROTECTED] machine OpenSSH_3.9p1, OpenSSL 0.9.7a Feb 19 2003 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: Connecting to ip_cgwin machine [ip_cgwin machine] port 22. debug1: connect to address ip_cgwin machine port 22: Connection timed out ssh: connect to host ip_cgwin machine port 22: Connection timed out I also add the ssh from the CM to ip_CM ssh -v ip_cgwin machine OpenSSH_4.0p1, OpenSSL 0.9.7f 22 mar 2005 debug1: Reading configuration data /etc/ssh_config debug1: Connecting to ip_cgwin machine [ip_cgwin machine] port 22. debug1: Connection established. debug1: identity file /home/user/.ssh/identity type -1 debug1: identity file /home/user/.ssh/id_rsa type -1 debug1: identity file /home/user/.ssh/id_dsa type -1 debug1: Remote protocol version 1.99, remote software version OpenSSH_4.0 debug1: match: OpenSSH_4.0 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_4.0 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server-client aes128-cbc hmac-md5 none debug1: kex: client-server aes128-cbc hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(102410248192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug1: Host 'ip_cygwin_machine' is known and matches the RSA host key. debug1: Found key in /home/user/.ssh/known_hosts:3 debug1: ssh_rsa_verify: signature correct debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey, password,keyboard-interactive debug1: Next authentication method: publickey debug1: Trying private key: /home/user/.ssh/identity debug1: Trying private key: /home/user/.ssh/id_rsa debug1: Trying private key:
Re: sshd problems
From your data it appears that you can ssh to the localhost which means your sshd server is running. However, you can't connect to your localhost from the Linux machine; the connection times out. Your other examples all look like they are connections from the localhost to other machines, which all appear to work. Is this a Windows XP machine with Service Pack 2 installed? Have you opened up the firewall to allow port 22 through? If not, that explains your problem. Port 22 is blocked by default. The firewall won't block ssh connections originating from your localhost to other machines. That would be consistent with the data you've shown. John On 16 Apr 2005 at 9:03, giuseppe wrote: To: cygwin@cygwin.com From: giuseppe [EMAIL PROTECTED] Subject:Re: sshd problems Date sent: Sat, 16 Apr 2005 09:03:35 + (UTC) [ Double-click this line for list subscription options ] dear john thanks a lot for your help; i write you here some answers at your indications - On the cygwin machine itself, can you ssh localhost? If you can't do that then sshd still has a - problem. If you can connect to localhost that proves that sshd is running okay on the cygwin - machine. - yes, ssh localhost works fine, (but isn't it working with loopback device instead of eth0??) - If you use the -v option you will get debug information that can be of help. Use this command: - ssh -v host_name - - where host_name is the name of the machine. If you're trying to connect to the cygwin - machine the command would be: - - ssh -v localhost - - You'll see lots of debug information. - - Once you can connect locally to the cygwin machine, then you can start solving the problems - from the Linux box. that's what happens from the cygwin machine ssh -v localhost OpenSSH_4.0p1, OpenSSL 0.9.7f 22 mar 2005 debug1: Reading configuration data /etc/ssh_config debug1: Connecting to localhost [127.0.0.1] port 22. debug1: Connection established. debug1: identity file /home/user/.ssh/identity type -1 debug1: identity file /home/user/.ssh/id_rsa type -1 debug1: identity file /home/user/.ssh/id_dsa type -1 debug1: Remote protocol version 1.99, remote software version OpenSSH_4.0 debug1: match: OpenSSH_4.0 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_4.0 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server-client aes128-cbc hmac-md5 none debug1: kex: client-server aes128-cbc hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(102410248192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug1: Host 'localhost' is known and matches the RSA host key. debug1: Found key in /home/user/.ssh/known_hosts:2 debug1: ssh_rsa_verify: signature correct debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey, password,keyboard-interactive debug1: Next authentication method: publickey debug1: Trying private key: /home/user/.ssh/identity debug1: Trying private key: /home/user/.ssh/id_rsa debug1: Trying private key: /home/user/.ssh/id_dsa debug1: Next authentication method: keyboard-interactive debug1: Authentications that can continue: publickey, password,keyboard-interactive debug1: Next authentication method: password [EMAIL PROTECTED]'s password: debug1: Authentication succeeded (password). debug1: channel 0: new [client-session] debug1: Entering interactive session. Last login: from * that's what happens when I try ssh from linux machine (LM) to the cygwin machine(CM) ssh -v [EMAIL PROTECTED] machine OpenSSH_3.9p1, OpenSSL 0.9.7a Feb 19 2003 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: Connecting to ip_cgwin machine [ip_cgwin machine] port 22. debug1: connect to address ip_cgwin machine port 22: Connection timed out ssh: connect to host ip_cgwin machine port 22: Connection timed out I also add the ssh from the CM to ip_CM ssh -v ip_cgwin machine OpenSSH_4.0p1, OpenSSL 0.9.7f 22 mar 2005 debug1: Reading configuration data /etc/ssh_config debug1: Connecting to ip_cgwin machine [ip_cgwin machine] port 22. debug1: Connection established. debug1: identity file /home/user/.ssh/identity type -1 debug1: identity file /home/user/.ssh/id_rsa type -1 debug1: identity file /home/user/.ssh/id_dsa type -1 debug1: Remote protocol version 1.99, remote software version OpenSSH_4.0 debug1: match: OpenSSH_4.0 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_4.0 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server-client aes128-cbc hmac-md5 none
Re: Possible to create an X application not linked to cygwin1.dll?
On Fri, Apr 15, 2005 at 11:28:33PM -0400, Christopher Faylor wrote: No, you can't do what you want to do. You could ask about this in the BLAH mailing list, however. This topic certainly has nothing to do with this mailing list. Just for the don't use raw email addresses in the body of messages police -- yes, I realize that I did this. My bad. -- 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/
