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 ?
Date: Sat, 11 Jun 2022 12:17:48 +0800	[thread overview]
Message-ID: <87k09nq1eb.fsf@localhost> (raw)
In-Reply-To: <SJ0PR03MB545565C9BB903C89277AD353A2A69@SJ0PR03MB5455.namprd03.prod.outlook.com>

David Masterson <dsmasterson@gmail.com> writes:

> I think I've gotten org-crypt working, but I think some things are not
> making sense (it might be just me):
> 1. I've set org-crypt-key to nil (symmetric encryption).
> 2. Can I use a different encryption key for each encrypted paragraph?

Yes. For each individual encrypted headline contents. Just enter
different passwords when queried to encrypt.

> 3. Does org-encrypt only ask for the key the first time?

No. Strictly speaking it may depend on you GnuPG config. Not by default.

> 4. Does org-decrypt only ask for the key the first time?

Depends on your GnuPG config. AFAIK, GnuPG will not cache keys by default.

> 5. How do they know where to get the password when they don't ask?

From gpg-agent.

> 6. Shouldn't org-crypt docs in org manual have examples?

We can mention org-encrypt-entry/entries and org-decrypt-entry/entries.
Would it help?


  parent reply	other threads:[~2022-06-11  4:18 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-10  4:08 org-crypt ? David Masterson
2022-06-11  3:35 ` Tim Cross
2022-06-11 21:29   ` David Masterson
2022-06-12  0:28     ` Tim Cross
2022-06-12  1:37       ` Ihor Radchenko
2022-06-12  3:07       ` David Masterson
2022-06-12  4:04         ` Tim Cross
2022-06-12  6:19           ` David Masterson
2022-06-12  4:15         ` Ihor Radchenko
2022-06-12  5:55           ` David Masterson
2022-06-14  4:13             ` Ihor Radchenko
2022-06-11  4:17 ` Ihor Radchenko [this message]
2022-06-11 21:17   ` David Masterson
2022-06-11 21:46     ` Ignacio Casso

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:

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


* 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


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).