Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-Id: <3.0.5.32.20030608233329.0080b100@incoming.verizon.net> X-Sender: vze1u1tg AT incoming DOT verizon DOT net Date: Sun, 08 Jun 2003 23:33:29 -0400 To: cygwin AT cygwin DOT com From: "Pierre A. Humblet" Subject: Re: exim - failed to read delivery status In-Reply-To: <19232840890.20030609065209@hotbox.ru> References: <3 DOT 0 DOT 5 DOT 32 DOT 20030608220432 DOT 007f9c90 AT incoming DOT verizon DOT net> <3 DOT 0 DOT 5 DOT 32 DOT 20030608201221 DOT 0080d8b0 AT incoming DOT verizon DOT net> <3 DOT 0 DOT 5 DOT 32 DOT 20030608201221 DOT 0080d8b0 AT incoming DOT verizon DOT net> <3 DOT 0 DOT 5 DOT 32 DOT 20030608220432 DOT 007f9c90 AT incoming DOT verizon DOT net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" At 06:52 AM 6/9/2003 +0400, CoolCold wrote: Hello CoolCold >>>PAH> Can you telnet and/or ssh into the box? >>>sshd works > >PAH> What about telnet (inetd)? How do you know sshd works? Can you telnet into the box as a normal user? >PAH> Edit the /etc/passwd file. The second field is the password. >SYSTEM::18:544:,S-1-5-18:/:/bin/bash is it ok? Yes. >PAH> Then telnet localhost. >PAH> You should not have to provide a password for SYSTEM >it says : >Password: >Login incorrect >login: system >Switching to user system failed! This starts well. login recognizes that SYSTEM exists and has no password. The error comes from these lines in login.c if (seteuid(pwd->pw_uid)) { printf("Switching to user %s failed!\n", username); So telnetd has the same problem as exim, it can't setuid, even though in this case the setuid should be a noop. There is something wrong with your installation. What version of Windows do you have? Does "ps -a" show that inetd has uid 18? Does uid 18 appear several times in /etc/passwd ? >ssh doesn't accept connection to,but AllowRootLogin=yes,and >AllowBlankPassword=yes... Same problem, probably. >In windows' event log I can see: >Event Type: Success Audit >Event Source: Security >Event Category: Privilege Use >Event ID: 576 >Date: 6/9/2003 >Time: 6:46:18 AM >User: WORKSTATION\coolcold >Computer: WORKSTATION >Description: >Special privileges assigned to new logon: > User Name: coolcold > Domain: WORKSTATION > Logon ID: (0x0,0x6526FC) > Privileges: SeChangeNotifyPrivilege > SeBackupPrivilege > SeRestorePrivilege > SeDebugPrivilege That looks normal and not related to the problem. Wait. What happened at 6:46 am? Did you login at the console or did you do something else? Is there anything in the application log? Is there anything interesting in /var/log/xxx.log ? Pierre (who sees it's 11:30 PM) -- 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/