all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Jens Schmidt <jschmidt4gnu@vodafonemail.de>
To: emacs-devel@gnu.org
Subject: Storing sensitive data indefinitely in variables or buffers: Whether and how to fix?
Date: Tue, 30 May 2023 23:25:32 +0200	[thread overview]
Message-ID: <bf0942aa-fd27-bec4-13cd-ec115a622b97@vodafonemail.de> (raw)

This is related to

   https://lists.gnu.org/archive/html/emacs-devel/2023-05/msg00327.html

and bug#63627 I've opened to track progress.

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?

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?

Thanks.



             reply	other threads:[~2023-05-30 21:25 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-30 21:25 Jens Schmidt [this message]
2023-05-31  8:02 ` Storing sensitive data indefinitely in variables or buffers: Whether and how to fix? 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

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=bf0942aa-fd27-bec4-13cd-ec115a622b97@vodafonemail.de \
    --to=jschmidt4gnu@vodafonemail.de \
    --cc=emacs-devel@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 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.