emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@gmail.com>
To: David Masterson <dsmasterson@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Org-Crypt usage questions
Date: Mon, 05 Sep 2022 15:00:42 +0800	[thread overview]
Message-ID: <87tu5mwbj9.fsf@localhost> (raw)
In-Reply-To: <SJ0PR03MB5455824C11F58C3D6E6F2F56A27F9@SJ0PR03MB5455.namprd03.prod.outlook.com>

David Masterson <dsmasterson@gmail.com> writes:

> I've gotten org-crypt working, but I have some questions:
>
> + the setup in the manual only automatically *encrypts* on save, not
> decrypts on read, correct?

Yes. 

> + decryption is done via org-decrypt-* -- is there another way?

M-x org-reveal (C-c C-r)

> + after org-decrypt-*, will the entries be automatically encrypted
> again or do I have to use org-encrypt-*?

They will be encrypted on save as long as they are marked with "crypt"
(or `org-crypt-tag-matcher', if you alter it).

> + after decrypting, can I re-encrypt with a new symmetric password?

Yes. AFAIK, the symmetric password is never reused. Though it may depend
on your gpg settings.

> + if I use a symmetric password on org-encrypt-entry, does the password
> apply to the whole file or just the entry?

Just the entry.

> + The manual needs the above information on org-[de|en]crypt or did I
> miss it?

You are right. Patches are welcome!

-- 
Ihor Radchenko,
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


  reply	other threads:[~2022-09-05  7:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-05  0:13 Org-Crypt usage questions David Masterson
2022-09-05  7:00 ` Ihor Radchenko [this message]
2022-09-05 20:46   ` David Masterson
2022-09-06 13:13     ` Ihor Radchenko

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=87tu5mwbj9.fsf@localhost \
    --to=yantar92@gmail.com \
    --cc=dsmasterson@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    /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).