From: Helmut Jarausch <jarausch@skynet.be>
To: Dale <rdalek1967@gmail.com>
Cc: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Encryption questions
Date: Fri, 14 Dec 2018 18:11:20 +0100 [thread overview]
Message-ID: <XORPEW5N.7SFIILMG.7OL7TENT@VXZJ7R2M.CQIKXBFR.6OENCN5X> (raw)
In-Reply-To: <97b5b7e5-8223-bbb7-e096-44c1b613310d@gmail.com> (from rdalek1967@gmail.com on Mon Dec 10 00:46:07 2018)
I use encfs (see github.com/vgough/encfs)
It's in the portage tree.
Here is my private Readme
# Neither .Secret nor Secret should contain data before creation !!!
# CREATION (only once)
e.g.
encfs -i 10 --ondemand --extpass=x11-ssh-askpass `pwd`/.Secret
`pwd`/Secret
or more simply in an XTerm
encfs `pwd`/.Secret `pwd`/Secret
================
# USAGE
encfs [-i idle[minutes]] [--ondemand] --extpass=x11-ssh-askpass <TRUE
FS> <MountPoint>
e.g.
encfs -i 10 --ondemand --extpass=x11-ssh-askpass ~/.Secret ~/Secret
or more simply in an XTerm : (>>> always use the full path of both
folders)
encfs ~/.Secret ~/Secret
=========
After Usage
=========
fusermount -u ~/Secret
If you shut down the machine you don't need to do fusermount -u.
BackUP : ~/.Secret and remember password (e.g. using
app-admin/keepassxc)
Important Note :
ENCFS does not hide the length and modification date/time of a file
If that matter you can archive several file in a tar-file before
encryption.
prev parent reply other threads:[~2018-12-14 17:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-09 23:46 [gentoo-user] Encryption questions Dale
2018-12-10 1:35 ` Grant Taylor
2018-12-10 5:15 ` Dale
2018-12-10 5:40 ` Grant Taylor
2018-12-10 9:25 ` Neil Bothwick
2018-12-10 10:45 ` Mick
2018-12-10 16:21 ` Grant Taylor
2018-12-10 22:09 ` Neil Bothwick
2018-12-13 5:29 ` Dale
2018-12-10 7:57 ` J. Roeleveld
2018-12-14 17:11 ` Helmut Jarausch [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=XORPEW5N.7SFIILMG.7OL7TENT@VXZJ7R2M.CQIKXBFR.6OENCN5X \
--to=jarausch@skynet.be \
--cc=gentoo-user@lists.gentoo.org \
--cc=rdalek1967@gmail.com \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox