On Feb  7 13:44, Brian Kasper wrote:
> 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.
> [...]
> /var/log/sshd.log remains empty, but a "failure audit" event appears in
> my Security event log:
> 
>       Event Type:     Failure Audit
>       Event Source:   Security
>       Event Category: Privilege Use
>       Event ID:       577
>       Date:           2/7/2007
>       Time:           8:26:55 AM
>       User:           ABF466\sshd_server
>       Computer:       ABF466
>       Description:
>       Privileged Service Called:
>               Server:         NT Local Security Authority / Authentication 
>               Service
>               Service:                LsaRegisterLogonProcess()
>               Primary User Name:      ABF466$
>               Primary Domain: AERO-ORG
>               Primary Logon ID:       (0x0,0x3E7)
>               Client User Name:       sshd_server
>               Client Domain:  ABF466
>               Client Logon ID:        (0x0,0x14B91291)
>               Privileges:     SeTcbPrivilege

Looks like the Tcb privilege ("Act as part of the operating system")
is missing for the sshd_server user.

> I don't know how to activate output to /var/log/sshd.log -- would that
> help to diagnose this problem?

No.  You don't have to activate anything.  If output is created,
it will go to sshd.log.  There's no magic.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Reply via email to