From: Gustavo Barros <gusbrs.2016@gmail.com>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: Timothy <orgmode@tec.tecosaur.net>,
org-mode list <emacs-orgmode@gnu.org>
Subject: Re: How to disable org-persist in a given file?
Date: Tue, 2 May 2023 17:36:39 -0300 [thread overview]
Message-ID: <CAM9ALR_F4gjWxOVh_Eq14NOC9nF6g0Cv1jAKb=p4FjPvjqSkWQ@mail.gmail.com> (raw)
In-Reply-To: <CAM9ALR-wvq-CP6d4PtMaCzddFCQVfAx52LHOJAemf_eV11FZ7Q@mail.gmail.com>
On Tue, 25 Apr 2023 at 07:52, Gustavo Barros <gusbrs.2016@gmail.com> wrote:
> My view is that there really should be a way of doing it. Because this
> has relevant security implications. And because users should be able
> to have control of their data in the first place. And then if one such
> a feature, necessarily requiring persistence (as opposed to the
> convenience of "just" speeding things up), a user-error could be
> signaled saying "sorry, can't do that because you disabled
> persistence". And the two cases you mentioned seem quite the exception
> to me. Of course, I'm speaking here about writing information about /
> of the org file itself to an external file, naturally internet
> downloads must go somewhere and that should be easy. The thing is Org
> is used for a lot of things. You can rest assured I have no intention
> of exporting my encrypted files alongside some remote content. But I
> do wish to be able to make sure my passwords are safe.
For the record, even ".org.gpg" files generate an entry in the cache
index. (True, not the `:persist-file' itself though).
My ~/.cache/org-persist/index contains:
(:container
((elisp org-element--headline-cache)
(elisp org-element--cache))
:persist-file "c8/fd2b62-45cc-41c8-8571-d944c76b1f15" :associated
(:hash "7fd2d95e0f9239939598e7a9b8d5a273" :file
"/path/to/myfile.org.gpg" :inode 41551881)
:expiry 30)
Please, please, be reasonable about this. Please, do not store
information about known encrypted files in other places. Please, allow
users to disable the feature cleanly and safely for arbitrary files if
they choose to.
Best,
Gustavo.
next prev parent reply other threads:[~2023-05-02 20:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-22 19:32 How to disable org-persist in a given file? Gustavo Barros
2023-04-23 10:58 ` Ihor Radchenko
2023-04-23 13:15 ` Gustavo Barros
2023-04-23 13:35 ` Ruijie Yu via General discussions about Org-mode.
2023-04-23 14:27 ` Gustavo Barros
2023-04-23 13:54 ` Ihor Radchenko
2023-04-23 14:13 ` Gustavo Barros
2023-04-25 10:24 ` Ihor Radchenko
2023-04-25 10:52 ` Gustavo Barros
2023-05-02 20:36 ` Gustavo Barros [this message]
2023-05-02 20:57 ` Ihor Radchenko
2023-05-02 21:25 ` Gustavo Barros
2023-05-03 10:58 ` Ihor Radchenko
2023-05-03 11:03 ` Gustavo Barros
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAM9ALR_F4gjWxOVh_Eq14NOC9nF6g0Cv1jAKb=p4FjPvjqSkWQ@mail.gmail.com' \
--to=gusbrs.2016@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=orgmode@tec.tecosaur.net \
--cc=yantar92@posteo.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).