linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Slade Watkins <slade@sladewatkins.com>
To: Benjamin Poirier <benjamin.poirier@gmail.com>
Cc: Vladimir Oltean <olteanv@gmail.com>,
	Lijun Pan <lijunp213@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Networking <netdev@vger.kernel.org>
Subject: Re: Unsubscription Incident
Date: Mon, 25 Oct 2021 13:04:34 -0400	[thread overview]
Message-ID: <CA+pv=HPyCEXvLbqpAgWutmxTmZ8TzHyxf3U3UK_KQ=ePXSigBQ@mail.gmail.com> (raw)
In-Reply-To: <YXY15jCBCAgB88uT@d3>

On Mon, Oct 25, 2021 at 12:43 AM Benjamin Poirier
<benjamin.poirier@gmail.com> wrote:
>
> On 2021-10-22 18:54 +0300, Vladimir Oltean wrote:
> > On Fri, 22 Oct 2021 at 18:53, Lijun Pan <lijunp213@gmail.com> wrote:
> > >
> > > Hi,
> > >
> > > From Oct 11, I did not receive any emails from both linux-kernel and
> > > netdev mailing list. Did anyone encounter the same issue? I subscribed
> > > again and I can receive incoming emails now. However, I figured out
> > > that anyone can unsubscribe your email without authentication. Maybe
> > > it is just a one-time issue that someone accidentally unsubscribed my
> > > email. But I would recommend that our admin can add one more
> > > authentication step before unsubscription to make the process more
> > > secure.
> > >
> > > Thanks,
> > > Lijun
> >
> > Yes, the exact same thing happened to me. I got unsubscribed from all
> > vger mailing lists.
>
> It happened to a bunch of people on gmail:
> https://lore.kernel.org/netdev/1fd8d0ac-ba8a-4836-59ab-0ed3b0321775@mojatatu.com/t/#u

I can at least confirm that this didn't happen to me on my hosted
Gmail through Google Workspace. Could be wrong, but it seems isolated
to normal @gmail.com accounts.

Best,
             -slade

  reply	other threads:[~2021-10-25 17:08 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-22 15:53 Unsubscription Incident Lijun Pan
2021-10-22 15:54 ` Vladimir Oltean
2021-10-25  4:43   ` Benjamin Poirier
2021-10-25 17:04     ` Slade Watkins [this message]
2021-10-25 18:08       ` Metztli Information Technology
2021-10-25 19:47         ` Slade Watkins
2021-10-25 18:34       ` Shannon Nelson
2021-10-25 19:44         ` Slade Watkins
2022-02-20 23:54           ` Metztli Information Technology
2022-02-23  3:06             ` Slade Watkins
2021-10-27 19:34         ` Jakub Kicinski
2021-10-27 19:40           ` Shannon Nelson
2021-10-27 20:42           ` John 'Warthog9' Hawley
2021-10-28  0:27             ` Slade Watkins
2021-10-28  4:05               ` John 'Warthog9' Hawley
2021-10-25 19:32 ` Cong Wang
2021-10-27  0:02   ` Slade Watkins
2021-10-27 19:29     ` Randy Dunlap
2021-10-27 23:07       ` Richard Cochran

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='CA+pv=HPyCEXvLbqpAgWutmxTmZ8TzHyxf3U3UK_KQ=ePXSigBQ@mail.gmail.com' \
    --to=slade@sladewatkins.com \
    --cc=benjamin.poirier@gmail.com \
    --cc=lijunp213@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=olteanv@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).