From: philipk@posteo.net (Philip K.)
To: rms@gnu.org
Cc: contovob@tcd.ie, larsi@gnus.org, alex.branham@gmail.com,
40676@debbugs.gnu.org, rpluim@gmail.com
Subject: bug#40676: 28.0.50; gnus locks when reading email
Date: Thu, 30 Jul 2020 10:32:51 +0200 [thread overview]
Message-ID: <87k0yl768c.fsf@posteo.net> (raw)
In-Reply-To: <E1k0yyW-0004rs-Ra@fencepost.gnu.org> (message from Richard Stallman on Wed, 29 Jul 2020 23:11:20 -0400)
Richard Stallman <rms@gnu.org> writes:
> [[[ To any NSA and FBI agents reading my email: please consider ]]]
> [[[ whether defending the US Constitution against all enemies, ]]]
> [[[ foreign or domestic, requires you to follow Snowden's example. ]]]
>
> > > Indeed -- it makes libravatar a much worse interface than the central
> > > Gravatar service (where you just have to trust the Gravatar people
> > > somewhat, instead of the entire internet).
> > >
> > > So that's another reason not to make libravatar the default provider.
>
> I don't know about libravatar, but ISTR that gravatar was found
> to do some sort of surveillance of users.
I'm not sure if it was proven, but just like Google Analytics or the
Facebook Like-button, they offer a service with a hidden fee -- that
they can or cannot exploit.
In the case of Emacs' Gravatar Integration, they get "notified" whenever
someone opens a message from person X (at least once), meaning they
could more easily reconstruct a database of who communicates with whom.
> Is that correct? Was libravatar intended as a replacement to respect
> users' privacy more than gravatar?
From libravatar's web page:
FREEDOM AND FEDERATION
How is Libravatar different from Gravatar though? The main
difference is that while Libravatar.org is an online avatar
hosting service just like Gravatar, the software that powers the
former is also available for download under a free software
license.
Why would you want to run your own instance? Our belief is that
centralised approaches don't put users in control. If you own
your own domain name, you control how mail is delivered to your
domain. You should also be able to control how avatars are
served to other websites.
So kind of, thought it seems to be more about controlling the software
you use than privacy per se.
> But it seems there is a problem with using libravatar, right?
Yes, the same attack as above with Gravatar (getting notified when you
open a message), just that a third party can set up their own libravatar
server and get notified when I open their email, instead of one
centralised service. So kind of like tracking bits in HTML messages.
> If that is the case, we should not think of "use gravatar"
> as a _solution_. It might fix an urgent problem, but we
> would not want it as a permanent change. A real solution
> is to make libravatar work well.
That would require an architectural change to libravatar itself. It's
current mechanism to retrieve an image for user@domain.tld is:
1. Check if domain.tld has a libravatar service (via DNS)
2. If yes, use that server, otherwise default to libravatar's server
3. Send a request to the server using the MD5/SHA256 hash of
user@domain.tld
Steps 1./2. are the trick to federation, but the crux of the issue as
well.
> If what is needed is async DNS lookup, how about running
> a shell command asynchronously to do it?
I guess that would also be possible, but wouldn't that require a DNS
tool to be installed on the system?
--
Philip K.
next prev parent reply other threads:[~2020-07-30 8:32 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-16 23:18 bug#40676: 28.0.50; gnus locks when reading email Alex Branham
2020-04-17 6:51 ` Eli Zaretskii
2020-04-17 11:51 ` Basil L. Contovounesios
2020-04-17 17:26 ` Alex Branham
2020-04-18 10:26 ` Robert Pluim
2020-04-18 11:50 ` Alex Branham
2020-07-19 2:20 ` Lars Ingebrigtsen
2020-07-19 8:15 ` Philip K.
2020-07-19 13:02 ` Lars Ingebrigtsen
2020-07-19 13:37 ` Philip K.
2020-07-19 13:52 ` Lars Ingebrigtsen
2020-07-29 6:48 ` Lars Ingebrigtsen
2020-07-30 1:43 ` Lars Ingebrigtsen
2020-07-30 3:30 ` Lars Ingebrigtsen
2020-07-30 3:11 ` Richard Stallman
2020-07-30 8:32 ` Philip K. [this message]
2020-07-31 3:24 ` Richard Stallman
2020-07-20 8:49 ` Robert Pluim
2020-07-20 9:05 ` Lars Ingebrigtsen
2020-07-20 9:23 ` Lars Ingebrigtsen
2020-07-20 9:33 ` Robert Pluim
2020-07-20 9:36 ` Robert Pluim
2020-07-20 11:02 ` Lars Ingebrigtsen
2020-07-20 9:41 ` Lars Ingebrigtsen
2020-07-20 9:43 ` Lars Ingebrigtsen
2020-04-17 15:09 ` Eric Abrahamsen
2020-04-17 15:14 ` Robert Pluim
2020-04-17 15:22 ` Eric Abrahamsen
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=87k0yl768c.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=40676@debbugs.gnu.org \
--cc=alex.branham@gmail.com \
--cc=contovob@tcd.ie \
--cc=larsi@gnus.org \
--cc=rms@gnu.org \
--cc=rpluim@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.
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).