From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Newsgroups: gmane.emacs.devel Subject: Re: Storing sensitive data indefinitely in variables or buffers: Whether and how to fix? Date: Wed, 31 May 2023 20:17:58 +0200 Message-ID: References: <87fs7dnd1u.fsf@localhost> <6503151d-13be-f299-24a2-76bb9d6fecc8@alphapapa.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="/i3dZR1gOrvSia/8" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="35043"; mail-complaints-to="usenet@ciao.gmane.io" To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed May 31 20:19:19 2023 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1q4QPm-0008pI-Fq for ged-emacs-devel@m.gmane-mx.org; Wed, 31 May 2023 20:19:18 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1q4QOu-000418-1Z; Wed, 31 May 2023 14:18:24 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1q4QOp-00040T-5e for emacs-devel@gnu.org; Wed, 31 May 2023 14:18:20 -0400 Original-Received: from mail.tuxteam.de ([5.199.139.25]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1q4QOi-0005fp-NW for emacs-devel@gnu.org; Wed, 31 May 2023 14:18:18 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=tuxteam.de; s=mail; h=From:In-Reply-To:Content-Type:MIME-Version:References:Message-ID: Subject:To:Date:Sender:Reply-To:Cc:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=QYUlRBvexJ/vOLCh66HfkHqyM1UUARxXucplcWUtPiY=; b=oqPD+Rox2mIR/6UOoqRAAEjRDz ur4hss4Wmu3bPBHlv0jhbLmD/igbRQvMJpR1Qs8LiqtNORwcn4JRzUp/h3vffHgYfmNjBSZxqqolJ 5GzBUpasEjVnl7Fd0hGU7R/gRdy3nBE3EMruYVuAVroZULCJOVkd+DiX3g8v/0EVtH0pJUeBbhutq 8mF788qwOztvJaAwQC6stL08Xqho3ISILsKpDnBwV8pr59FKiRzIEmDiKTAnz1t+rvCXQ8RC2EW/y W9nfK8Ctu170VGf4EOs6i9NGZbDSrhxGuI52qP+6tw4C2yWTFcxvEWgPCJOaRI65Bk/Ji3pNjsFED 25vR3vWQ==; Original-Received: from tomas by mail.tuxteam.de with local (Exim 4.94.2) (envelope-from ) id 1q4QOU-0005i4-7E for emacs-devel@gnu.org; Wed, 31 May 2023 20:17:58 +0200 Content-Disposition: inline In-Reply-To: <6503151d-13be-f299-24a2-76bb9d6fecc8@alphapapa.net> Received-SPF: pass client-ip=5.199.139.25; envelope-from=tomas@tuxteam.de; helo=mail.tuxteam.de X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:306457 Archived-At: --/i3dZR1gOrvSia/8 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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. >=20 > I think Emacs needs a new library to store Lisp data securely. Ideally t= he > API would simply return a Lisp object which could be used with common > functions like alist-get, gethash, etc. to read data. For writing, perha= ps > some kind of simple macro or function wrapper that would store the data > securely, as-configured, without the application needing to know the > details. >=20 > 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 --=20 t --/i3dZR1gOrvSia/8 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iF0EABECAB0WIQRp53liolZD6iXhAoIFyCz1etHaRgUCZHePTwAKCRAFyCz1etHa RtL4AJ0TjPttR0njDY/sswbXcKFF7nS2SgCdE2gAuiQ8T0zQWD9TWzqullv56DE= =Qcpq -----END PGP SIGNATURE----- --/i3dZR1gOrvSia/8--