X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=kqm+XGR5lENFldvhaCx0pzxPOA813qtSG6Z3VadR0ffIa+6O/lCAR
	ttoPCSEBLfsNjWzjz300+nizi4+PlhvEi+SGR3us7PD1UpQ+qZv+EeSE18JG2+JT
	za5THQc6WZjLo/okeUFsWyxvifcduKQ/65Jjg/vp36ZalouLE7H+/s=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; s=default;
	bh=Dw/gQ6eNn+qQfVCnshmcXVD1p0Q=; b=u/iQeMxdiCdl6oXTbz44dapSPE7M
	68lZhDjudF6xdPLN3LfgW73/1r4cgVHTVpmPj68IaQuPXABsJEa22c3TOimCTXrx
	aDEQzesE8dyGm8EimVtRJRrswSvmP1fUslAAMI4IHbeEJuTDsYBsmqtTe2aZI383
	VlJ3dS9Fq3kUmRo=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=-1.5 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2
X-HELO:	mho-01-ewr.mailhop.org
X-Mail-Handler:	Dyn Standard SMTP by Dyn
X-Report-Abuse-To:	abuse AT dyndns DOT com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User:	U2FsdGVkX19yO85nEP3UG4TLP799+Wqr
Date:	Wed, 23 Jul 2014 12:27:03 -0400
From:	Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: The eternal uid issue
Message-ID:	<20140723162703.GA3951@ednor.casa.cgf.cx>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<53CF6CEC DOT 6D68E485 AT boland DOT nl> <20140723091409 DOT GH27005 AT calimero DOT vinschen DOT de> <53CF9E0F DOT F596FC60 AT boland DOT nl> <1273556697 DOT 20140723200807 AT yandex DOT ru>
MIME-Version:	1.0
In-Reply-To:	<1273556697.20140723200807@yandex.ru>
User-Agent:	Mutt/1.5.20 (2009-06-14)

On Wed, Jul 23, 2014 at 08:08:07PM +0400, Andrey Repin wrote:
>Greetings, D. Boland!
>> Cygwin security will be done for in the long run. Why not make the leap and
>> show MS admins/developers how it should be done?
>
>You really think they are all idiots?... Like, really?

Sure, why not.  MS admins/developers are all idiots who are apparently
supposed to be taught by Cygwin developers who have been getting it
wrong for many years until being correct by the OP.

To the OP: If you want to start a dialog, do research and ask questions.
Don't just assume that you understand everything and can provide insight
that no one else has thought of.

cgf

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

- Raw text -