Larry Hall (Cygwin) wrote:
> Brian Kasper wrote:
>> I'm not sure why it worked, but it does. I performed at least one
>> update of Cygwin recently, so it's possible I have a newer version of
>> something.
>
> You mean you're not sure why it didn'
I wiped my sshd install based upon Corinna's instructions and re-ran
ssh-host-config. Short answer: it worked, and I didn't experience the
privilege problems with the sshd_server user.
For the sake of completeness, I'll include a slightly longer answer.
Here's the exact operating system I'm run
Andrew DeFaria wrote:
> I do recall having something similarly wrong with the ssh-host-config
> when I was working at a client's site a while back. Something, IIRC, to
> do with domain policies overriding local policies such that when trying
> to ssh into the server I was receiving similar behavior
Corinna Vinschen wrote:
>> I was seeing errors in the system event log, but unfortunately I'm not
>> very experienced with Windows security, so I wasn't understanding what I
>> was seeing.
>
> When you set up a server it makes a lot of sense trying to understand
> Windows security. Besides of boo
I've been having a hard time getting sshd to accept logins on a Windows
XP 2003 x64 box. The problems ranged from the error mentioned in the
subject line ("/bin/bash: permission denied" appearing during logins) to
silent failures during password authentication, during which the ssh
connection woul
Thanks for pointing that out -- I'm really not very conversant with
Windows security.
While logged in as Administrator, I tried adding sshd_server to the list
of users with the "Act as part of the operating system" privilege
(SeTcbPrivilege), but for some reason on my system both the "Add User
Thanks for responding, Corinna. I obviously wasn't clear in my original
post -- ssh login attempts to my Win2003 x64 system running Cygwin sshd
as a service always fail, which is why I tried running sshd from the
command prompt as a test.
As far as I know, my Cygwin installation is completely up
I've been having terrible problems getting Cygwin ssh/sshd to work under
the x64 version of WinXP 2003 SP1. The basic symptom has been that if I
ran sshd as a service, I was unable to run any executables during the
ssh login procedure. This included bash.exe, so my attempts to ssh into
localh
Thanks, the lack of the sshd_server user was the problem -- it's
possible I deleted it accidentally after running ssh-host-config, though
I *thought* I deleted that user and then ran the script, but I was
never asked if I wanted to create the user. Hmm
Anyway, thanks for the help. Much
I am *still* having problems getting ssh and sshd to work under WinXP
2003 x64. I'm no longer seeing "error 1062" messages, but as of today
(after I ran setup.exe to update my Cygwin install), whenever I try to
ssh to localhost I immediately saw this message:
Connection closed by 127.0.0.1
I
In complete frustration, I wiped my entire Cygwin install and
re-downloaded and -installed everything. Then, on a whim, I logged in
as the actual "Administrator" account on my box (instead of my account,
which *is* a member of the Administrators group) and configured sshd in
a bash shell by is
g the
whole issue of permissions in WinXP problematic.
Any other thoughts?
-B
Dave Korn wrote:
On 14 November 2006 18:30, Brian Kasper wrote:
Here's the text of my most recent login attempt:
>kasper 509 $ ssh localhost
>[EMAIL PROTECTED]'s password:
>Warning: No xau
Hoping that the latest release of openssh would fix the problem I'm
having starting sshd as a service, I updated my Cygwin install to Ms.
Vinschen's latest release, 4.5p1-1. I then re-ran ssh-host-config.
Unfortunately, I'm still unable to start sshd as a service, either with
or without privilege
13 matches
Mail list logo
