From: Eli Zaretskii <eliz@gnu.org>
To: Jens Schmidt <jschmidt4gnu@vodafonemail.de>
Cc: emacs-devel@gnu.org
Subject: Re: Storing sensitive data indefinitely in variables or buffers: Whether and how to fix?
Date: Wed, 31 May 2023 15:56:48 +0300 [thread overview]
Message-ID: <83bki0fylr.fsf@gnu.org> (raw)
In-Reply-To: <bf0942aa-fd27-bec4-13cd-ec115a622b97@vodafonemail.de> (message from Jens Schmidt on Tue, 30 May 2023 23:25:32 +0200)
> Date: Tue, 30 May 2023 23:25:32 +0200
> From: Jens Schmidt <jschmidt4gnu@vodafonemail.de>
>
> plstore.el stores clear-text sensitive data in a number of places in a
> running emacs without automatically expiring it as, for example,
> password-cache does.
>
> 1. As usually, fixing these decreases convenience. Is that OK?
In general, if the inconvenience is significant, it is best to make
the feature opt-in. Even if we do make it ON by default, there should
be a way of getting back old behavior, and that way should be
documented in NEWS.
> 2. Is fixing these considered a bug (relevant for emacs-29) even if it
> involves a bit more effort, possibly even new functions and
> variables?
No, this is not a "bugfix" in terms applicable to the emacs-29 branch.
These changes should go to master.
Thanks.
prev parent reply other threads:[~2023-05-31 12:56 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-30 21:25 Storing sensitive data indefinitely in variables or buffers: Whether and how to fix? Jens Schmidt
2023-05-31 8:02 ` Ihor Radchenko
2023-05-31 16:39 ` Adam Porter
2023-05-31 18:17 ` tomas
2023-06-01 6:34 ` Ihor Radchenko
2023-06-01 6:51 ` tomas
2023-06-01 7:11 ` Ihor Radchenko
2023-05-31 19:05 ` Eli Zaretskii
2023-06-01 6:48 ` Ihor Radchenko
2023-06-01 7:11 ` Eli Zaretskii
2023-06-01 7:29 ` Ihor Radchenko
2023-06-01 7:33 ` Eli Zaretskii
2023-06-01 7:34 ` tomas
2023-05-31 19:37 ` Jens Schmidt
2023-06-01 6:42 ` Ihor Radchenko
2023-06-01 20:10 ` Jens Schmidt
2023-06-01 20:47 ` Adam Porter
2023-06-02 6:30 ` Eli Zaretskii
2023-06-04 23:47 ` Adam Porter
2023-06-05 2:31 ` Eli Zaretskii
2023-05-31 12:56 ` Eli Zaretskii [this message]
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=83bki0fylr.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jschmidt4gnu@vodafonemail.de \
/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).