RE: Updated: setup (2.880)

RE: Updated: setup (2.880)

[Nellis, Kenneth]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 1223 bytes --]

From: cygwin-announce-owner
> 
> A new version of Setup, release 2.880, has been uploaded to
> 
>    https://cygwin.com/setup-x86.exe     (32 bit version)
>    https://cygwin.com/setup-x86_64.exe  (64 bit version)
> ...
> Please send bug reports, as usual, to the public mailing list cygwin AT
> cygwin DOT com.

So, I went to download this latest setup.exe using the script 
that I've been using...

#!/bin/sh
# From http://cygwin.com/ml/cygwin/2012-04/msg00714.html
name=setup-x86_64.exe
wget -O $name --quiet http://cygwin.com/$name || exit
# ACL issues require some fixing up after wget
chmod +x $name
exit

...but Windows complained about the file format when I tried to launch 
it. Then "file" told me...

$ file *.exe
setup-x86_64.exe: gzip compressed data, from Unix
$

...so I added suffix .gz and then used (actually) WinZip to unzip
it, and it created a working setup.exe.

So, is this new behavior? Is it to be expected going forward?

--Ken Nellis
\x03B‹KCB”\x1c›Ø›\x19[H\x1c™\^[ܝ\x1cΈ\b\b\b\b\b\b\x1a\x1d\x1d\x1c\x0e‹ËØÞYÝÚ[‹˜ÛÛKÜ\x1c›Ø›\x19[\Ëš\x1d^[[\x03B‘TNˆ\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\x1a\x1d\x1d\x1c\x0e‹ËØÞYÝÚ[‹˜ÛÛKÙ˜\KÃB‘^[ØÝ[Y[\x18]\x1a[ÛŽˆ\b\b\b\b\b\b\b\b\x1a\x1d\x1d\x1c\x0e‹ËØÞYÝÚ[‹˜ÛÛKÙ^[ØÜËš\x1d^[[\x03B•[œÝXœØÜšX™H\x1a[™›Îˆ\b\b\b\b\b\x1a\x1d\x1d\x1c\x0e‹ËØÞYÝÚ[‹˜ÛÛKÛ[\vÈÝ[œÝXœØÜšX™K\Ú[\^[\x19CBƒB

Re: Updated: setup (2.880)

[Marco Atzeri]

On 19/06/2017 17:29, Nellis, Kenneth wrote:
> From: cygwin-announce-owner
>>
>> A new version of Setup, release 2.880, has been uploaded to
>>
>>    https://cygwin.com/setup-x86.exe     (32 bit version)
>>    https://cygwin.com/setup-x86_64.exe  (64 bit version)
>> ...
>> Please send bug reports, as usual, to the public mailing list cygwin AT
>> cygwin DOT com.
>
> So, I went to download this latest setup.exe using the script
> that I've been using...
>
> #!/bin/sh
> # From http://cygwin.com/ml/cygwin/2012-04/msg00714.html
> name=setup-x86_64.exe
> wget -O $name --quiet http://cygwin.com/$name || exit
> # ACL issues require some fixing up after wget
> chmod +x $name
> exit
>
> ...but Windows complained about the file format when I tried to launch
> it. Then "file" told me...
>
> $ file *.exe
> setup-x86_64.exe: gzip compressed data, from Unix
> $
>
> ...so I added suffix .gz and then used (actually) WinZip to unzip
> it, and it created a working setup.exe.
>
> So, is this new behavior? Is it to be expected going forward?
>
> --Ken Nellis
>

Not on this side :

$ wget https://www.cygwin.com/setup-x86_64.exe
--2017-06-19 18:27:55--  https://www.cygwin.com/setup-x86_64.exe
Resolving www.cygwin.com... 209.132.180.131
Connecting to www.cygwin.com|209.132.180.131|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 906771 (886K) [application/octet-stream]
Saving to: ‘setup-x86_64.exe’

setup-x86_64.exe    100%[===================>] 885.52K   381KB/s    in 2.3s

2017-06-19 18:27:59 (381 KB/s) - ‘setup-x86_64.exe’ saved [906771/906771]

$ wget https://www.cygwin.com/setup-x86_64.exe.sig
--2017-06-19 18:29:38--  https://www.cygwin.com/setup-x86_64.exe.sig
Resolving www.cygwin.com... 209.132.180.131
Connecting to www.cygwin.com|209.132.180.131|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 72 [application/pgp-signature]
Saving to: ‘setup-x86_64.exe.sig’

setup-x86_64.exe.si 100%[===================>]      72  --.-KB/s    in 0s

2017-06-19 18:29:39 (271 KB/s) - ‘setup-x86_64.exe.sig’ saved [72/72]


$ file setup-x86_64.exe
setup-x86_64.exe: PE32+ executable (GUI) x86-64, for MS Windows

$ gpg --verify setup-x86_64.exe.sig
gpg: assuming signed data in `setup-x86_64.exe'
gpg: Signature made Thu, Jun 15, 2017  8:50:31 PM CEST using DSA key ID 
676041BA
gpg: Good signature from "Cygwin <cygwin (at) cygwin.com>"
...



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

Re: Updated: setup (2.880)

[Andrey Repin]

Greetings, Nellis, Kenneth!

> wget -O $name --quiet http://cygwin.com/$name || exit

Do not use wget -O name unless you have no other choice.
The construction is essentially equal to

wget -O - --quiet http://cygwin.com/$name > "$name"

Means, it will never allow -N to work. (When -O given, -N is silently
discarded.)

> ...but Windows complained about the file format when I tried to launch
> it. Then "file" told me...

> $ file *.exe
> setup-x86_64.exe: gzip compressed data, from Unix
> $

> ...so I added suffix .gz and then used (actually) WinZip to unzip
> it, and it created a working setup.exe.

> So, is this new behavior? Is it to be expected going forward?

Not confirming, my installation went smooth, I barely noticed the setup
update. (Yes, I'm running it via script too.)


-- 
With best regards,
Andrey Repin
Monday, June 19, 2017 19:23:55

Sorry for my terrible english...


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

Re: Updated: setup (2.880)

[Andrey Repin]

Greetings, Nellis, Kenneth!

> name=setup-x86_64.exe
> wget -O $name --quiet http://cygwin.com/$name || exit

Wait, WHY do you download it over HTTP?
Use HTTPS.


-- 
With best regards,
Andrey Repin
Monday, June 19, 2017 19:28:44

Sorry for my terrible english...


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

Re: Updated: setup (2.880)

[Jon Turney]

On 19/06/2017 16:29, Nellis, Kenneth wrote:
> #!/bin/sh
> # From http://cygwin.com/ml/cygwin/2012-04/msg00714.html
> name=setup-x86_64.exe
> wget -O $name --quiet http://cygwin.com/$name || exit
> # ACL issues require some fixing up after wget
> chmod +x $name
> exit
> 
> ...but Windows complained about the file format when I tried to launch
> it. Then "file" told me...
> 
> $ file *.exe
> setup-x86_64.exe: gzip compressed data, from Unix
> $
> 
> ...so I added suffix .gz and then used (actually) WinZip to unzip
> it, and it created a working setup.exe.
> 
> So, is this new behavior? Is it to be expected going forward?

This behaviour is not expected or wanted.  I can't reproduce it, either.

> $ wget https://cygwin.com/setup-x86_64.exe
> --2017-06-19 17:31:56--  https://cygwin.com/setup-x86_64.exe
> Resolving cygwin.com... 209.132.180.131
> Connecting to cygwin.com|209.132.180.131|:443... connected.
> HTTP request sent, awaiting response... 200 OK
> Length: 906771 (886K) [application/octet-stream]
> Saving to: ‘setup-x86_64.exe’
> 
> setup-x86_64.exe    100%[===================>] 885.52K   550KB/s    in 1.6s
> 
> 2017-06-19 17:31:58 (550 KB/s) - ‘setup-x86_64.exe’ saved [906771/906771]
> 
> $ file setup-x86_64.exe
> setup-x86_64.exe: PE32+ executable (GUI) x86-64, for MS Windows
> 
> $ xxd setup-x86_64.exe | head -1
> 00000000: 4d5a 9000 0300 0000 0400 0000 ffff 0000  MZ..............

Do you have something in your ~/.wgetrc to add an "accept-encoding: 
gzip" header or something?

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

Re: Updated: setup (2.880)

[Andrey Repin]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=utf-8, Size: 1253 bytes --]

Greetings, Jon Turney!

>> $ wget https://cygwin.com/setup-x86_64.exe
>> --2017-06-19 17:31:56--  https://cygwin.com/setup-x86_64.exe
>> Resolving cygwin.com... 209.132.180.131
>> Connecting to cygwin.com|209.132.180.131|:443... connected.
>> HTTP request sent, awaiting response... 200 OK
>> Length: 906771 (886K) [application/octet-stream]
>> Saving to: ‘setup-x86_64.exe’
>> 
>> setup-x86_64.exe    100%[===================>] 885.52K   550KB/s    in 1.6s
>> 
>> 2017-06-19 17:31:58 (550 KB/s) - ‘setup-x86_64.exe’ saved [906771/906771]
>> 
>> $ file setup-x86_64.exe
>> setup-x86_64.exe: PE32+ executable (GUI) x86-64, for MS Windows
>> 
>> $ xxd setup-x86_64.exe | head -1
>> 00000000: 4d5a 9000 0300 0000 0400 0000 ffff 0000  MZ..............

> Do you have something in your ~/.wgetrc to add an "accept-encoding: 
> gzip" header or something?

My bet is malicious proxy server.


-- 
With best regards,
Andrey Repin
Monday, June 19, 2017 20:03:34

Sorry for my terrible english...\x03B‹KCB”\x1c›Ø›\x19[H\x1c™\^[ܝ\x1cΈ\b\b\b\b\b\b\x1a\x1d\x1d\x1c\x0e‹ËØÞYÝÚ[‹˜ÛÛKÜ\x1c›Ø›\x19[\Ëš\x1d^[[\x03B‘TNˆ\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\x1a\x1d\x1d\x1c\x0e‹ËØÞYÝÚ[‹˜ÛÛKÙ˜\KÃB‘^[ØÝ[Y[\x18]\x1a[ÛŽˆ\b\b\b\b\b\b\b\b\x1a\x1d\x1d\x1c\x0e‹ËØÞYÝÚ[‹˜ÛÛKÙ^[ØÜËš\x1d^[[\x03B•[œÝXœØÜšX™H\x1a[™›Îˆ\b\b\b\b\b\x1a\x1d\x1d\x1c\x0e‹ËØÞYÝÚ[‹˜ÛÛKÛ[\vÈÝ[œÝXœØÜšX™K\Ú[\^[\x19CBƒB

RE: Updated: setup (2.880)

[Nellis, Kenneth]

The folks who couldn't reproduce it were using different 
command syntax than I.

Mine:   wget -O setup-x86_64.exe http://cygwin.com/setup-x86_64.exe
Theirs: wget https://cygwin.com/setup-x86_64.exe

Why did I use that syntax? Because it was given in the OP,
http://cygwin.com/ml/cygwin/2012-04/msg00714.html,
and it worked at the time, so I stuck with it.

So, experimenting with this, I was able to reproduce what I 
reported from the command line using my syntax, above, again 
creating the gzip formatted file. Then I tried the alternate 
syntax ("Theirs"), and I got the desired executable binary, 
as others have found. Then the surprising part: I then 
retried my syntax, and it created the correct executable 
image! I saw that this exercise created file ~/.wget-hsts, 
so I deleted it, reran my syntax, and again it created the 
gzip format. I also noticed that it was significantly 
quicker to download the .gzip format, even though the size 
difference is small.

To Jon who asks:
> Do you have something in your ~/.wgetrc to add an "accept-encoding: gzip" header or something? 
No, I don't even have this file.

Here, I show the commands and output that corroborate my assertions:
1. reproduce original results
2. reproduce others' results
3. show others' results influences my results
4. remove hidden file to restore my original results

$ time wget -O setup-x86_64.exe http://cygwin.com/setup-x86_64.exe
--2017-06-19 13:04:16--  http://cygwin.com/setup-x86_64.exe
Resolving cygwin.com... 209.132.180.131
Connecting to cygwin.com|209.132.180.131|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 877562 (857K) [application/octet-stream]
Saving to: ‘setup-x86_64.exe’

setup-x86_64.exe    100%[===================>] 856.99K  --.-KB/s    in 0.01s

2017-06-19 13:04:17 (78.5 MB/s) - ‘setup-x86_64.exe’ saved [877562/877562]


real    0m0.306s
user    0m0.000s
sys     0m0.046s
$ ls -l
total 860
-rw-r----- 1 knellis Domain Users 877562 Jun  7 12:58 setup-x86_64.exe
$ file setup-x86_64.exe
setup-x86_64.exe: gzip compressed data, from Unix
$ rm setup-x86_64.exe
$ time wget https://cygwin.com/setup-x86_64.exe
--2017-06-19 13:04:51--  https://cygwin.com/setup-x86_64.exe
Resolving cygwin.com... 209.132.180.131
Connecting to cygwin.com|209.132.180.131|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 906771 (886K) [application/octet-stream]
Saving to: ‘setup-x86_64.exe’

setup-x86_64.exe    100%[===================>] 885.52K  1.31MB/s    in 0.7s

2017-06-19 13:04:52 (1.31 MB/s) - ‘setup-x86_64.exe’ saved [906771/906771]


real    0m0.992s
user    0m0.031s
sys     0m0.061s
$ ls -l
total 888
-rw-r----- 1 knellis Domain Users 906771 Jun  7 12:58 setup-x86_64.exe
$ file setup-x86_64.exe
setup-x86_64.exe: PE32+ executable (GUI) x86-64, for MS Windows
$ rm setup-x86_64.exe
$ time wget -O setup-x86_64.exe http://cygwin.com/setup-x86_64.exe
URL transformed to HTTPS due to an HSTS policy
--2017-06-19 13:05:27--  https://cygwin.com/setup-x86_64.exe
Resolving cygwin.com... 209.132.180.131
Connecting to cygwin.com|209.132.180.131|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 906771 (886K) [application/octet-stream]
Saving to: ‘setup-x86_64.exe’

setup-x86_64.exe    100%[===================>] 885.52K  1.03MB/s    in 0.8s

2017-06-19 13:05:28 (1.03 MB/s) - ‘setup-x86_64.exe’ saved [906771/906771]


real    0m1.171s
user    0m0.015s
sys     0m0.031s
$ ls -l
total 888
-rw-r----- 1 knellis Domain Users 906771 Jun  7 12:58 setup-x86_64.exe
$ file setup-x86_64.exe
setup-x86_64.exe: PE32+ executable (GUI) x86-64, for MS Windows
$ rm setup-x86_64.exe
$ rm ~/.wget-hsts
$ time wget -O setup-x86_64.exe http://cygwin.com/setup-x86_64.exe
--2017-06-19 13:06:29--  http://cygwin.com/setup-x86_64.exe
Resolving cygwin.com... 209.132.180.131
Connecting to cygwin.com|209.132.180.131|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 877562 (857K) [application/octet-stream]
Saving to: ‘setup-x86_64.exe’

setup-x86_64.exe    100%[===================>] 856.99K  3.99MB/s    in 0.2s

2017-06-19 13:06:30 (3.99 MB/s) - ‘setup-x86_64.exe’ saved [877562/877562]


real    0m0.399s
user    0m0.000s
sys     0m0.046s
$ ls -l
total 860
-rw-r----- 1 knellis Domain Users 877562 Jun  7 12:58 setup-x86_64.exe
$ file setup-x86_64.exe
setup-x86_64.exe: gzip compressed data, from Unix
$

I shall change to the better syntax.

--Ken Nellis

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

Re: Updated: setup (2.880)

[Andrey Repin]

Greetings, Nellis, Kenneth!

> The folks who couldn't reproduce it were using different 
> command syntax than I.

Doesn't matter what syntax I use, I'm unable to reproduce your effects.

> I shall change to the better syntax.

Get rid of intercepting proxies and your problem will go away as well.
It's not a matter of syntax.


-- 
With best regards,
Andrey Repin
Monday, June 19, 2017 20:37:29

Sorry for my terrible english...


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

RE: Updated: setup (2.880)

[Nellis, Kenneth]

From: Andrey Repin
> Doesn't matter what syntax I use, I'm unable to reproduce your effects.
> ...
> Get rid of intercepting proxies and your problem will go away as well.
> It's not a matter of syntax.

I'm unaware of any proxies involved. I haven't set any up. Don't even 
know how. Any proxies that may be involved are outside of my control.

I wonder if you have a ~/.wget-hsts file that affects your results as it 
did mine.

--Ken Nellis

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

Re: Updated: setup (2.880)

[Andrey Repin]

Greetings, Nellis, Kenneth!

> From: Andrey Repin
>> Doesn't matter what syntax I use, I'm unable to reproduce your effects.
>> ...
>> Get rid of intercepting proxies and your problem will go away as well.
>> It's not a matter of syntax.

> I'm unaware of any proxies involved. I haven't set any up. Don't even 
> know how. Any proxies that may be involved are outside of my control.

I didn't say they are under your control, I said get rid of them. I.e. by
using HTTPS as you should.

> I wonder if you have a ~/.wget-hsts file that affects your results as it 
> did mine.

I closely followed your experimentation and never been able to replicate
your issue.


-- 
With best regards,
Andrey Repin
Tuesday, June 20, 2017 14:03:17

Sorry for my terrible english...


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

Re: Updated: setup (2.880)

[Csaba Raduly]

Hi Kenneth,

On Mon, Jun 19, 2017 at 7:29 PM, Nellis, Kenneth  wrote:
...
>
> Here, I show the commands and output that corroborate my assertions:
> 1. reproduce original results
> 2. reproduce others' results
> 3. show others' results influences my results
> 4. remove hidden file to restore my original results
>
> $ time wget -O setup-x86_64.exe http://cygwin.com/setup-x86_64.exe
> --2017-06-19 13:04:16--  http://cygwin.com/setup-x86_64.exe
> Resolving cygwin.com... 209.132.180.131
> Connecting to cygwin.com|209.132.180.131|:80... connected.
> HTTP request sent, awaiting response... 200 OK
> Length: 877562 (857K) [application/octet-stream]
> Saving to: ‘setup-x86_64.exe’
>
> setup-x86_64.exe    100%[===================>] 856.99K  --.-KB/s    in 0.01s
>
> 2017-06-19 13:04:17 (78.5 MB/s) - ‘setup-x86_64.exe’ saved [877562/877562]
>
>
> real    0m0.306s
> user    0m0.000s
> sys     0m0.046s
> $ ls -l
> total 860
> -rw-r----- 1 knellis Domain Users 877562 Jun  7 12:58 setup-x86_64.exe
> $ file setup-x86_64.exe
> setup-x86_64.exe: gzip compressed data, from Unix
...

I also couldn't reproduce your scenario.

$ time wget -O setup-x86_64.exe http://cygwin.com/setup-x86_64.exe
--2017-06-24 10:34:02--  http://cygwin.com/setup-x86_64.exe
Resolving cygwin.com... 209.132.180.131
Connecting to cygwin.com|209.132.180.131|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 906771 (886K) [application/octet-stream]
Saving to: ‘setup-x86_64.exe’

setup-x86_64.exe
100%[==============================================================================================>]
885.52K  51.1KB/s    in 14s

2017-06-24 10:34:16 (62.8 KB/s) - ‘setup-x86_64.exe’ saved [906771/906771]


real    0m14.975s
user    0m0.046s
sys     0m0.031s

Csaba@assos ~
$ file setup-x86_64.exe
setup-x86_64.exe: PE32+ executable (GUI) x86-64, for MS Windows

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.

Csaba
-- 
GCS a+ e++ d- C++ ULS$ L+$ !E- W++ P+++$ w++$ tv+ b++ DI D++ 5++
The Tao of math: The numbers you can count are not the real numbers.
Life is complex, with real and imaginary parts.
"Ok, it boots. Which means it must be bug-free and perfect. " -- Linus Torvalds
"People disagree with me. I just ignore them." -- Linus Torvalds

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

RE: Updated: setup (2.880)

[Nellis, Kenneth]

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
Setting --output-document (outputdocument) to setup-x86_64.exe
DEBUG output created by Wget 1.19.1 on cygwin.

Reading HSTS entries from /home/knellis/.wget-hsts
--2017-06-27 16:42:01--  http://cygwin.com/setup-x86_64.exe
Resolving cygwin.com... 209.132.180.131
Caching cygwin.com => 209.132.180.131
Connecting to cygwin.com|209.132.180.131|:80... connected.
Created socket 5.
Releasing 0x0000000600066420 (new refcount 1).

---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---
200 OK
Registered socket 5 for persistent reuse.
Length: 877562 (857K) [application/octet-stream]
Saving to: ‘setup-x86_64.exe’

setup-x86_64.exe            100%[===========================================>] 856.99K  --.-KB/s    in 0.01s

2017-06-27 16:42:02 (73.9 MB/s) - ‘setup-x86_64.exe’ saved [877562/877562]

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

--Ken Nellis

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

Re: Updated: setup (2.880)

[Lee]

On 6/27/17, 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
> Setting --output-document (outputdocument) to setup-x86_64.exe
> DEBUG output created by Wget 1.19.1 on cygwin.
>
> Reading HSTS entries from /home/knellis/.wget-hsts
> --2017-06-27 16:42:01--  http://cygwin.com/setup-x86_64.exe
> Resolving cygwin.com... 209.132.180.131
> Caching cygwin.com => 209.132.180.131
> Connecting to cygwin.com|209.132.180.131|:80... connected.
> Created socket 5.
> Releasing 0x0000000600066420 (new refcount 1).
>
> ---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)

^^^^^^^^ that
it looks like you've got a cisco ironport playing mitm with your traffic.

  <.. snip ..>

> Note the response from the Apache server:
>> Content-Encoding: gzip

nobody else gets that, and you don't if you do a wget from home -
correct?  So it's most probably coming from the ironport & not the
cygwin web server

Regards,
Lee

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

Re: Updated: setup (2.880)

[Brian Inglis]

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

Re: Updated: setup (2.880)

[cyg Simple]

On 6/27/2017 4:55 PM, 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

Sorry if you've done this already but what if you use https instead of http?

> Setting --output-document (outputdocument) to setup-x86_64.exe
> DEBUG output created by Wget 1.19.1 on cygwin.
> 
> Reading HSTS entries from /home/knellis/.wget-hsts
> --2017-06-27 16:42:01--  http://cygwin.com/setup-x86_64.exe
> Resolving cygwin.com... 209.132.180.131
> Caching cygwin.com => 209.132.180.131
> Connecting to cygwin.com|209.132.180.131|:80... connected.
> Created socket 5.
> Releasing 0x0000000600066420 (new refcount 1).
> 
> ---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
> 

Do you have access to configure the allowable sites for download in
ironport?

https://supportforums.cisco.com/discussion/12920926/wsa-ironport-allow-exe-downloads-specific-urls-wsus-server

> ---response end---
> 200 OK
> Registered socket 5 for persistent reuse.
> Length: 877562 (857K) [application/octet-stream]
> Saving to: ‘setup-x86_64.exe’
> 
> setup-x86_64.exe            100%[===========================================>] 856.99K  --.-KB/s    in 0.01s
> 
> 2017-06-27 16:42:02 (73.9 MB/s) - ‘setup-x86_64.exe’ saved [877562/877562]
> 
> $ 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.
> 

It might be being added by ironport or perhaps an IE network setting
that is adding it to all requests for the file type.

-- 
cyg Simple

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