public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Tim Prince <n8tm@aol.com>
To: cygwin@cygwin.com
Subject: Re: ShellShock and Latest Version Problem
Date: Sun, 05 Oct 2014 00:02:00 -0000	[thread overview]
Message-ID: <54308A71.9060609@aol.com> (raw)
In-Reply-To: <m0ptu0$g3g$1@ger.gmane.org>


On 10/4/2014 6:56 PM, René Berber wrote:
> On 10/4/2014 4:38 PM, Dennis Putnam wrote:
>> On 10/4/2014 4:38 PM, René Berber wrote:
>>> On 10/4/2014 2:55 PM, Dennis Putnam wrote:
>>>
>>>> According to the cygwin web site the latest version that contains
>>>> the shellshock patch is 1.7.32. I ran setup-x86_64.exe to get the
>>>> latest patches but I wind up with version 1.7.16 and nothing later
>>>> is found. My cygwin test indicates it is still vulnerable. How do I
>>>> get 1.7.32 if not through setup? TIA.
>>> Shellshock is related to the bash version, not the Cygwin version.
>>>
>>> If you updated Cygwin and think you still have an older version (of
>>> Cygwin), that probably means that you didn't stop all processes that
>>> use the Cygwin dll.
>>>
>>> Updating Bash doesn't affect, or depend, on the Cygwin dll.
>> Thanks for the reply. I assumed that since bash was part of basic Cygin,
>> if I updated everything, bash would be included. I had Cygwin completely
>> down when I updated with setup. Why did I not get the latest bash with
>> the other updates? How to I get the right version of bash other than
>> with setup?
> Use setup.  Don't assume it doesn't work, it does work fine.
>
> Check the version available shown in setup, it its not (as of today)
> 4.1.16 then the _mirror_ you are using is stale (which would explain why
> you didn't get the latest version of Cygwin).
Slightly off topic, I tend to put off updating from setup due to the
default of rolling gcc back to an earlier (buggier, in my tests)
version.  There are about 6 selections which have to be set to Keep to
avoid breaking it.

-- 
Tim Prince


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

  reply	other threads:[~2014-10-05  0:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-04 19:55 Dennis Putnam
2014-10-04 20:38 ` René Berber
2014-10-04 21:38   ` Dennis Putnam
2014-10-04 22:56     ` René Berber
2014-10-05  0:02       ` Tim Prince [this message]
2014-10-05 13:30       ` Dennis Putnam
2014-10-05 13:41         ` Yaakov Selkowitz
2014-10-05 13:46           ` Dennis Putnam
2014-10-05 13:48             ` Yaakov Selkowitz
2014-10-05 15:08               ` Dennis Putnam

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=54308A71.9060609@aol.com \
    --to=n8tm@aol.com \
    --cc=cygwin@cygwin.com \
    --cc=tprince@computer.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).