Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Bernd Edlinger <bernd.edlinger@hotmail.de>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: Alternative Mailing list archives
Date: Wed, 1 Apr 2020 10:47:25 +0200	[thread overview]
Message-ID: <AM6PR03MB5170ABC89AD72A90C2227FE4E4C90@AM6PR03MB5170.eurprd03.prod.outlook.com> (raw)
In-Reply-To: <878sjfzm30.fsf@igel.home>

Hi Andreas,

On 4/1/20 9:44 AM, Andreas Schwab wrote:
> There are also the NNTP archives on gmane.io.  They even contain the
> full headers.
> 
> Andreas.
> 

Thanks that is also good.

BUT I have a discovered a very serious problem with the mailing lists
that must be fixed by our overseers.

That is the scubbed attachments.

As an example please look at this one:
https://marc.info/?l=gdb-patches&m=158571308379946&w=2


you see this:

-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Fix-range-end-handling-of-inlined-subroutines.patch
Type: text/x-patch
Size: 10992 bytes
Desc: not available
URL: <http://sourceware.org/pipermail/gdb-patches/attachments/20200313/5158bb87/attachment.bin>

So there are two serious problems here:

1. there is a single point of failure, if sourceware.org goes down the attachment is lost.

2. since the url is http: a man in the middle can impersonate sourceware.org and give you a
virus instead of my patch file.
It does not help that sourceware.org redirects the download to https://sourceware.org/pipermail/gdb-patches/attachments/20200313/5158bb87/attachment.bin
an attacker will not be so polite to do that.


@overseeers: PLEASE STOP IMMEDIATELY THAT SCRUBBING


Thanks
Bernd.




      reply	other threads:[~2020-04-01  8:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-01  6:59 Bernd Edlinger
2020-04-01  7:44 ` Andreas Schwab
2020-04-01  8:47   ` Bernd Edlinger [this message]

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

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

  git send-email \
    --in-reply-to=AM6PR03MB5170ABC89AD72A90C2227FE4E4C90@AM6PR03MB5170.eurprd03.prod.outlook.com \
    --to=bernd.edlinger@hotmail.de \
    --cc=gdb-patches@sourceware.org \
    --cc=schwab@linux-m68k.org \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox