From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.devel Subject: Re: What is the most useful potential feature which Emacs lacks? Date: Sun, 17 May 2020 23:45:28 -0400 Message-ID: References: <865zd1h3ru.fsf@duenenhof-wilhelm.de> <875zd15rze.fsf@gmx.de> <87wo5gjfbr.fsf@gmx.de> <87eermkdov.fsf@gmx.de> <87r1vlipg4.fsf@gmx.de> <86lflrttxn.fsf@duenenhof-wilhelm.de> Reply-To: rms@gnu.org Content-Type: text/plain; charset=Utf-8 Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="63814"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org, michael.albinus@gmx.de, ndame@protonmail.com To: dieter@duenenhof-wilhelm.de (H. Dieter Wilhelm) Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon May 18 05:46:02 2020 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 1jaWj3-000GS3-Mx for ged-emacs-devel@m.gmane-mx.org; Mon, 18 May 2020 05:46:01 +0200 Original-Received: from localhost ([::1]:44912 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jaWj2-0007qf-Py for ged-emacs-devel@m.gmane-mx.org; Sun, 17 May 2020 23:46:00 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:40212) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jaWiZ-0007Ml-Sv for emacs-devel@gnu.org; Sun, 17 May 2020 23:45:31 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:48408) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jaWiZ-0001Un-0J; Sun, 17 May 2020 23:45:31 -0400 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.82) (envelope-from ) id 1jaWiW-00055r-5u; Sun, 17 May 2020 23:45:28 -0400 In-Reply-To: <86lflrttxn.fsf@duenenhof-wilhelm.de> (dieter@duenenhof-wilhelm.de) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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" Xref: news.gmane.io gmane.emacs.devel:250696 Archived-At: [[[ To any NSA and FBI agents reading my email: please consider ]]] [[[ whether defending the US Constitution against all enemies, ]]] [[[ foreign or domestic, requires you to follow Snowden's example. ]]] > Sorry, I can't tell what the norm is. Personally, I'm using a webhoster > for my Nextcloud instance. And I've got a colleague which is running it > on his Raspberry Pi from home. Of course: Both is possible. Since we can't determine whether any given user will want the auto-encrypt-decrypt, we should let users specify yes or no. Eventually we might develop ideas for defaults more sophisticated than just "yes" and "no". The goal here is to be able to save and retrieve files on any server, such that the server operator can't determine their contents or their names. Tramp would generate the remote file name to use, encrypt the file contents, then write that into the generated remote file name on the remote machine. Tramp would have to maintain a local table mapping specified (local) names to generated (remote) names. The data that gets encrypted could contain first the specified file name, then a delimiter, then the contents of the file. That way, if you lose the local table or it is lacking some files, but you have the encryption key, you can decrypt each saved remote file and find out what its original specified file name was. -- Dr Richard Stallman Chief GNUisance of the GNU Project (https://gnu.org) Founder, Free Software Foundation (https://fsf.org) Internet Hall-of-Famer (https://internethalloffame.org)