DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org E52AB3858D32
Message-ID: <4cf463fc-38a2-0dd2-7bea-c7293abbd754@Shaw.ca>
Date: Sun, 22 Jan 2023 12:24:36 -0700
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101
 Thunderbird/102.6.1
Subject: Re: observation: masses of requests to LDAP
Content-Language: en-CA
To: cygwin@cygwin.com
References: <ae73845c-b970-37ab-f429-65b15cf8540c@tu-dortmund.de>
Organization: Inglis
In-Reply-To: <ae73845c-b970-37ab-f429-65b15cf8540c@tu-dortmund.de>
Precedence: list
From: Brian Inglis via Cygwin <cygwin@cygwin.com>
Reply-To: cygwin@cygwin.com
Cc: Brian Inglis <Brian.Inglis@Shaw.ca>,
        Tobias Wendorff <tobias.wendorff@tu-dortmund.de>
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Errors-To: cygwin-bounces+archive-cygwin=delorie.com@cygwin.com
Sender: "Cygwin" <cygwin-bounces+archive-cygwin=delorie.com@cygwin.com>
Content-Transfer-Encoding: 8bit

On 2023-01-22 07:32, Tobias Wendorff via Cygwin wrote:
> our IT department has informed me that masses of requests are being sent from my 
> computer to our two LDAP servers on port 389. After a detailed investigation, 
> the problem could be clearly traced back to "cygwin".

That is required for Cygwin to emulate POSIX permissions and ACLs: see security 
and domain info in:

/usr/share/doc/cygwin-doc/html/cygwin-ug-net/cygwin-ug-net.html
/usr/share/doc/cygwin-doc/cygwin-ug-net.pdf

or the equivalant online docs:

https://cygwin.com/cygwin-ug-net.html
https://cygwin.com/cygwin-ug-net/cygwin-ug-net.html
https://cygwin.com/cygwin-ug-net/cygwin-ug-net.pdf
https://cygwin.com/faq.html

Your IT folks could contact peers at Aachen, Bochum, Dresden, Esslingen, FAU who 
provide Cygwin mirrors, probably use it in courses, and have experience with it; 
see:
	https://cygwin.com/mirrors.html

> Firewall logs show that about any tool, even base tools "sort" or "less", 
> initiates a request to port 389 on our LDAP servers.

Each process needs access to your credentials, groups, and memberships, and 
pulls them for domain accounts on domain members.

> Sorry, I am _not_ going to release "cygcheck.out" to public, since it contains 
> sensitive information about the domain and its groups and memberships.

It is acceptable to anonymize or summarize information in cygcheck output.
In this case, counts of ids, groups, and memberships might help.

> Even after reinstalling cygwin from another server, the problem still appears. 
> Could it be that this is part of an attack?

Definitely not, this is normal behaviour.

Your first step should be to run cygserver to cache SAM and AD info on each 
system using cygwin on domain members.

Your second step should be to review /etc/nsswitch.conf settings for searching 
and possibly set:

	db_enum: cache local primary builtin

or maybe:

	db_enum: cache local primary alltrusted

or if connecting from home maybe:

	db_enum: cache local primary domain.tld

Check the mainling list archives for previous posts about domain settings.

-- 
Take care. Thanks, Brian Inglis			Calgary, Alberta, Canada

La perfection est atteinte			Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter	not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer	but when there is no more to cut
			-- Antoine de Saint-Exupéry

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