unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefan@marxist.se>
To: Eli Zaretskii <eliz@gnu.org>
Cc: rgm@gnu.org, monnier@iro.umontreal.ca, 46472@debbugs.gnu.org
Subject: bug#46472: Make lisp/mail/uce.el obsolete
Date: Tue, 12 Oct 2021 10:29:16 -0700	[thread overview]
Message-ID: <CADwFkmkwUzuMSf13Vow5E9BgK_3utdWZeeGRdV0NOvGDKaeWiA@mail.gmail.com> (raw)
In-Reply-To: <83pmsap50e.fsf@gnu.org>

Eli Zaretskii <eliz@gnu.org> writes:

>> I'd suggest installing the change as attached on emacs-28.  If that's
>> not possible, I'd like to install it on master, but add the same text to
>> the package "Commentary" section on emacs-28.
>
> On master, please.

It is really unfortunate if we can't even document serious security and
privacy issues in Emacs 28 at this point.  I do not see how such
documentation could possibly affect the release date.

> And I don't see why have the same text twice.

I removed the duplicates in the new patch.  Did I send the wrong patch?

Or maybe my suggestion was not clear:

- Emacs 28: Documentation changes only.  Do not merge to master.
- Emacs 29: Warning only, no documentation changes.

>> +- You will confirm that your email address is valid, thus ensuring
>> +  you get more spam.
>> +
>> +- You will leak information (e.g. on your email server and
>> +  setup), thus opening yourself up for further attack.  They are
>> +  likely to find your IP and \"geolocation\"), which often makes
>> +  it trivial to find e.g. your home address and phone number.
>
> The first paragraph is a special case of the second one.

Yes, it is also the one that immediately shows why this is
counter-productive, so it is worth making into its own item.

>> +- You confirm that the email did not land in your spam folder.
>> +  (This helps them refine their methods of spamming.)
>
> This is also the same as what you already said.

It is subtly different:

1. Spammers can use the information that your address is valid.

2. They can also use the information that their email has been crafted
   in such a way that they can evade some spam filters.

>> +- Scammers have been known to threaten, intimidate, and use other
>> +  forms of criminal manipulation.  Replying to spam can lead down
>> +  a path that you may not want to be on.
>
> This is the same as "open yourself to ..." paragraph.

It is hammering home the point to a certain extent, sure.  I think it is
motivated and useful.  There is no specific reason to keep this text
very brief: it is much more important that it accurately conveys the
dangers involved.





  reply	other threads:[~2021-10-12 17:29 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-12 21:58 bug#46472: Make lisp/mail/uce.el obsolete Stefan Kangas
2021-02-13  7:58 ` Eli Zaretskii
2021-02-13 12:25   ` Stefan Kangas
2021-02-13 14:00     ` Eli Zaretskii
2021-03-04 19:27       ` Glenn Morris
2021-03-04 21:12         ` Eli Zaretskii
2021-03-06 17:14           ` Stefan Kangas
2021-03-06 17:25             ` Eli Zaretskii
2022-06-17 13:07         ` Lars Ingebrigtsen
2021-10-12  4:33       ` Stefan Kangas
2021-10-12 13:52         ` Eli Zaretskii
2021-10-12 16:12           ` Stefan Kangas
2021-10-12 16:44             ` Eli Zaretskii
2021-10-12 17:29               ` Stefan Kangas [this message]
2021-10-12 18:50                 ` Eli Zaretskii
2021-10-14 20:45                   ` Stefan Kangas
2021-10-15  6:12                     ` Eli Zaretskii
2021-10-15  8:50                       ` Stefan Kangas
2021-10-15 10:46                         ` Eli Zaretskii
2021-10-16 12:48                           ` Stefan Kangas
2021-10-16 12:50                             ` Eli Zaretskii
2021-10-17 23:56                               ` Stefan Kangas
2021-10-16 12:32                       ` Stefan Kangas
2021-03-03 21:22   ` Stefan Monnier
2021-03-04  3:39     ` Eli Zaretskii

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=CADwFkmkwUzuMSf13Vow5E9BgK_3utdWZeeGRdV0NOvGDKaeWiA@mail.gmail.com \
    --to=stefan@marxist.se \
    --cc=46472@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=rgm@gnu.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.
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).