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:message-id:from:to:subject:references
	:in-reply-to:content-type; q=dns; s=default; b=OVM5VJnkmD2mXP7Yo
	6TYmcAAABLd8GtW6X8pDGgq0PBTIw6qo9DFa+z79rgNHzo4yfkj1jY+TWDm4pvkY
	ncBK66xZ3gDf6+Ok8ZufuZmhq8bHLjQaCok6zHC/2scrPCUQdkMIGeR2RchmBok/
	XtxBozDav9jgcL+pe9e865fuX0=
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:message-id:from:to:subject:references
	:in-reply-to:content-type; s=default; bh=43+FTXvObp1aZO63VAizEZc
	p130=; b=xwRlFqUt8Yw0XSn7fUaM1TBhfmGoZJ5vCJ1MP1KPYgd3S9E8z+/SFU4
	Pf7xz0BMoa8R1aigs9T8LFWK8mBm9EM63Nir+Cai8EBeGTsTLFObu/pZw6o57O06
	K3gSLTyslDllSbYxRmrzKhhJuJNo7CgG8qTpsh/g3wt05fsYFYvU=
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=-2.4 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy=uninstalled, *****, H*F:D*nl
X-HELO: lb3-smtp-cloud3.xs4all.net
Date: Fri, 26 May 2017 19:06:36 +0200
Message-ID: <7d631cf2046da7baf573707ad337efd2@smtp-cloud3.xs4all.net>
From: Houder <houder AT xs4all DOT nl>
To: cygwin AT cygwin DOT com
Subject: Re: Clueless! sshd ONLY fails at system startup (XP/SP3) -- FOLLOWUP
References: <20c9be1102ad4e7590b837c068d3f0ba AT xs4all DOT nl> <ca928265410362b988dd9d6f8f2332c1 AT xs4all DOT nl> <d4460ebed35e9764c07d4e04f44b589b AT xs4all DOT nl> <280fdefd-c77c-1b75-7191-af541c8c781e AT SystematicSw DOT ab DOT ca> <25b9ec2d5d45d2788af33ed35a7c9af2 AT xs4all DOT nl> <f025d47b-9c82-fb92-b336-254675a2c068 AT gmail DOT com>
In-Reply-to: <f025d47b-9c82-fb92-b336-254675a2c068@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=fixed
User-Agent: mua.awk 0.99

On Fri, 26 May 2017 10:40:20, cyg Simple wrote:
> On 5/26/2017 4:17 AM, Houder wrote:
> 
> Are you positive your XP system, even though beyond EOSL didn't get auto
> updated because of RANSOMEWARE upgrades[1][2]?  Perhaps this was the
> source of your problems.

I applied the patch myself ... (and I do not believe that the patch was the
cause of the problem - given the fact, that the problem disappeared after I
had UNinstalled the F-Secure *****)

Henri

> [1]
> https://www.theverge.com/2017/5/13/15635006/microsoft-windows-xp-security-patch-wannacry-ransomware-attack
> [2]
> https://redmondmag.com/articles/2017/05/15/microsoft-releases-windows-ransomware-patch.aspx


--
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