There was a typo in earlier mail.
Its "nontsec" and not "ntnosec".
-Prasad
--- Prasad Dabak <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I hear you and I completely agree with you. I am
> looking for a very short term solution right now and
> will soon upgrade to the latest version.
>
> BTW, settin
Hello,
I hear you and I completely agree with you. I am
looking for a very short term solution right now and
will soon upgrade to the latest version.
BTW, setting cygwin environment variable to "ntnosec"
also solves the issue (even if I keep StrictModes to
Yes)
Thanks.
-Prasad
--- Corinna Vinsc
On Fri, Jul 11, 2003 at 05:26:12AM -0700, Prasad Dabak wrote:
> So now, I have openssh 2.5.2p2 and cygwin 1.3.22 on
^^^
Again, 2.5.2p2 has a bunch of known security problems. These are
not Cygwin specific but generic flaws. It's not secure to run a
publically accessib
Hello,
Thank you very much for all your help. I really
appreciate that.
I found a workaround, by setting the StrictModes
setting in \etc\sshd_config to "No". As you said
earlier, new cygwin is more strict in terms of
permissions and ownership.
So now, I have openssh 2.5.2p2 and cygwin 1.3.22 on
On Fri, Jul 11, 2003 at 04:32:43AM -0700, Prasad Dabak wrote:
> 1. I am using openssh 2.5.2p2 and cygwin 1.3.1 using
> passwordless authentication with sshd running in
> SYSTEM context. I have been using this combination for
> years on Windows 2000 and it works fine.
Just as a side note: 2.5.2 ha
Hello,
I am sorry, if I have lead to further confusions. Let
me explain everything all over again
1. I am using openssh 2.5.2p2 and cygwin 1.3.1 using
passwordless authentication with sshd running in
SYSTEM context. I have been using this combination for
years on Windows 2000 and it works fine.
On Fri, Jul 11, 2003 at 03:39:05AM -0700, Prasad Dabak wrote:
> Hello,
>
> Thanks for your help.
>
> I am sorry to bug you again.
>
> So, does this mean, that, I can not run sshd with
> passwordless authentication in SYSTEM context even if
> I switch to the latest version of openssh?
In your p
Hello,
Thanks for your help.
I am sorry to bug you again.
So, does this mean, that, I can not run sshd with
passwordless authentication in SYSTEM context even if
I switch to the latest version of openssh?
Further, the question is, if I use old version of
cygwin, it is not giving me the permiss
On Fri, Jul 11, 2003 at 02:30:42AM -0700, Prasad Dabak wrote:
> Hello,
>
> Yes, sshd is running as service under SYSTEM account.
I'm speechless.
> Are there any issues in doing this with the latest
> cygwin?
Well, passwordless authentication shouldn't work at all under 2003
when running as serv
Hello,
Yes, sshd is running as service under SYSTEM account.
Are there any issues in doing this with the latest
cygwin?
I know, that, Cygwin 1.3.22 comes with OpenSSH
3.6.1p2. However, due to other reasons, I don't want
to upgrade to new openSSH as far as possible.
Thanks.
-Prasad
--- Corinna V
On Thu, Jul 10, 2003 at 11:36:44PM -0700, Prasad Dabak wrote:
> Hello,
>
> I am using public key authentication. If I use the old
> version of cygwin (1.3.1), I am able to ssh on to the
> box.
Is sshd running as service under SYSTEM account?
> Hence, I think, that the issue is not related to
> W
Hello,
I am using public key authentication. If I use the old
version of cygwin (1.3.1), I am able to ssh on to the
box. However, it fails with cygwin heap error while
spawning bash. But at least it does not give me
authentication error.
c:\bin\bash.exe: *** Couldn't reserve space for
cygwin's he
On Thu, Jul 10, 2003 at 07:18:19AM -0700, Prasad Dabak wrote:
> I am using cygwin 1.3.1 on Windows 2003. While
> executing certain commands, I am getting the following
> error. This happens especially, when, one command is
> internally spawning another command
> [...]
> breaks openssh 2.5.2p2-3 ser
sible.
-Mark
- Original Message -
From: "Prasad Dabak" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, July 10, 2003 10:44 AM
Subject: Re: cygwin on Windows 2003...
> Hello,
>
> Its not a typo. I am indeed using cygwin 1.3.1. As I
> mentioned i
Hello,
Its not a typo. I am indeed using cygwin 1.3.1. As I
mentioned in my original mail, upgrading to latest
version 1.3.22 does solve the heap problem. However,
it creates problems for openssh server that I am
running on the same box.
Sorry for sending it to cygwin-apps. I will keep it in
mind
On Thu, 10 Jul 2003, Prasad Dabak wrote:
> Hello,
>
> I am using cygwin 1.3.1 on Windows 2003. While
> executing certain commands, I am getting the following
> error. This happens especially, when, one command is
> internally spawning another command
Just out of curiousity, is the above version a
16 matches
Mail list logo
