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
21 matches
Mail list logo
