From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: users@linux.kernel.org, tools@linux.kernel.org
Subject: Re: [kernel.org users] Gmail message ID finder Chrome extension
Date: Fri, 27 Mar 2020 20:07:46 -0600 [thread overview]
Message-ID: <CAHmME9oPWZFggrmDyOeu26HJZE16kmaHZ3HXUCTm1Yy0cLGrgQ@mail.gmail.com> (raw)
In-Reply-To: <20200327165402.slc5l46hc7hlo2l5@chatter.i7.local>
Note that this extension has access to your gmail.com content, and can
also be remotely updated by its original author. I'm not sure I'd be
too happy about having this rando developer being the weakest link in
security posture. However, you can download that and install it
locally, or make it into a bookmarklet or greasemonkey script.
next prev parent reply other threads:[~2020-03-28 2:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-27 16:54 Gmail message ID finder Chrome extension Konstantin Ryabitsev
2020-03-28 2:07 ` Jason A. Donenfeld [this message]
2020-03-29 14:54 ` [kernel.org users] " Linus Walleij
2020-03-29 17:13 ` Konstantin Ryabitsev
2020-03-30 20:31 ` Linus Walleij
2020-03-31 8:03 ` Geert Uytterhoeven
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=CAHmME9oPWZFggrmDyOeu26HJZE16kmaHZ3HXUCTm1Yy0cLGrgQ@mail.gmail.com \
--to=jason@zx2c4.com \
--cc=konstantin@linuxfoundation.org \
--cc=tools@linux.kernel.org \
--cc=users@linux.kernel.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;
as well as URLs for NNTP newsgroup(s).