From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Max Nikulin Newsgroups: gmane.emacs.bugs Subject: bug#58774: 29.0.50; [WISH]: Let us make EWW browse WWW Org files correctly Date: Thu, 27 Oct 2022 22:35:57 +0700 Message-ID: References: <86bkq0qf8p.fsf@protected.rcdrun.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="14695"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.2.2 To: 58774@debbugs.gnu.org, Org Mode List Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Thu Oct 27 17:41:51 2022 Return-path: Envelope-to: geb-bug-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 1oo50x-0003bX-4X for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 27 Oct 2022 17:41:51 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oo4wP-0000f3-WC; Thu, 27 Oct 2022 11:37:10 -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 1oo4wJ-0000b6-3Y for bug-gnu-emacs@gnu.org; Thu, 27 Oct 2022 11:37:03 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1oo4wI-0007pt-Ra for bug-gnu-emacs@gnu.org; Thu, 27 Oct 2022 11:37:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1oo4wI-0006kk-Ms for bug-gnu-emacs@gnu.org; Thu, 27 Oct 2022 11:37:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Max Nikulin Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 27 Oct 2022 15:37:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 58774 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: wontfix Original-Received: via spool by 58774-submit@debbugs.gnu.org id=B58774.166688497525882 (code B ref 58774); Thu, 27 Oct 2022 15:37:02 +0000 Original-Received: (at 58774) by debbugs.gnu.org; 27 Oct 2022 15:36:15 +0000 Original-Received: from localhost ([127.0.0.1]:59001 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oo4vS-0006jH-Of for submit@debbugs.gnu.org; Thu, 27 Oct 2022 11:36:15 -0400 Original-Received: from mail-lf1-f45.google.com ([209.85.167.45]:40479) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oo4vO-0006il-IS for 58774@debbugs.gnu.org; Thu, 27 Oct 2022 11:36:10 -0400 Original-Received: by mail-lf1-f45.google.com with SMTP id d25so3363663lfb.7 for <58774@debbugs.gnu.org>; Thu, 27 Oct 2022 08:36:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:in-reply-to:from:to:references :content-language:subject:user-agent:mime-version:date:message-id :sender:from:to:cc:subject:date:message-id:reply-to; bh=QAwJZJR904/4fSb54r+zRj41Zs9iCrcEA4p4sGJFX+M=; b=Z4QMTuoSdz5iRZ7c13/QMn2t3m0ulK8kN9SYrKaelTTwtvAL71IWweNHe6SSjJmo3k GmjvQOCqQr1yF6xZvhJP2Q9CoGIVgrHvybtdm/fIxUWStt5y9hkMk4nNeE72m2WC2/6W WM3+vM0O6w2WchMY/J1gj1/wEH+vEfyPJiV6Qn1aZyhDCMEtbUTWpuqEiE/e6YoCj/cG BlWivg4RKEU3ngiKCNp6WwNO2VNR+6z94N9oBJ2PXG3Z7ZWr74kAI+1gr+lOzkYfJWKS uy2XhrMNuaWJ8g9N28QNLNnaJ0en7D/orw96+uQ+zNGPLtCCN65hjfCCufzm5dvheOJ1 70Nw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:from:to:references :content-language:subject:user-agent:mime-version:date:message-id :sender:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=QAwJZJR904/4fSb54r+zRj41Zs9iCrcEA4p4sGJFX+M=; b=d1xmg1dFeHyeBn1Xs45KaDnHk1VS0Y+pOnt9qPTXsQPs1VqGZekAVOuEFGWdLtGauX 96G+Iu3g8FW9iCf1sAyfw9jlHobPT8kLWKILqHSinNqwGpp/yutmc4/Do4DY/8NXhd61 bwDpxs5yX7SaYxTFjk71Uxck8s1qgRkCYy3lHs9BA/O9lqE3XGMtJcVrIdtiIqwgKqh1 cyWXjvTcEVNRdCWYq7cG4883cRXuo9sR+nDu5DU6Ln7lgfj4zMQhzHVvfQQLw5sItOfr UnjjbsB12vkMUFAE0sq4gcMrxwFB+msJ2nj/7NGVaHvGgVLTUFygZ5sBvUmwQS3iZPnE cogA== X-Gm-Message-State: ACrzQf1RMeK5cPhm3BXr0X2V+SWy4VsE/68+rdffh8p4X5422Agha5hq H7a8Bm/lnE4oMBB5D1QcEZxCDbhu06OzSA== X-Google-Smtp-Source: AMsMyM4ZMsgHKKGvlTlexfp0RJcTvbm9eOlshMv4GCT0P5kF9pz13njeffOmuhoq7a4NB5gFh4JqQA== X-Received: by 2002:a05:6512:1287:b0:4a2:a7c3:641d with SMTP id u7-20020a056512128700b004a2a7c3641dmr20184463lfs.511.1666884959788; Thu, 27 Oct 2022 08:35:59 -0700 (PDT) Original-Received: from [192.168.0.101] (nat-0-0.nsk.sibset.net. [5.44.169.188]) by smtp.googlemail.com with ESMTPSA id g1-20020a056512118100b00496693860dcsm220500lfr.232.2022.10.27.08.35.58 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 27 Oct 2022 08:35:59 -0700 (PDT) Content-Language: en-US In-Reply-To: X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: "bug-gnu-emacs" Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:246311 Archived-At: On 27/10/2022 11:55, Jean Louis wrote: > > Now is clear that main problem here is that Org advertises somewhere > to be "text" in MIME context, while it is not, it is by default > "application" and thus unsafe, see: ... > Text Media Types > https://datatracker.ietf.org/doc/html/rfc6838#section-4.2.1 I do not see any problem or any difference what MIME type you are going to associate with Org mode. I agree with Arne that text/... type is more appropriate for a format readable as text. I do not see any contradictions with that RFC. "Org Mode Your life in plain text" Chromium is able to display text/x-org internally just as text/plain and I like it as a way to preview and review file contents. I have not managed to configure Firefox to achieve the same behavior that allows to avoid an external application (certainly not Emacs at first). > We can't just speak of safety alone when we are in general > computing environment, we must also speak of usefulness. I do not mind to have org-view-mode that saves me from execution some code unintentionally. Since most of the code was written without having in mind such feature, I expect a lot of iterations before all possibilities to run code will be plumbed. I suspect that it is possible to ruin whole protection by a small piece of elisp code. I am unaware of sandboxing in Emacs. I expect that making Org mode safe enough will require a lot of efforts by developers. Your are pushing Org to rather hostile environment: highly automated attacks to distribute exploits, market of breached computers listening for remote commands. A running cryptominer would be rather innocent consequence, through the same backdoor you may receive an encryptor or various stuff searching for credentials and access tokens in your files. Emacs is protected mostly by its low popularity. A lot of efforts have been invested in browser making attacks more expensive, but still attractive due to possible benefits. I do not like to increase surface for attacks. Someone may create a plugin targeting Emacs users just because it would be easy enough. Consider converting Org files to HTML as an unpleasant tax for the sake of safety. > All I want is to access my personal read-only Org files by using WWW > and browse from one to the other by using links. How are you going to distinguish your personal files and arbitrary files from non-trusted sources? By signing your files and maintaining list of trusted certificates? For personal notes I would expect e.g. private instance of nextcloud file share (that is internally HTTP server), not accessing files directly through HTTP.