From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-gw0-f50.google.com (mail-gw0-f50.google.com [74.125.83.50]) by mail.saout.de (Postfix) with ESMTP for ; Thu, 4 Mar 2010 23:59:43 +0100 (CET) Received: by gwb20 with SMTP id 20so1548036gwb.37 for ; Thu, 04 Mar 2010 14:59:42 -0800 (PST) Message-ID: <4B903B5C.70404@gmail.com> Date: Thu, 04 Mar 2010 17:59:40 -0500 From: Scott Castaline MIME-Version: 1.0 References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [dm-crypt] dm-crypt Digest, Vol 9, Issue 4 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: dm-crypt@saout.de > Today's Topics: > > 1. Re2: reading archives (Arno Wagner) > 2. reading archives (Scott Castaline) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 4 Mar 2010 01:31:16 +0100 > From: Arno Wagner > To: dm-crypt@saout.de > Cc: christophe@saout.de > Subject: [dm-crypt] Re2: reading archives > Message-ID:<20100304003116.GA1196@tansi.org> > Content-Type: text/plain; charset=us-ascii > > > Ok, I looked a bit closer. It seems this is compressed > on-the-fly and corrupted on server side. Strangely > the corruption seems to be a windows thing or at least > browser dependent. I got suspicuous after I got two > different sized files with Opera and Firefox. On > Linux I downloaded with wget for yet another size. > > After a bit of messing around, I have it now: > Under Windows the files get compressed with gzip > twice! Possibly some terminally stupid, over-helpful > automatisation that decided to make sure it is a > gzip'ed file. > > Temporary workaround for Windows: > > Decompress, rename to name.gz and decompress again. > You may also have to click through a folder hierachy > (that I had no idea gzip could support). > > Admin of the archive cc'ed, just in case. > > Arno > Ok, doing gzip twice was the trick, I can now read the archives from Aug 09 to Jan 10. Are you doing the list on a Windows Server? I've zipped files on Linux many times and never ran into this bug of double packing before. I did wonder about the fact that the 1st unpacking produced the same size file that the size didn't change until the 2nd go around.