From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Ihor Radchenko Newsgroups: gmane.emacs.devel Subject: Re: Storing sensitive data indefinitely in variables or buffers: Whether and how to fix? Date: Thu, 01 Jun 2023 06:42:18 +0000 Message-ID: <874jnrd6ph.fsf@localhost> References: <87fs7dnd1u.fsf@localhost> <6503151d-13be-f299-24a2-76bb9d6fecc8@alphapapa.net> <46880634-f4bd-f036-9d85-0d17ce213112@vodafonemail.de> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="10298"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Adam Porter , emacs-devel@gnu.org To: Jens Schmidt Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Jun 01 08:38:41 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 1q4bxI-0002Tw-QB for ged-emacs-devel@m.gmane-mx.org; Thu, 01 Jun 2023 08:38:40 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1q4bwd-00012F-HM; Thu, 01 Jun 2023 02:38:01 -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 1q4bwX-0000rB-TV for emacs-devel@gnu.org; Thu, 01 Jun 2023 02:37:53 -0400 Original-Received: from mout01.posteo.de ([185.67.36.65]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1q4bwV-0004bF-Pr for emacs-devel@gnu.org; Thu, 01 Jun 2023 02:37:53 -0400 Original-Received: from submission (posteo.de [185.67.36.169]) by mout01.posteo.de (Postfix) with ESMTPS id 2A119240027 for ; Thu, 1 Jun 2023 08:37:49 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1685601469; bh=u7AaYL4VX7otdG1Lw1d2lsTPouw9DOPUBZyoXztw11A=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:From; b=TW1uDISofacPb+LJevFYB4+jT0+0DdN5j4yeTYdp2rp0dVTDytkTZTbrWakqnevvk hKgYCdpj4w7kwRaPl18NdkbCOapTrlUYJZnpuSbEWxbGpp2GXkzMrMEqcmv4OBsr1w u+xJ3lrH4t5EtwcQhaEwzxWbUjMR/Ek59xYv+3JHL5AZv/xWc6SvtHnNDU4aLIyCrn cXkUz3GaU6wHrELBKxcmsupK+0+6a4wb11rg30z7aNELqzO2cuOPANi0WaFq/aJFdN IitYB7HllzSdhqP3Sha3XbMBglfxU2K7/Lt81DEQcbLFB+yFU+0D0pAEx2NofA4LLb sELdYYCQhNrOw== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4QWxJr4ZKgz6txM; Thu, 1 Jun 2023 08:37:48 +0200 (CEST) In-Reply-To: <46880634-f4bd-f036-9d85-0d17ce213112@vodafonemail.de> Received-SPF: pass client-ip=185.67.36.65; envelope-from=yantar92@posteo.net; helo=mout01.posteo.de X-Spam_score_int: -43 X-Spam_score: -4.4 X-Spam_bar: ---- X-Spam_report: (-4.4 / 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, RCVD_IN_DNSWL_MED=-2.3, 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:306480 Archived-At: Jens Schmidt writes: > On 2023-05-31 18:39, Adam Porter wrote: > >> 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. > > Er, that's what I thought plstore.el is about: Persisting sensitive and > non-sensitive data in a structured way, securely, with on-demand > decryption. It certainly has rough edges, and almost no UI at all, but > I liked the basic idea. AFAIK, Adam had a very hard time dealing with auth-source.el. See the reddit link in his message. AFAIR, part of the problem was (1) poor documentation; (2) various edge cases that had to be considered; (3) complex code required to make things work. So, here he is asking for a _simple_ API that does not require too much of tinkering with the internals. If such API is added to plstore, it will certainly be great. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at