unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: <tomas@tuxteam.de>
To: emacs-devel@gnu.org
Subject: Re: Storing sensitive data indefinitely in variables or buffers: Whether and how to fix?
Date: Wed, 31 May 2023 20:17:58 +0200	[thread overview]
Message-ID: <ZHePVqjLLJ7JtG0y@tuxteam.de> (raw)
In-Reply-To: <6503151d-13be-f299-24a2-76bb9d6fecc8@alphapapa.net>

[-- Attachment #1: Type: text/plain, Size: 1304 bytes --]

On Wed, May 31, 2023 at 11:39:31AM -0500, Adam Porter wrote:

[...]

> Since then we've gained the `persist' and `multisession' libraries, which
> seem like good tools, but neither one offers secure storage.
> 
> I think Emacs needs a new library to store Lisp data securely.  Ideally the
> API would simply return a Lisp object which could be used with common
> functions like alist-get, gethash, etc. to read data.  For writing, perhaps
> some kind of simple macro or function wrapper that would store the data
> securely, as-configured, without the application needing to know the
> details.
> 
> Even more ideally, such a feature would be part of `persist' and/or
> `multisession', or at least be built on top of them, to avoid having
> yet-another data-persistence library.

This sounds enticing from a technical POV. OTOH, I'm a bit wary of a
big intransparent cache dump.

I'm already wrangling with Org caching (for now, my sweet spot
seems to be directing it to a non-existing directory and ignoring
the complaints: paradoxically, Emacs is snappier then).

I'd hate to end up with a setup like the monster browsers have
these days: an obscure set of sqlite databases you need a huge
amount of dedication to extract some slivers of information from.

Cheers
-- 
t

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  reply	other threads:[~2023-05-31 18:17 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 [this message]
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

  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=ZHePVqjLLJ7JtG0y@tuxteam.de \
    --to=tomas@tuxteam.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 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).