musl - "musl" gzip-compressed tarballs are decompressed if using newest wegt release

Follow @Openwall on Twitter for new release announcements and other news

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.LSU.2.20.1711011051060.6924@schiller.site>
Date: Wed, 1 Nov 2017 11:19:30 +0100 (CET)
From: "Jens Schleusener" <Jens.Schleusener@...nline.de>
To: musl@...ts.openwall.com
Subject: "musl" gzip-compressed tarballs are decompressed if using newest
 wegt release

Hi,

not a real "musl" software problem but just an observation of a changed 
behaviour of "musl" tarball downloads with the newest "wegt" release 
(1.19.2): The tarballs are saved now decompressed but contains the 
original extension (.tar.gz). Although if the extension would be .tar it 
seems at least to me an undesired behaviour.

Reason seems a new "wget" feature, here some extracted lines taken from 
the ChangeLog

  2017-08-04
  Add gzip Content-Encoding decompression
  (gethttp): Decompress files with gzip Content-Encoding

in combination with the HTTP header the www.musl-libc.org server delivers:

  Content-Type: application/x-tar
  Content-Encoding: gzip

Solutions/workarounds may be on the server side delivering of a HTTP 
header like

  Content-Type: application/x-gzip
  (or Content-Type: application/octet-stream)

or on the client side the use of the new "wget" option

  --compression=none

Regards

Jens

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.