From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mx.stare.cz (ns.stare.cz [79.98.77.229]) by mandoc.bsd.lv (OpenSMTPD) with ESMTP id bdd0d5c4 for ; Sun, 16 Feb 2020 07:43:40 -0500 (EST) Received: from localhost (stare.cz [local]) by stare.cz (OpenSMTPD) with ESMTPA id c78bec9a for ; Sun, 16 Feb 2020 13:43:38 +0100 (CET) Date: Sun, 16 Feb 2020 13:43:38 +0100 From: Jan Stary To: discuss@mandoc.bsd.lv Subject: Re: man.cgi and gzip manuals: bug or feature Message-ID: <20200216124338.GA34693@www.stare.cz> References: <20200216115947.7gsgn5hgkinplzo5@BlackBox> X-Mailinglist: mandoc-discuss Reply-To: discuss@mandoc.bsd.lv MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20200216115947.7gsgn5hgkinplzo5@BlackBox> On Feb 16 22:59:47, dev@sgregoratto.me wrote: > man.cgi doesn't handle serving gzipped manuals, with it dumping the raw > bytes onto the user's screen. You can view a simple test I made to > illustrate[1]. Not sure if this is a bug or some way of reducing attack > service ¯\_(ツ)_/¯. > > [1] https://man.sgregoratto.me/gzip-test/man1/sh.1 What happens when you name the file appropriately, such as ls.1.gz ? -- To unsubscribe send an email to discuss+unsubscribe@mandoc.bsd.lv