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: Thu, 1 Jun 2023 09:34:58 +0200 Message-ID: References: <87fs7dnd1u.fsf@localhost> <6503151d-13be-f299-24a2-76bb9d6fecc8@alphapapa.net> <83h6rse2zb.fsf@gnu.org> <871qivd6ek.fsf@localhost> <83353bejwi.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="b68g3sE15ML9NmuP" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="20046"; 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 Thu Jun 01 09:35:46 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 1q4cqX-0004yR-A0 for ged-emacs-devel@m.gmane-mx.org; Thu, 01 Jun 2023 09:35:45 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1q4cq3-0002qa-4F; Thu, 01 Jun 2023 03:35:15 -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 1q4cpy-0002q7-JO for emacs-devel@gnu.org; Thu, 01 Jun 2023 03:35:11 -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 1q4cpr-0007pm-L8 for emacs-devel@gnu.org; Thu, 01 Jun 2023 03:35:10 -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=0bgo8heSYfS/h0lbQMUzDyxisnfqH9F57ikMEEM2nlw=; b=QbqbSCJ8isjasVbNNgGG6xuAyb wbR0tyrH4Og/xMUipMA86tl+xaI9+2XnUBFqA6QoHPnWm12OKawjFtJs5XIectFZI1DcEF+Xt599g LUva/zeljtkDbQ4mTz15FC5J05dpLiZnVgHAdXQ9n4pArl0FPokOQaEYVtZLDnMdhmcG6ky9i8uCc N1XSV+0PClPBDXPMdb/mtdrkHMzFEmf9lnn/mOOCPEXsNmEp2qADIqPLmRYZzU/K+rfPffPBiG77U R5MtdOImldUFE+xRMh/h8NY7hH2LGLe6KTKFVLSaN2pATuc1tHm+3qO1yklLwyBQ1gi8Np/u6pVaB K2IdixWA==; Original-Received: from tomas by mail.tuxteam.de with local (Exim 4.94.2) (envelope-from ) id 1q4cpm-0008Iz-0V for emacs-devel@gnu.org; Thu, 01 Jun 2023 09:34:58 +0200 Content-Disposition: inline In-Reply-To: <83353bejwi.fsf@gnu.org> 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:306493 Archived-At: --b68g3sE15ML9NmuP Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jun 01, 2023 at 10:11:57AM +0300, Eli Zaretskii wrote: > > From: Ihor Radchenko > > Cc: Adam Porter , emacs-devel@gnu.org, > > jschmidt4gnu@vodafonemail.de > > Date: Thu, 01 Jun 2023 06:48:51 +0000 > >=20 > > Eli Zaretskii writes: > >=20 > > >> I think Emacs needs a new library to store Lisp data securely. > > > > > > Can't we use the GnuTLS cryptography functions, like > > > gnutls-symmetric-encrypt, for that? > >=20 > > I think that it is not just about encryption. > > The API should also have ways to expire passwords and deal with a need > > to update them individually. >=20 > What would be the effect of expiring a password on stuff stored using > the password that just expired? would it mean I can no longer access > that stuff? Or would it mean I must use a new password for storing > new stuff? Or something else? This might be a slight misunderstanding: if I understand Ihor correctly, only the cached password is expired, so the user would have just to reenter it. This is to mitigate the risk that someone else takes over an abandoned session (a mild form of user presence check, if you will). If I understand you correctly, you seem to envision the expiry of the password itself, which is something different, to happen at the "server" side. Cheers --=20 t --b68g3sE15ML9NmuP Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iF0EABECAB0WIQRp53liolZD6iXhAoIFyCz1etHaRgUCZHhKGgAKCRAFyCz1etHa Ri7iAJ9PeuNrsVhxtVI/hWJT6tI1f5i4VwCdHcYkPWKUaRZQ61lVt+1Sr2gQkdg= =opL9 -----END PGP SIGNATURE----- --b68g3sE15ML9NmuP--