public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: Updated: setup (2.880)
Date: Wed, 28 Jun 2017 05:34:00 -0000	[thread overview]
Message-ID: <5370dce1-012a-1442-86c0-28a9232a1486@SystematicSw.ab.ca> (raw)
In-Reply-To: <BN6PR2001MB1074F5546A217174ABC51170F1DC0@BN6PR2001MB1074.namprd20.prod.outlook.com>

On 2017-06-27 14:55, Nellis, Kenneth wrote:
> From: Csaba Raduly 
>> I also couldn't reproduce your scenario.
>> ...
>> Since it's reproducible for you, you could (if you're curious) run
>> wget with the -d (--debug) switch or break out the heavy artillery:
>> install Wireshark and look at the HTTP headers sent and received by
>> wget.
> Thanx, Csaba, for your interest. Another test with -d is easy enough,
> so here it is:
> $ wget -d -O setup-x86_64.exe http://cygwin.com/setup-x86_64.exe
...
> ---request begin---
> GET /setup-x86_64.exe HTTP/1.1
> User-Agent: Wget/1.19.1 (cygwin)
> Accept: */*
> Accept-Encoding: identity
> Host: cygwin.com
> Connection: Keep-Alive
> ---request end---
> HTTP request sent, awaiting response...
> ---response begin---
> HTTP/1.1 200 OK
> Server: Apache
> ETag: "16b1f9e-dd613-55161a558184f"
> Accept-Ranges: bytes
> Cache-Control: max-age=0
> Expires: Tue, 27 Jun 2017 20:40:06 GMT
> Vary: Accept-Encoding
> Content-Encoding: gzip
> Content-Security-Policy: default-src 'self' http: https:
> Keep-Alive: timeout=30, max=20
> Content-Length: 877562
> Content-Type: application/octet-stream
> Last-Modified: Wed, 07 Jun 2017 16:58:31 GMT
> Date: Tue, 27 Jun 2017 20:39:27 GMT
> Age: 0
> Via: 1.1 ironport.tms.local:80 (Cisco-WSA/10.1.0-204)
> Connection: keep-alive
> ---response end---
...
> $ file *.exe
> setup-x86_64.exe: gzip compressed data, from Unix
> $
> Note the response from the Apache server:
>> Content-Encoding: gzip
> Not sure why it would do that. Maybe my wget could be more specific.
> But my updated script (per advice from others) is working fine.

Try:
$ rm -f setup-x86_64.exe
$ wget -d -N -nv --no-cache --no-http-keep-alive --no-proxy \
	https://cygwin.com/setup-x86_64.exe
and see if it can bypass the effects of the appliance, or get it to
respond as requested, but it may download and cache gzipped content
that pass its scans, and serve them as is, ignoring client content
negotiation. Not encouraging when a security product web site states
in its Features [emphasis added]:
"*When* compromise occurs, quickly determine the scope of the damage,
remediate it, and bring operations back to normal."

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

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

  parent reply	other threads:[~2017-06-28  5:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <088b3d84-aad8-4984-1892-b66b9714f343@dronecode.org.uk>
2017-06-19 15:29 ` Nellis, Kenneth
2017-06-19 16:34   ` Marco Atzeri
2017-06-19 16:35   ` Andrey Repin
2017-06-19 16:35   ` Andrey Repin
2017-06-19 16:38   ` Jon Turney
2017-06-19 17:05     ` Andrey Repin
2017-06-19 17:29     ` Nellis, Kenneth
2017-06-19 17:50       ` Andrey Repin
2017-06-19 17:55         ` Nellis, Kenneth
2017-06-20 11:05           ` Andrey Repin
2017-06-24  8:38       ` Csaba Raduly
2017-06-27 20:55         ` Nellis, Kenneth
2017-06-27 23:25           ` Lee
2017-06-28  5:34           ` Brian Inglis [this message]
2017-06-29 17:23           ` cyg Simple

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=5370dce1-012a-1442-86c0-28a9232a1486@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --cc=cygwin@cygwin.com \
    /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).