Re: can't ssh to self -amended w/cygcheck
Lex Ein wrote: After what seemed like a normal May 2005 Cygwin update, my Ohio remote Win2K SP4 machine stopped accepting ssh connections. For two years up to that point, no Cygwin update interfered with normal SSH operation. Via a naked VNC connection, in the Cygwin shell, 'ssh -vvv localhost' fails with the error message "ssh_exchange_identification: Connection closed by remote host". See -vvv output below: I removed cygwin from the machine and freshly installed (today) the current release of Cygwin and openssh/ssl, cyrunsrv, etc. Same result. I have tried with and without ntsec. sshd does run, it appears in the ps output.. Installation on about six other systems has been trouble-free; each of these successes encouraged me to retry getting the remote system running ssh again. Every time, failure. I'm not understanding the clues in man sshd or man ssh or the readmes. I don't seem to be able to get sshd to generate log entries to /var/log/* as suggested by man sshd. I'm afraid I need some damn handholding to get this thing running. $ ssh -vvv localhost OpenSSH_4.2p1, OpenSSL 0.9.8a 11 Oct 2005 debug1: Reading configuration data /etc/ssh_config debug2: ssh_connect: needpriv 0 debug1: Connecting to localhost [127.0.0.1] port 22. debug1: Connection established. debug1: identity file /home/NotRevealed/.ssh/identity type -1 debug3: Not a RSA1 key file /home/NotRevealed/.ssh/id_rsa. debug2: key_type_from_name: unknown key type '-BEGIN' debug3: key_read: missing keytype debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug2: key_type_from_name: unknown key type '-END' debug3: key_read: missing keytype debug1: identity file /home/NotRevealed/.ssh/id_rsa type 1 debug3: Not a RSA1 key file /home/NotRevealed/.ssh/id_dsa. debug2: key_type_from_name: unknown key type '-BEGIN' debug3: key_read: missing keytype debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug2: key_type_from_name: unknown key type '-END' debug3: key_read: missing keytype debug1: identity file /home/NotRevealed/.ssh/id_dsa type 2 ssh_exchange_identification: Connection closed by remote host [EMAIL PROTECTED] ~ $ Cygwin Configuration Diagnostics Current System Time: Sat Jan 21 20:51:15 2006 Windows 2000 Professional Ver 5.0 Build 2195 Service Pack 4 Path:C:\cygwin\usr\local\bin C:\cygwin\bin C:\cygwin\bin C:\cygwin\usr\X11R6\bin c:\WINNT\system32 c:\WINNT c:\WINNT\System32\Wbem c:\Program Files\Real\Helix Producer Basic C:\cygwin\bin C:\cygwin\sbin c:\bin c:\Novell\Client32 .\ c:\PROGRA~1\NETWOR~1\MCAFEE~1 Output from C:\cygwin\bin\id.exe (nontsec) UID: 500(NotRevealed) GID: 513(None) 0(root) 513(None) 544(NotRevealeds) 545(Users) Output from C:\cygwin\bin\id.exe (ntsec) UID: 500(NotRevealed) GID: 513(None) 0(root) 513(None) 544(NotRevealeds) 545(Users) SysDir: C:\WINNT\system32 WinDir: C:\WINNT USER = 'NotRevealed' PWD = '/home/NotRevealed' CYGWIN = 'ntsec tty' HOME = '/home/NotRevealed' MAKE_MODE = 'unix' HOMEPATH = '\Documents and Settings\NotRevealed' MANPATH = '/usr/local/man:/usr/share/man:/usr/man::/usr/ssl/man' APPDATA = 'C:\Documents and Settings\NotRevealed\Application Data' HOSTNAME = 'lamachine' TERM = 'cygwin' PROCESSOR_IDENTIFIER =
can't ssh to self
After what seemed like a normal May 2005 Cygwin update, my Ohio remote Win2K SP4 machine stopped accepting ssh connections. For two years up to that point, no Cygwin update interfered with normal SSH operation. Via a naked VNC connection, in the Cygwin shell, 'ssh -vvv localhost' fails with the error message "ssh_exchange_identification: Connection closed by remote host". See -vvv output below: I removed cygwin from the machine and freshly installed (today) the current release of Cygwin and openssh/ssl, cyrunsrv, etc. Same result. I have tried with and without ntsec. sshd does run, it appears in the ps output.. Installation on about six other systems has been trouble-free; each of these successes encouraged me to retry getting the remote system running ssh again. Every time, failure. I'm not understanding the clues in man sshd or man ssh or the readmes. I don't seem to be able to get sshd to generate log entries to /var/log/* as suggested by man sshd. I'm afraid I need some damn handholding to get this thing running. $ ssh -vvv localhost OpenSSH_4.2p1, OpenSSL 0.9.8a 11 Oct 2005 debug1: Reading configuration data /etc/ssh_config debug2: ssh_connect: needpriv 0 debug1: Connecting to localhost [127.0.0.1] port 22. debug1: Connection established. debug1: identity file /home/user/.ssh/identity type -1 debug3: Not a RSA1 key file /home/user/.ssh/id_rsa. debug2: key_type_from_name: unknown key type '-BEGIN' debug3: key_read: missing keytype debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug2: key_type_from_name: unknown key type '-END' debug3: key_read: missing keytype debug1: identity file /home/user/.ssh/id_rsa type 1 debug3: Not a RSA1 key file /home/user/.ssh/id_dsa. debug2: key_type_from_name: unknown key type '-BEGIN' debug3: key_read: missing keytype debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug2: key_type_from_name: unknown key type '-END' debug3: key_read: missing keytype debug1: identity file /home/user/.ssh/id_dsa type 2 ssh_exchange_identification: Connection closed by remote host [EMAIL PROTECTED] ~ $ -- 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: PostInstallLast addons?
On Sat, 9 Oct 2004 16:19:36 -0400, "Christopher Faylor" <[EMAIL PROTECTED]> said: > On Sat, Oct 09, 2004 at 07:28:14PM +0200, Reini Urban wrote: > >Robert R Schneck schrieb: > >>lex ein wrote: > >>>6. If a user has by some miracle heard of 'locate', a search using > >>>'locate openssh' produces no results unless the user first runs > >>>'updatedb'. > >> > >>Would it be appropriate for the PostInstallLast part of setup which > >>"updates info dir" to also run makewhatis? And perhaps even updatedb? > > > >Very unlikely. > >These are quite massive processes in contrary to _update-info-dir > > [...] > Boy, I started a makewhatis at the start of this message. It's been > a few minutes, and it's still going. > > > > It took *seven* minutes to complete (cygwin sucks. why is it so slow? > discuss amongst yourselves) I guess we really can't add this to the > setup process. > > cgf How about a few extra checkbox items on the "Cygwin Setup - Create Icons" screen in setup.exe? "Cygwin Setup - Finish Create icons Have setup create icons for easy access to the Cygwin environment. [ ] Create icon on _Desktop [ ] Add icon to _Start Menu Optional tasks - (may take many minutes!) [ ] Build database (makewhatis) of man page short descriptions for 'whatis' & 'apropos'. [ ] Build database (updatedb) of file names for 'locate'. Display README information at exit. [ ] Display /usr/share/doc/Cygwin/ directory of README files. " -- 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: Cygwin & openssh(d) & login without password
On Tue, 5 Oct 2004 10:47:57 +0200, Corinna Vinschen <[EMAIL PROTECTED]> wrote: On Oct 5 16:00, David Campbell wrote: I've read lots of web pages about how to set it up, and I believe I've followed them, eg http://bumblebee.lcs.mit.edu/ssh2/ (for openssh to openssh): WHY DON'T YOU READ THE OFFICIAL DOCUMENTATION INSTEAD? [caps mine] OpenSSH comes with a lot of man pages. Then there's /usr/share/doc/Cygwin/openssh.README. Then you could have used ssh-host-config and ssh-user-config for the basic configuration. BECAUSE in the case of openssh(and others), the "official documentation" is of little use to a new user: information is not gathered, stored, or presented in a orderly, logical, or sensible hierarchical manner, is not meaningfully cross-referenced, and is not reasonably searchable. There's just no usable thread to pull to unravel the mystery, either. Let's examine the steps a new user might pursue: 1. A new user types 'help' and is presented with shell help. Luckily, there's a mention of 'man -k'(which doesn't work) and 'info'. 2. The user might type 'help openssh' and be told to "try 'man -k openssh' which produces "openssh: nothing appropriate", a nice showstopper. IF enterprising (and unafraid of the command line) enough, one _might_ try 'man openssh', and 'info openssh' and be met with stony silence. 3. One may try 'help ssh' and be told to "try 'man -k ssh' which produces "ssh: nothing appropriate", another showstopper. One _might_ ultimately try 'man ssh' instead and get (sort of) lucky. 4. 'man' and 'info' pages for ssh and sshd don't refer to /usr/share/doc/Cygwin/openssh.README, nor to /usr/share/doc/ssh/ssh-host-config or ssh-user-config. So the new user is confronted with a brightly lit maze of lucidly defined options and configuration information. 5. A search using 'find / -name openssh*' does find appropriate directories, and even the README. However, 'find' is ill-behaved: alone on a command line, it prints a _full recursive tree_ of the current directory. It's counterintuitive, and ill-documented. 'man find' shows no functional examples. 'find --help' lists options, not ordered by likelyhood of use, but _alphabetically_. Only 'info find' shows a useful example. And if the unlucky user forgets to type 'openssh*', they'll miss the README file. Nice. 6. If a user has by some miracle heard of 'locate', a search using 'locate openssh' produces no results unless the user first runs 'updatedb'. 7. So someone in a hurry is likely instead to go out-of band: 7a. Google for "cygwin openssh setup" produces NO useful official documentation in the first 50 results. In fact, the very first result is the http://tech.erdelynet.com/cygwin-sshd.html . This resource has been maligned in this very cygwin list. 7b. Windows Find "openssh" finds whatever _might_ be there to see. 8. Let's say the user somehow finds openssh.README. Who the HELL decided to put the "If you are installing OpenSSH the first time" at the END of a four-page document? Wading through panicky "important change" notices is rather pure torture, and irrelevant to the new user. So these little unfindable jewels exist not to be used _by_ new users, but to be shot _at_ new users in ascerbic opprobrium. To make the docs _easy_ to find would go against the dinosaur mentality of "Back in the day, I had to read all the docs before I could do anything, and now so do you." The major difference being that back in the day, all the docs fit in a 1/4" booklet. Now the task of forcing the user to imagine, compose a search for, search for, find, read, interpret, and correctly apply the hidden, terse, ultimately unhelpful, poorly referenced "official documentation" is simply onerous. So, let's have no more asking new users why they didn't read the official documentation, then, eh? They have _very good reasons_ for not doing so. -- 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: mod-php4 missing from cygwin distro
Larry Hall wrote: ... I would be very grateful to anyone who could give me leads on what happened to the php libs. ... mod-php4 is not part of the distribution at this time. There are plans to re-add it in the future. No, I don't know when that will be. ;-) What were the reasons for removal? 1. WJM. 2. redundancy? (easy to grab&compile or grab&run if needed) 3. technical? (difficulty integrating into cygwin release pipeline, cross-compilation probs, slow bug fixes) 4. political/personal? 5. other? (URL or concise, relevant reason here) -- 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: is ms internet explorer 5 a spambot?
>>> When I tried to access messages in the cygwin mailing list archive >>> (using ms internet explorer 5), I got the following: >>>Spambot detected. >>>Hi, your web browser has triggered our spambot detection mechanism. >>><...> >>> I understand the humor. However, cygwin is intended to run under >>> ms windows, where ie 5 is the standard web browser, isn't it? >>> Any suggestions? The fine Opera browser also works with the archives, and can be quick-preference set to identify as other browsers. If you must use IE and happen to browse promiscuously, do run cwshredder to eliminate a particularly pernicious browser-helper-object. I'm just saying. http://www.spywareinfo.com/~merijn/cwschronicles.html Okay, NOW we're off the rigidly defined Cygwin topic, but it was short, wasn't it? L1 -- 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: THANKS for a fantastic product
Guy Stalnaker wrote: > Figure cygwin developers rarely get kudos, but here's one! Here's another:(Imagine Michael Moore reading this aloud:) I'm using Cygwin for remote sshd/vnc access to a four-armed triple-jointed servopneumatic robotic system which could fatally stab or crush someone if they were standing in the wrong place during a software glitch. It can also demolish the ceiling and rip itself up by the anchor bolts. When the lease is up, de-installation will be easy. For safety we decided that a water-filled moat around the machine was cheaper than fixing the software. Besides, the bug budget and insurance carrier allow one catastrophic flail/kill failure every 4 years, and we're only operating it for 3. Count me one happy Cygwin user. Next contract: medical monitoring devices. Lex (Relax folks, it's all true.) -- 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: Cygwin Nightly Snapshots
http://www.cygwin.com/snapshots/ "Cygwin Interim Snapshots" Whoo, racy. Guess I missed the party. L Dave Korn wrote: -Original Message- From: cygwin-owner On Behalf Of fergus bonhard Sent: 07 June 2004 12:23 Hi, Not wishing or intending to sound a complete head-banger, I've lately taken to moderately frequent visits to Cygwin Nightly Snapshots, thereby increasing the likelihood of those visits being observed (Person Over Shoulder). It's a hell of a banner headline title that one might end up having to explain to a wife or a boss. Any chance of a different name?! Fergus I agree. I propose we rename the page to "Fresh Hot Wet Cygwin Images" forthwith! cheers, DaveK -- 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: gcc inst hosed after upgrading to cygwin 1.5.10x
Quoting: "One of the cygwin mailing lists is absolutely the proper place for reporting problems. The mailing lists were created for this express purpose. " So, your point was? L Brian Ford wrote: On Thu, 27 May 2004, Hans Horn wrote: Folks, after I had an upgrade orgy to cygwin 1.5.10.x, my gcc installation got hosed. in particular: gcc: installation problem, cannot exec `cc1plus': No such file or directory completely uninstalling and then re-installing all gcc related stuff doesn't help! Any clues / advice? Just one: Problem reports: http://cygwin.com/problems.html -- 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/
How to force Setup.exe to behave?
Nine days ago, this was "Using Setup.exe to uninstall -bogus". Please help me figure out how to get Setup.exe to STOP TRYING TO INSTALL X. Setup.exe won't stop trying to snag unnecessary components. What file(s) to I have to edit manually to make this happen? What can I manually delete? It's a remote system, so I can't uninstall Cygwin without losing control. Little help? On Fri, 07 May 2004 19:16:54 -0700, "Lex Ein" <[EMAIL PROTECTED]> said: > If there exists a sensible method for trimming the bulk of an existing > Cygwin installation on a running disk-limited REMOTE system accessible > only via ssh, I'd love to know it. I've completely lost patience. > > On a remote system, I've been trying to uninstall large chunks of Cygwin > (x, db). Using Setup.exe to do this is like playing Whack-a-Mole, and is > extremely frustrating. > > The "Keep | Reinstall | Source | Version1 | Version2...| Uninstall" > click-to-rotate control forces dependancies both far and near while I'm > trying to _reach_ Uninstall. Uninstall LEAVES THOSE DEPENDANCIES > ACTIVATED. > > Without a way to select Uninstall without clocking through all the other > dependancy activators, it's impossible to remove features and all their > dependancies stickily. > > In fact, the very process of trying to do this piece by piece has > resulted in masses of other crap being installed which I don't need. > It's rather disturbing, as I'm running out of space on the remote system. > > L > > flames->dev/null > > -- > http://www.fastmail.fm - Choose from over 50 domains or use your own > > -- > 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/ > -- http://www.fastmail.fm - Choose from over 50 domains or use your own -- 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/
Using Setup.exe to uninstall - bogus
If there exists a sensible method for trimming the bulk of an existing Cygwin installation on a running disk-limited REMOTE system accessible only via ssh, I'd love to know it. I've completely lost patience. On a remote system, I've been trying to uninstall large chunks of Cygwin (x, db). Using Setup.exe to do this is like playing Whack-a-Mole, and is extremely frustrating. The "Keep | Reinstall | Source | Version1 | Version2...| Uninstall" click-to-rotate control forces dependancies both far and near while I'm trying to _reach_ Uninstall. Uninstall LEAVES THOSE DEPENDANCIES ACTIVATED. Without a way to select Uninstall without clocking through all the other dependancy activators, it's impossible to remove features and all their dependancies stickily. In fact, the very process of trying to do this piece by piece has resulted in masses of other crap being installed which I don't need. It's rather disturbing, as I'm running out of space on the remote system. L flames->dev/null -- http://www.fastmail.fm - Choose from over 50 domains or use your own -- 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/
