From: stardiviner <email@example.com>
Subject: Re: Org export to HTML with encrypted information ??
Date: Sat, 21 Dec 2019 12:19:52 +0800 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
David Masterson <email@example.com> writes:
> My use-case is this:
> I'd like to use Org to write up *all* the information about my family
> life (so to speak) including medical histories of my family, issues with
> the house, bank accounts, financial information, etc., so that my family
> has all the information to refer to when necessary in a (hopefully)
> well-structured form. Naturally, this is going to have a fair amount of
> really sensitive information. By carefully outlining the information, I
> can structure the sensitive information to be in key parts of the
> documents that I can then encrypt using org-crypt.
> That part is straightforward. The tricky part is that my family is not
> "Emacs literate" and, so, I'm thinking the best idea is to export the
> information from Org files to HTML files so that I can then present to
> them as a website. They are used to browsing the web, so this should be
> more natural to them. The problem that I'm looking for help with is how
> to deal with the encrypted information? Any suggestions?
I have same needs for my all-in-Org knowledge database. I will keep some
personal information in some public Org files but encrypt Org headlines with
encrypted contents. That will have more control on your hand. More choices.
[ stardiviner ]
I try to make every word tell the meaning what I want to express.
IRC(freenode): stardiviner, Matrix: stardiviner
next prev parent reply other threads:[~2019-12-21 4: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
2019-12-21 4:19 ` stardiviner [this message]
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).