From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Jean Louis Newsgroups: gmane.emacs.help Subject: Re: Is with-temp-buffer really temporary? Date: Tue, 27 Apr 2021 20:39:33 +0300 Message-ID: References: <20210427071122.GA7836@tuxteam.de> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="3851"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mutt/2.0.6 (2021-03-06) Cc: help-gnu-emacs@gnu.org To: Stefan Monnier Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Tue Apr 27 19:42:54 2021 Return-path: Envelope-to: geh-help-gnu-emacs@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 1lbRja-0000vM-F1 for geh-help-gnu-emacs@m.gmane-mx.org; Tue, 27 Apr 2021 19:42:54 +0200 Original-Received: from localhost ([::1]:40100 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lbRjZ-0006r5-F7 for geh-help-gnu-emacs@m.gmane-mx.org; Tue, 27 Apr 2021 13:42:53 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:45012) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lbRiR-0006pi-Tv for help-gnu-emacs@gnu.org; Tue, 27 Apr 2021 13:41:43 -0400 Original-Received: from stw1.rcdrun.com ([217.170.207.13]:55501) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lbRiH-0006bd-QC for help-gnu-emacs@gnu.org; Tue, 27 Apr 2021 13:41:43 -0400 Original-Received: from localhost ([::ffff:41.202.241.10]) (AUTH: PLAIN securesender, TLS: TLS1.3,256bits,ECDHE_RSA_AES_256_GCM_SHA384) by stw1.rcdrun.com with ESMTPSA id 000000000002BEDC.0000000060884CCA.00003349; Tue, 27 Apr 2021 10:41:30 -0700 Mail-Followup-To: Stefan Monnier , help-gnu-emacs@gnu.org Content-Disposition: inline In-Reply-To: Received-SPF: pass client-ip=217.170.207.13; envelope-from=bugs@gnu.support; helo=stw1.rcdrun.com X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.io gmane.emacs.help:129170 Archived-At: * Stefan Monnier [2021-04-27 19:54]: > >> > And if Emacs exits, finishes the process, is memory then scraped? > >> Of course not. > > I'd think this is your operating system's job. > > Also, given the way computers are currently implemented, the cost of > having to scrape all memory immediately after use would be somewhat > high, especially compared to the benefit: > > - most of that memory contains data of no significance, so most of that > work is wasted. > - it just removes one particular attack vector, among many others, so > the added security gain is low. Purpose is to implement Emacs Lisp based uploading of files that are on the fly GnuPG/PGP encrypted and would like to have zero-knowledge privacy from hosting provider. As I see it now, it is not easy task. Could you give me pointers on how to accept uploaded data, should I use (read-event) to read POST request like one byte by byte? -- Jean Take action in Free Software Foundation campaigns: https://www.fsf.org/campaigns Sign an open letter in support of Richard M. Stallman https://stallmansupport.org/ https://rms-support-letter.github.io/