From: David Masterson <email@example.com>
To: "firstname.lastname@example.org" <email@example.com>
Cc: "firstname.lastname@example.org" <email@example.com>
Subject: Re: Org export to HTML with encrypted information ??
Date: Mon, 2 Dec 2019 06:20:07 +0000 [thread overview]
Message-ID: <DM5PR07MB39905FDE9D99795FE1330EE5A5430@DM5PR07MB3990.namprd07.prod.outlook.com> (raw)
In-Reply-To: <20191130025736.c53tqpqqsvzgc32o@wrycode> (firstname.lastname@example.org's message of "Fri, 29 Nov 2019 21:57:36 -0500")
> Here's a simpler flow. See if it would support your use case:
> Modern PDF readers support password
> encryption. org-latex-export-to-pdf, then encrypt the file and share
> it with your family. If you want to keep it offline, give them USB
> drives. It's not too late to get black Friday deals on the 2.0 sticks.
> Write the password on a sticky note and stick it on your fridge.
> If you're worried about the integrity of the org file on your own
> computer, make it a .gpg file instead, and stick something like:
> # -*- mode:org; epa-file-encrypt-to: ("email@example.com") -*-
> at the top.
This is an interesting idea that I'm considering, but it kind of assumes
that the data is (mostly) static. Updating the information gets a
little tedious, but it is doable. Encryption into the cloud makes it a
little easier to keep it up-to-date for the family as I change the data.
next prev parent reply other threads:[~2019-12-02 6:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-29 7:24 David Masterson
2019-11-29 8:50 ` Colin Baxter
2019-12-02 6:22 ` David Masterson
2019-11-29 11:19 ` Marcin Borkowski
2019-11-29 14:27 ` George Mauer
2019-11-30 2:57 ` wry
2019-12-02 6:20 ` David Masterson [this message]
2019-12-21 4:19 ` stardiviner
2019-12-21 22:50 ` David R
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 \
* 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).