On Tue, 5 Aug 2003, Ville Herva wrote:
> On Tue, Aug 05, 2003 at 08:07:43AM -0400, you [Igor Pechtchanski] wrote:
> >
> > IIRC, the default installation of sshd as service used the event log for
> > all output, rather than /var/log/sshd.log (though I'm not too sure on this
> > one)...
>
> It certa
On Tue, Aug 05, 2003 at 11:22:58AM -0400, you [Igor Pechtchanski] wrote:
>
> Well, how about getting a SYSTEM-owned shell and checking? ;-)
I didn't think of that. Silly me.
> Make sure the SYSTEM user doesn't have any *user* mounts (by running
> "mount" from a SYSTEM-owned shell).
Spot on.
Igor Pechtchanski wrote:
On Tue, 5 Aug 2003, Ville Herva wrote:
On Mon, Aug 04, 2003 at 10:03:18PM -0400, you [Larry Hall] wrote:
I tried adding '-d' to the sshd parameters, but that doesn't help (gives
the
same error 255) - it seems to die earlier than that.
What does /var/log/sshd.log say?
On Tue, Aug 05, 2003 at 08:52:13PM +0300, you [Ville Herva] wrote:
>
> > Make sure the SYSTEM user doesn't have any *user* mounts (by running
> > "mount" from a SYSTEM-owned shell).
>
> Spot on.
>
> C: on / type system (textmode)
(...)
> Starting service as SYSTEM still fails:
(...)
> but I d
On Mon, Aug 04, 2003 at 10:03:18PM -0400, you [Larry Hall] wrote:
> >
> >I tried adding '-d' to the sshd parameters, but that doesn't help (gives
> >the
> >same error 255) - it seems to die earlier than that.
> >
>
>
> What does /var/log/sshd.log say?
It remains empty, on both servers.
Based
On Tue, Aug 05, 2003 at 08:07:43AM -0400, you [Igor Pechtchanski] wrote:
>
> IIRC, the default installation of sshd as service used the event log for
> all output, rather than /var/log/sshd.log (though I'm not too sure on this
> one)...
It certainly seems to, in the event log, there are sshd gener
On Tue, 5 Aug 2003, Ville Herva wrote:
> On Mon, Aug 04, 2003 at 10:03:18PM -0400, you [Larry Hall] wrote:
> > >
> > >I tried adding '-d' to the sshd parameters, but that doesn't help (gives
> > >the
> > >same error 255) - it seems to die earlier than that.
> > >
> >
> >
> > What does /var/log/ssh
Ville Herva wrote:
On Fri, Aug 01, 2003 at 12:11:49PM -0400, you [Larry Hall] wrote:
Please *attach* your cygcheck output next time rather than including
it in the text of your message.
Sorry.
I suggest the following two changes.
1. Remove 'ntea' from your CYGWIN environment variable.
It
On Fri, Aug 01, 2003 at 12:11:49PM -0400, you [Larry Hall] wrote:
>
> Please *attach* your cygcheck output next time rather than including
> it in the text of your message.
Sorry.
> I suggest the following two changes.
>
> 1. Remove 'ntea' from your CYGWIN environment variable.
It still say
Larry Hall wrote:
1. SYSTEM is the account that sshd runs as, not administrator.
Hmm, perhaps it's just a coincidence then that Administrator permissions
correspond with sshd permissions.
2. Only the owner of the private key files in .ssh should have
permissions
to access these files. Publi
and I have not received the error you are describing. You might
want
> > to check the value of the CYGWIN environment variable. By default ntsec
is
> > turned on but if that variable includes "nontsec" or "ntea" then that
might
> > be what is causing your pro
Ville Herva wrote:
I think I have somewhat similar problem with setting up sshd. It must be
something stupid, but this has happened to me on two separate machines. As
it happens, someone else had initially set up cygwin on both of them, so I
don't know exactly what options were used (but I assume
I think I have somewhat similar problem with setting up sshd. It must be
something stupid, but this has happened to me on two separate machines. As
it happens, someone else had initially set up cygwin on both of them, so I
don't know exactly what options were used (but I assume they are fairly
defa
m: "Larry Hall" <[EMAIL PROTECTED]>
To: "Myk Melez" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Thursday, July 31, 2003 9:40 PM
Subject: Re: Administrator lacking super-user privileges on cygwin
installation
Myk Melez wrote:
I have two machines with wha
--- Original Message -
From: "Larry Hall" <[EMAIL PROTECTED]>
To: "Myk Melez" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Thursday, July 31, 2003 9:40 PM
Subject: Re: Administrator lacking super-user privileges on cygwin
installation
> Myk Melez wrote:
&
Myk Melez wrote:
I have two machines with what look like identical cygwin installations
on them, but the Administrator account on one of them doesn't have
super-user privileges. This causes sshd not to have access to
/home/some-user/.ssh (which is restricted to only "some-user") and thus
prev
I have two machines with what look like identical cygwin installations
on them, but the Administrator account on one of them doesn't have
super-user privileges. This causes sshd not to have access to
/home/some-user/.ssh (which is restricted to only "some-user") and thus
prevents key-based aut
17 matches
Mail list logo
