From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: jporterbugs@gmail.com, ozzloy@challenge-bot.com,
65973@debbugs.gnu.org, ozzloy@gmail.com,
sebastian@sebasmonia.com
Subject: bug#65973: [PATCH] ; send filename, not full path, on EWW form submit
Date: Thu, 07 Nov 2024 08:20:41 +0200 [thread overview]
Message-ID: <86ttcjr2di.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmkQpM1MA09wYiepRAter-5zOExCK=+g0SWivkxnh135mQ@mail.gmail.com> (message from Stefan Kangas on Wed, 6 Nov 2024 23:30:54 +0000)
> From: Stefan Kangas <stefankangas@gmail.com>
> Date: Wed, 6 Nov 2024 23:30:54 +0000
> Cc: ozzloy@challenge-bot.com, 65973@debbugs.gnu.org, ozzloy@gmail.com
>
> Jim Porter <jporterbugs@gmail.com> writes:
>
> > On 11/5/2024 9:08 AM, Eli Zaretskii wrote:
> >
> >> I'd like some rationale for this change. The original report never
> >> explains why sending the full absolute file name to the server is bad.
> >
> > I see three possible reasons: 1) there could be (probably minor) privacy
> > issues with sending the directory structure along to a server;
>
> >From a privacy perspective, I don't think this we can really consider
> this as a minor issue.
>
> Users commonly use their full names, or another similarly unique
> identifier, as their login name. It goes without saying, that sending a
> string such as "/home/myfullname/some/file" to a remote host completely
> defeats all notions of preserving user privacy.
The private information can be in the file name you send as well, so
this is not a convincing argument.
But since the RFC says to ignore the leading directories, I think the
change is okay, provided we describe the rationale in the comments to
the code. It is very unusual thing in Emacs to remove leading
directories from a file name, so doing so generally begs for some
commentary.
next prev parent reply other threads:[~2024-11-07 6:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-14 6:10 bug#65973: [PATCH] ; send filename, not full path, on EWW form submit daniel watson via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-15 11:47 ` Stefan Kangas
2023-09-19 7:15 ` daniel watson via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-02 15:02 ` ozzloy
2024-11-05 14:34 ` Sebastián Monía
2024-11-05 17:08 ` Eli Zaretskii
2024-11-05 19:36 ` Jim Porter
2024-11-06 3:30 ` Sebastián Monía
2024-11-06 15:34 ` daniel watson
2024-11-06 23:30 ` Stefan Kangas
2024-11-07 6:20 ` Eli Zaretskii [this message]
2024-11-07 18:58 ` Jim Porter
2024-11-08 1:33 ` Stefan Kangas
2024-11-07 18:52 ` Jim Porter
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=86ttcjr2di.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=65973@debbugs.gnu.org \
--cc=jporterbugs@gmail.com \
--cc=ozzloy@challenge-bot.com \
--cc=ozzloy@gmail.com \
--cc=sebastian@sebasmonia.com \
--cc=stefankangas@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.