From: Ihor Radchenko <yantar92@posteo.net>
To: Gustavo Barros <gusbrs.2016@gmail.com>
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, 02 May 2023 20:57:31 +0000 [thread overview]
Message-ID: <87zg6mqwn8.fsf@localhost> (raw)
In-Reply-To: <CAM9ALR_F4gjWxOVh_Eq14NOC9nF6g0Cv1jAKb=p4FjPvjqSkWQ@mail.gmail.com>
Gustavo Barros <gusbrs.2016@gmail.com> writes:
> 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)
I think `recentf-save-file' for example is no different. And
org-id-locations-file. And custom-file, if you happen to save safe
buffer-local variables by answering "!" in Emacs prompt. And many many
other places.
I do not think that file name, even from encrypted volume, is something
we need to worry about.
I even suspect that, for example, browser cache often contains all kinds
of secrets, like files associated with web pages were you logged in. And
they can be read by anyone familiar with the layout! (like
https://www.nirsoft.net/utils/chrome_cache_view.html)
> 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.
That said, do not worry about this issue being forgotten. But it is not
easy to design cleanly. I am thinking about it.
Of course, if you have good ideas or patches, they are welcome.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2023-05-02 20:55 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
2023-05-02 20:57 ` Ihor Radchenko [this message]
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=87zg6mqwn8.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=gusbrs.2016@gmail.com \
--cc=orgmode@tec.tecosaur.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).