delorie.com/archives/browse.cgi | search |
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:subject:to:references:from:message-id:date | |
:mime-version:in-reply-to:content-type | |
:content-transfer-encoding; q=dns; s=default; b=VPerCxnG4k1B42TI | |
n2VShoqiLfsi/aBynuaSd130tML78G06deAgemTyE38GrAHk/moOh+IhEdx+NXVn | |
Fz8AcDagrYNo9wEJeKjCBq1F52lnKKr/KOHJzArHO/XhIw5dG+1tHDaA5X2aQGjx | |
2ZmwvgKBWgeHcEk3MXQGVIBHacY= | |
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:subject:to:references:from:message-id:date | |
:mime-version:in-reply-to:content-type | |
:content-transfer-encoding; s=default; bh=h5MfV/nHOzZdF7oUQWLTFR | |
PPtCk=; b=cwK2mzKVDBqybr96RPOmpC9JAMIBxkPomidqs9Vh3E5Eac5g2qGcKz | |
8lEJvFrU6kopoxr0pd0c2zUL6Y5wheWAVoxbsjtvl2vuCiOgB9ey8gnZW0ksR9y3 | |
46eVnU8dQzIbJLGIJSC4d11I09BL7+Ffgpk5OwukbA2+YME5HZqx8= | |
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-Spam-SWARE-Status: | No, score=-5.0 required=5.0 tests=AWL,BAYES_00,GIT_PATCH_1,KAM_SHORT autolearn=ham version=3.3.1 spammy=H*u:5.1 |
X-HELO: | se1h-lax1.servconfig.com |
Subject: | Re: another question about cygwin bash trying to make connections |
To: | cygwin AT cygwin DOT com |
References: | <3af7d373-de36-cb8d-04ad-04ccda05667b AT molconn DOT com> <4397f4e8-a867-67b6-beed-018adbe5b4cc AT gmail DOT com> |
From: | LMH <lmh_users-groups AT molconn DOT com> |
Message-ID: | <99d7614e-b49d-6a15-dfee-7d1e030d55af@molconn.com> |
Date: | Tue, 7 Jan 2020 18:02:57 -0500 |
User-Agent: | Mozilla/5.0 (Windows NT 5.1; rv:49.0) Gecko/20100101 Firefox/49.0 SeaMonkey/2.46 |
MIME-Version: | 1.0 |
In-Reply-To: | <4397f4e8-a867-67b6-beed-018adbe5b4cc@gmail.com> |
X-OutGoing-Spam-Status: | No, score=-1.0 |
X-SpamExperts-Domain: | ecbiz204.inmotionhosting.com |
X-SpamExperts-Username: | 198.46.81.33 |
Authentication-Results: | servconfig.com; auth=pass smtp.auth=198 DOT 46 DOT 81 DOT 33 AT ecbiz204 DOT inmotionhosting DOT com |
X-SpamExperts-Outgoing-Class: | ham |
X-SpamExperts-Outgoing-Evidence: | Combined (0.25) |
X-Recommended-Action: | accept |
X-Report-Abuse-To: | spam AT se1-lax1 DOT servconfig DOT com |
X-IsSubscribed: | yes |
Marco Atzeri wrote: > Am 07.01.2020 um 21:58 schrieb LMH: >> Hello, >> >> >> This is the version of bash, >> >> GNU bash, version 4.3.42(4)-release (i686-pc-cygwin) >> >> it would be very helpful as a first step if I could find a verified digital signature >> for this version of bash. The index here, >> >> https://ftp.gnu.org/gnu/bash/ >> >> gives an archive of bash with a signature for each tar.gz but not the signature for >> each version of the extracted binary. >> >> Thanks, >> > > that is not the last version of bash, so I guess your system is not updated anyway > > > $ bash --version > GNU bash, version 4.4.12(3)-release (i686-pc-cygwin) > > -- > 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 > > No, this is an older system that I keep around to run and test XP software on. It has the latest version of cygwin that still supports XP (2.874). This system isn't on the internet very often. It is still of interest to me to understand how the components of cywgin work and what controls such things as how and why IPC may be triggered. This is especially true when I see behavior that doesn't make sense to me. I don't see any reason why bash should need to communicate with svchost every time it is run, especially where blocking that communication has no discernible effect. If this is evidence of a system problem somewhere, I of course would like to know about that as well. LMH -- 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
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |