Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Wed, 26 Feb 2003 08:39:44 -0500
From: Jason Tishler <jason AT tishler DOT net>
Subject: Re: exim 4.12-3 winsock problem (was Re: 1.3.21)
In-reply-to: <3E5BE69D.5CDC7510@ieee.org>
To: "Pierre A. Humblet" <Pierre DOT Humblet AT ieee DOT org>
Cc: cygwin AT cygwin DOT com
Mail-followup-to: "Pierre A. Humblet" <Pierre DOT Humblet AT ieee DOT org>,
 cygwin AT cygwin DOT com
Message-id: <20030226133944.GG772@tishler.net>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Content-disposition: inline
User-Agent: Mutt/1.4i
References: <20030225114401 DOT GA1876 AT tishler DOT net> <3E5B8599 DOT B853407A AT ieee DOT org>
 <20030225170155 DOT GI1876 AT tishler DOT net> <3E5BAB43 DOT 94FFA9ED AT ieee DOT org>
 <20030225202123 DOT GN1876 AT tishler DOT net> <3E5BD593 DOT 6892CA19 AT ieee DOT org>
 <20030225210138 DOT GO1876 AT tishler DOT net> <3E5BDDC7 DOT 6E3A44D7 AT ieee DOT org>
 <20030225214640 DOT GP1876 AT tishler DOT net> <3E5BE69D DOT 5CDC7510 AT ieee DOT org>

Pierre,

On Tue, Feb 25, 2003 at 06:29:01PM -0500, Andre Bleau wrote:
> Sorry to jump in now. A good way to resolve that kind of problem is
> auditing. As administrator, enable auditing. With regedt32, enable
> auditing on selected keys and subkeys for read or write failure, as
> required. You will find results in event viewer, in the security log.

Andre, no need to apologize -- the above is a very good suggestion.

This problem has turned into great learning experience.  It's ironic how
the most painful problems usually yield the greatest insights, knowledge,
etc.

On Tue, Feb 25, 2003 at 04:56:45PM -0500, Pierre A. Humblet wrote:
> Jason Tishler wrote:
> > Do you want me further isolate?  If so, any hints?
> 
> Yes, please! Your guess is as good as mine. Anything having to do with
> networking?

Using good old fashioned strings and Andre's suggestion I have isolated
the registry keys requiring read access for Everyone (which did not
already have it) to the following:

    1. HKLM\System\CurrentControlSet\Services\Winsock\Parameters
    2. HKLM\System\CurrentControlSet\Services\WinSock2\Parameters

I guess that the above is no great surprise.

BTW, not having read access for Everyone on the above keys causes the
following exim error messages:

    1. IPv4 socket creation failed: Operation not permitted
    2. cannot find smtp/tcp service when starting daemon

respectively.

Jason

-- 
PGP/GPG Key: http://www.tishler.net/jason/pubkey.asc or key servers
Fingerprint: 7A73 1405 7F2B E669 C19D  8784 1AFD E4CC ECF4 8EF6

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/