At 01:29 AM 7/21/2005, you wrote:
>On Wed, 20 Jul 2005, Eli Barzilay wrote:
>
>> On Jul 20, Larry Hall wrote:
>> > At 03:10 AM 7/20/2005, you wrote:
>> > >
>> > >It did run into permission problems -- the /etc/ssh* keys were not
>> > >readable. Looks like chowning them didn't help at all. Finally
On Wed, 20 Jul 2005, Eli Barzilay wrote:
> On Jul 20, Larry Hall wrote:
> > At 03:10 AM 7/20/2005, you wrote:
> > >
> > >It did run into permission problems -- the /etc/ssh* keys were not
> > >readable. Looks like chowning them didn't help at all. Finally, I
> > >resorted to removeing them and r
At 10:58 PM 7/20/2005, you wrote:
>> I'm not sure what's holding you back now...
>
>Mainly the fact that I'm fine with starting my own sshd, even if its
>manual. (I'll try a quick strace.)
Actually, I meant this differently than you took it I think. I was
lamenting that I couldn't think of a re
On Jul 20, Larry Hall wrote:
> At 03:10 AM 7/20/2005, you wrote:
> >
> >It did run into permission problems -- the /etc/ssh* keys were not
> >readable. Looks like chowning them didn't help at all. Finally, I
> >resorted to removeing them and re-runnning ssh-host-config to
> >regenerate. Now runn
At 03:10 AM 7/20/2005, you wrote:
>On Jul 19, Larry Hall wrote:
>> At 02:32 AM 7/19/2005, you wrote:
>> >I did the additional chown, and my username is a mamber of the
>> >administrators group, but I'm still getting the same error (1053).
>> >Is there any log file or something that will hint at the
On Jul 19, Larry Hall wrote:
> At 02:32 AM 7/19/2005, you wrote:
> >I did the additional chown, and my username is a mamber of the
> >administrators group, but I'm still getting the same error (1053).
> >Is there any log file or something that will hint at the problem?
>
> Only /var/log/sshd.log b
At 02:32 AM 7/19/2005, you wrote:
>I did the additional chown, and my username is a mamber of the
>administrators group, but I'm still getting the same error (1053). Is
>there any log file or something that will hint at the problem?
Only /var/log/sshd.log but this really only provides informat
On Jul 18, Larry Hall wrote:
> At 12:23 AM 7/18/2005, you wrote:
> >On Jul 17, Larry Hall wrote:
> >> [...]
> >> You'll need to change some permissions. Try this:
> >>
> >> chown eli /etc/ssh*
> >> chown eli /var/log/sshd.log
> >>
> >> Then start the service:
> >>
> >> cygrunsrv --start sshd
>
At 12:23 AM 7/18/2005, you wrote:
>On Jul 17, Larry Hall wrote:
>> At 08:58 PM 7/17/2005, Eli wrote:
>> >
>> >When I try that (after shutting down the existing sshd with
>> >cygrunsrv -E) I get errors when trying to access private key files
>> >in /etc. How do I make them accessible to my user? M
On Jul 17, Larry Hall wrote:
> At 08:58 PM 7/17/2005, Eli wrote:
> >
> >When I try that (after shutting down the existing sshd with
> >cygrunsrv -E) I get errors when trying to access private key files
> >in /etc. How do I make them accessible to my user? Maybe there is
> >some simple way to make
At 08:58 PM 7/17/2005, Eli wrote:
>On Jul 10, Larry Hall wrote:
>> [...]
>> Then there's always running sshd as the user you want to run the
>> builds. This should eliminate any authentication problems but it
>> does limit the usefulness of sshd since it's now affectively a
>> one-person service,
On Jul 10, Larry Hall wrote:
> [...]
> Then there's always running sshd as the user you want to run the
> builds. This should eliminate any authentication problems but it
> does limit the usefulness of sshd since it's now affectively a
> one-person service, though you could certainly run two sshds
On Mon, 11 Jul 2005, Eli Barzilay wrote:
> (BTW, is there cron-like functionality that can behave as different
> users? Something that can be used to start sshd if the macine
> reboots.)
Huh? I thought cygrunsrv did that by default, unless one specified "-t
manual"...
> > But I think it's fair
On Jul 10, Larry Hall wrote:
>
> Eli, please send all replies to the list only. That is why I set my
> "Reply-To" to point to the Cygwin list. There's no need to force a
> reply to me directly as I read the list as much as I do my personal
> email. Sometimes more. ;-)
Sorry, that was unintende
On Sun, 10 Jul 2005, Eli Barzilay wrote:
> On Jul 9, Larry Hall wrote:
> > When running through sshd, you're running via a service.
> > Authenticating without a password means that Windows won't
> > authenticate as the user you are. The reverse is also true. So it's
> > possible that VS needs ac
At 08:15 PM 7/10/2005, you wrote:
>On Jul 9, Larry Hall wrote:
>> When running through sshd, you're running via a service. Authenticating
>> without a password means that Windows won't authenticate as the user you are.
>> The reverse is also true. So it's possible that VS needs access to some
On Jul 9, Larry Hall wrote:
> When running through sshd, you're running via a service. Authenticating
> without a password means that Windows won't authenticate as the user you are.
> The reverse is also true. So it's possible that VS needs access to some
> information that it doesn't have acc
On Tue July 5 2005 22:59, Eli Barzilay wrote:
> On Jul 5, Larry Hall wrote:
> > At 08:45 PM 7/5/2005, you wrote:
> > >(If this is not the right place for this, please direct me.)
> > >
> > >I have recently updated an old Windows setup, including a new cygwing
> > >installation. We use this machin
Original Message
>From: Eli Barzilay
>Sent: 06 July 2005 03:59
> On Jul 5, Larry Hall wrote:
>> Sounds to me like you're trying to access a network drive which
>> requires authentication but that's just a WAG.
> Don't know what a "WAG" is, and the above faq entry didn't help...
http:
On Jul 5, Larry Hall wrote:
> At 08:45 PM 7/5/2005, you wrote:
> >(If this is not the right place for this, please direct me.)
> >
> >I have recently updated an old Windows setup, including a new cygwing
> >installation. We use this machine for nightly builds, using a shell
> >script that connect
At 08:45 PM 7/5/2005, you wrote:
>(If this is not the right place for this, please direct me.)
>
>I have recently updated an old Windows setup, including a new cygwing
>installation. We use this machine for nightly builds, using a shell
>script that connects to multiple machines and runs the build
(If this is not the right place for this, please direct me.)
I have recently updated an old Windows setup, including a new cygwing
installation. We use this machine for nightly builds, using a shell
script that connects to multiple machines and runs the builds
(DevStudio in the Windows case). Wi
Robert Schmidt wrote:
OK, here's some more info from the hanging unison over ssh on 1.5.11.
> ...
Sorry, forgot the cygcheck -s -v -r output.
Cheers,
Rob
Cygwin Configuration Diagnostics
Current System Time: Wed Sep 15 09:01:32 2004
Windows XP Professional Ver 5.1 Build 2600 Service Pack 2
Path:
[snip]
> I'll restrain myself in the future, and will keep learning
> from the list how to be helpful without being shot down.
Wow, did YOU stumble into the wrong mailing list!
--
Gary R. Van Sickle
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: ht
OK, here's some more info from the hanging unison over ssh on 1.5.11.
I've attached the last part of an strace, taken from after ssh reads the
RSA key. At the end of the log, ssh just waits. I've kept the full
logs from both 1.5.10 and 1.5.11 if it can be helpful.
And thanks, Dave, for the refere
Igor Pechtchanski cs.nyu.edu> writes:
>
> Hmm, what does "ssh -nx user host cvs -tn server" print?
> Igor
It comes back immediately (does not hang) and with no output:
$ ssh -nx [EMAIL PROTECTED] cvs -tn server >out 2>err
$ ls -l out err
-rw-rw-rw-1 chcobb Domain_U0 Sep 14
Dave Korn artimi.com> writes:
>
> I suggest you should use "od" to see if there's a CR-without-a-LF in the
> middle causing two lines of messages to overprint each other.
>
> cheers,
> DaveK
Yes, there was an embedded ^M:
cvs status: warning: unrecognized response `Warning: No xa
On Tue, 14 Sep 2004, Christopher Cobb wrote:
> Igor Pechtchanski cs.nyu.edu> writes:
>
> > Probably an stdout buffering artifact. Try
> >
> > cvs status myFile.txt >out 2>err
> >
> > and examine the out and err files.
> >
> > Did you try setting CVS_RSH to "/usr/bin/ssh -x"?
> > Igor
>
> $ c
> -Original Message-
> From: cygwin-owner On Behalf Of Christopher Cobb
> Sent: 14 September 2004 17:57
> Igor Pechtchanski writes:
> >
> > Probably an stdout buffering artifact. Try
> >
> > cvs status myFile.txt >out 2>err
> >
> > and examine the out and err files.
> >
> > Did you tr
Igor Pechtchanski cs.nyu.edu> writes:
>
> Probably an stdout buffering artifact. Try
>
> cvs status myFile.txt >out 2>err
>
> and examine the out and err files.
>
> Did you try setting CVS_RSH to "/usr/bin/ssh -x"?
> Igor
$ cat out
(nothing)
$ cat err
cvs status: warning: unrecognized
On Tue, 14 Sep 2004, Christopher Cobb wrote:
> Igor Pechtchanski cs.nyu.edu> writes:
> >
> > > authentication dat' from cvs servering.
> > ^^^!!!
> > > (never returns)
> >
> > I'm a bit concerned about the "ing" above (marked with "!!!"). Looks like
> > you have
Igor Pechtchanski cs.nyu.edu> writes:
>
> > authentication dat' from cvs servering.
> ^^^!!!
> > (never returns)
>
> I'm a bit concerned about the "ing" above (marked with "!!!"). Looks like
> you have intermixed the outputs of programs somehow...
>
Facinating
Robert Schmidt broadpark.no> writes:
>
> On the unison.general mailing list, Mark Rogers reports that replacing
> the cygwin1.dll with version 1.5.10 makes unison over ssh work again.
>
I am using 1.5.11 and I can confirm that reverting to 1.5.10 makes my cvs/ssh
problems go
My XP machine at work was just upgraded to SP2. Now I'm having problems
accessing a cvs repository on a linux box over ssh. Everything was working
fine until this SP2 upgrade.
I'm doing CVS over SSH a lot, and what can i say: it just works, and
i've got SP2 and Cygwin 1.5.11 installed too.
--
> -Original Message-
> From: cygwin-owner On Behalf Of Robert Schmidt
> Sent: 14 September 2004 16:15
> I don't quite understand the sarcasm here.
http://cygwin.com/acronyms#WJM
OOO
OO OO
OO OO
OO
OO OO
OO OO
OOO
[nb. big a
Christopher Faylor wrote:
On Tue, Sep 14, 2004 at 04:37:55PM +0200, Robert Schmidt wrote:
On the unison.general mailing list, Mark Rogers reports that replacing
the cygwin1.dll with version 1.5.10 makes unison over ssh work again.
So, I assume that replacing the DLL with version B20 would really
su
On Tue, 14 Sep 2004, Christopher Cobb wrote:
> My XP machine at work was just upgraded to SP2. Now I'm having problems
> accessing a cvs repository on a linux box over ssh. Everything was working
> fine until this SP2 upgrade.
>
> I can access the cvs host via ssh normally (although in a possibl
Corinna Vinschen wrote:
On Sep 14 16:37, Robert Schmidt wrote:
A quick follow-up:
On the unison.general mailing list, Mark Rogers reports that replacing
the cygwin1.dll with version 1.5.10 makes unison over ssh work again.
I also tried it (temporarily, of course), and can confirm that it works.
So
On Tue, Sep 14, 2004 at 04:37:55PM +0200, Robert Schmidt wrote:
>A quick follow-up:
>
>On the unison.general mailing list, Mark Rogers reports that replacing
>the cygwin1.dll with version 1.5.10 makes unison over ssh work again.
So, I assume that replacing the DLL with version B20 would really
sup
On Sep 14 16:37, Robert Schmidt wrote:
> A quick follow-up:
>
> On the unison.general mailing list, Mark Rogers reports that replacing
> the cygwin1.dll with version 1.5.10 makes unison over ssh work again.
>
> I also tried it (temporarily, of course), and can confirm that it works.
>
> So SP2 d
A quick follow-up:
On the unison.general mailing list, Mark Rogers reports that replacing
the cygwin1.dll with version 1.5.10 makes unison over ssh work again.
I also tried it (temporarily, of course), and can confirm that it works.
So SP2 does seem to break something in cygwin 1.5.11, as installin
I get similar symptoms with unison over ssh:
It worked great before SP2 (i.e. 2 hours ago).
After I installed SP2 on the client, unison/ssh just hangs.
The server has been running SP2 for over a week.
Any normal ssh sessions work fine. I'm also using ssh to forward the
IMAP port (143) to my server
My XP machine at work was just upgraded to SP2. Now I'm having problems
accessing a cvs repository on a linux box over ssh. Everything was working
fine until this SP2 upgrade.
I can access the cvs host via ssh normally (although in a possibly related
matter, ssh sometimes seems to be a characte
43 matches
Mail list logo
