[arch-general] pacman-key complaining, but what to do about it?

[ProgAndy]

Am 02.04.2014 17:56, schrieb Magnus Therning:
> On Wed, Apr 02, 2014 at 10:16:04AM +0200, Magnus Therning wrote:
>> On Wed, Apr 2, 2014 at 9:32 AM, Magnus Therning <magnus at therning.org> wrote:
>>> On a newly set up system I've added the [haskell-core] repo [1], but
>>> get stuck with the following message from `pacman`:
>>>
>>> ~~~~
>>> % sudo pacman -Syy
>>> error: haskell-testing: signature from "ArchHaskell (Magnus Therning)
>>> <magnus at therning.org>" is invalid
>>> :: Synchronising package databases...
>>>   core                                                    108.2 KiB
>>> 1335K/s 00:00 [##############################################] 100%
>>>   haskell-testing.sig                                      96.0   B
>>> 0.00B/s 00:00 [##############################################] 100%
>>> error: haskell-testing: signature from "ArchHaskell (Magnus Therning)
>>> <magnus at therning.org>" is invalid
>>> error: failed to update haskell-testing (invalid or corrupted database
>>> (PGP signature))
>>>   extra                                                  1565.7 KiB
>>> 1947K/s 00:01 [##############################################] 100%
>>>   community                                                 2.1 MiB
>>> 1735K/s 00:01 [##############################################] 100%
>>>   multilib                                                115.3 KiB
>>> 1746K/s 00:00 [##############################################] 100%
>>> error: database 'haskell-testing' is not valid (invalid or corrupted
>>> database (PGP signature))
>>> ~~~~
>>>
>>> I've read [2] and verified (to the best of my ability) that I have
>>> correct time settings.  I've also tried resetting the keys, but that
>>> doesn't improve the situation either.
>>>
>>> What else could it be?  How do I find out?  What can I do about it?
>> I think I've found the reason for it:
>>
>> ~~~~
>> community.db:       gzip compressed data, last modified: Wed Apr  2
>> 04:23:21 2014, from Unix
>> core.db:            gzip compressed data, last modified: Tue Apr  1
>> 19:08:44 2014, from Unix
>> extra.db:           gzip compressed data, last modified: Wed Apr  2
>> 01:09:14 2014, from Unix
>> haskell-testing.db: POSIX tar archive
>> multilib.db:        gzip compressed data, last modified: Wed Apr  2
>> 05:12:37 2014, from Unix
>> ~~~~
>>
>> Where and why would un-gzipping strike like this?
> And now I've confirmed that this un-gzipping doesn't happen on my
> private computer at home.  So, what's causing this un-gzipping of the
> downloaded repo db, I wonder?
>
> /M
>
There may be a transparent proxy in your routing chain that strips 
compression in order to run a virus scan.
The server sends these headers for haskell-core.db
( curl -I http://xsounds.org/~haskell/core/x86_64/haskell-core.db )

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

It might work as expected without a Content-Encoding header:

Content-Type: application/x-gzip