Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com Date: Thu, 18 May 2000 20:20:07 +0400 From: Egor Duda X-Mailer: The Bat! (v1.41) Reply-To: Egor Duda Organization: DEO X-Priority: 3 (Normal) Message-ID: <16847.000518@logos-m.ru> To: Olivier Jacquemin CC: "'cygwin AT sourceware DOT cygnus DOT com'" Subject: Re[2]: Login incorrect In-reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi! Thursday, 18 May, 2000 Olivier Jacquemin Olivier DOT Jacquemin AT DialogSystems DOT be wrote: OJ> I'm afraid everything is set as it should... and still this "Login OJ> incorrect"... OJ> Here is a small session, just after starting Cygwin from the shortcut (so I OJ> did not set anything manually before and the CYGWIN environment variable was OJ> set in the NT environment before startup). I swear I entered my correct OJ> password after the "Password:" promt :-) OJ> bash-2.03$ echo $CYGWIN OJ> ntsec binmode tty OJ> bash-2.03$ mkpasswd -d > /etc/passwd OJ> bash-2.03$ mkgroup -d > /etc/group OJ> bash-2.03$ cat /etc/passwd | grep OJA OJ> OJA::1013:513:Jacquemin OJ> Olivier,S-1-5-21-154406374-876364143-99485923-1013::/bin/sh OJ> bash-2.03$ login OJ> login: OJA OJ> Password: OJ> Login incorrect OJ> login: Login timed out after 300 seconds Quote from http://www.lexa.ru/sos/ ------------------8<----------------- The account's rights required are "Act as part of operation system" (SE_TCB_NAME) for LogonUser call, and "Replace a process level token" (SE_ASSIGNPRIMARYTOKEN_NAME) and "Increase quotas" (SE_INCREASE_QUOTA_NAME) for CreateProcessAsUser call. Note: "Administrator" account have no all neccessary rights by default. Relogin if you added these rights to the account you are currently logged in. ------------------8<----------------- Corinna will correct me if i'm wrong, but i think login.exe still uses "LogonUser" and "CreateProcessAsUser" calls. So you probably should enable aforementioned access rights for the account from which you trying to run 'login'. Egor. mailto:deo AT logos-m DOT ru ICQ 5165414 FidoNet 2:5020/496.19 -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com