unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Robert Pluim <rpluim@gmail.com>
To: Clemens Radermacher <clemens.radermacher@posteo.de>
Cc: 33825@debbugs.gnu.org
Subject: bug#33825: 25.2; , Failing to verify signature for ELPA debbugs package
Date: Sun, 30 Dec 2018 13:55:44 +0100	[thread overview]
Message-ID: <m2va3b897z.fsf@gmail.com> (raw)
In-Reply-To: <66111503-49dd-f295-f43f-3d07ef577697@posteo.de> (Clemens Radermacher's message of "Sun, 30 Dec 2018 13:34:09 +0100")

Clemens Radermacher <clemens.radermacher@posteo.de> writes:

> On 30.12.18 13:12, Robert Pluim wrote:
>
>> There are 'transparent' proxies which will untar archives and then
>> retar them, resulting in a file that fails signature verification even
>> though the contents are identical. When you then repeat the download,
>> the proxy knows it has previously inspected the file, and thus lets
>> through the original. Using https solves this issue 99% of the time.
>
> That's interesting thanks! For GNU ELPA I use http indeed, because I rely on Emacs 
> taking care of the verification. I don't understand why those proxies should 
> unpack archives though, is that for filtering purposes?

In enlightened democracies they want to see if there is any malware
hiding inside. In other types of countries they're filtering
'undesirable' content. Identifying which type youʼre living in is
becoming harder every day :-)

Robert





  reply	other threads:[~2018-12-30 12:55 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-21 13:38 bug#33825: 25.2; Failing to verify signature for ELPA debbugs package clemera
2018-12-21 23:39 ` Glenn Morris
2018-12-22 12:08 ` bug#33825: 25.2; , " clemera
2018-12-30 12:12   ` Robert Pluim
2018-12-30 12:34     ` Clemens Radermacher
2018-12-30 12:55       ` Robert Pluim [this message]
2019-09-13 19:50 ` Stefan Kangas
2019-09-16  9:07   ` Robert Pluim
2019-09-16 11:04     ` Stefan Kangas
2019-09-16 13:28       ` Robert Pluim
2019-09-16 14:29       ` Eli Zaretskii
2019-09-16 19:13         ` Stefan Kangas
2019-09-17 13:34           ` Robert Pluim
2019-09-20 17:24             ` Stefan Kangas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m2va3b897z.fsf@gmail.com \
    --to=rpluim@gmail.com \
    --cc=33825@debbugs.gnu.org \
    --cc=clemens.radermacher@posteo.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).