From: Jari Ruusu <jariruusu@users.sourceforge.net>
To: linux-crypto@nl.linux.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: Announce loop-AES-v2.2c file/swap crypto package
Date: Mon, 25 Oct 2004 19:55:10 +0300 [thread overview]
Message-ID: <417D2FEE.D0FB3C99@users.sourceforge.net> (raw)
In-Reply-To: 417BE3D6.BB54FE7D@users.sourceforge.net
Jari Ruusu wrote:
> - Added random key setup option to mount and losetup. This can be used to
> encrypt /tmp with random keys.
As some of you may have noticed, new example 4 of loop-AES README file was
fucked up. One important step was missing from example 4 instructions, and
if those instructions were followed literally, /tmp partition most likely
ended up being unwritable by non-root users.
Below is the fix in patch form, and URL of full corrected README file:
http://loop-aes.sourceforge.net/loop-AES.README
--
Jari Ruusu 1024R/3A220F51 5B 4B F9 BB D3 3F 52 E9 DB 1D EB E3 24 0E A9 DD
--- ../loop-AES-v2.2c/README Sun Oct 24 19:19:00 2004
+++ ./README Mon Oct 25 19:15:39 2004
@@ -1,4 +1,4 @@
-Written by Jari Ruusu <jariruusu@users.sourceforge.net>, October 24 2004
+Written by Jari Ruusu <jariruusu@users.sourceforge.net>, October 25 2004
Copyright 2001,2002,2003,2004 by Jari Ruusu.
Redistribution of this file is permitted under the GNU Public License.
@@ -616,7 +616,10 @@
/dev/hda555 /tmp ext2 defaults,loop=/dev/loop2,encryption=AES128,phash=random 0 0
^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^ ^
-Third, run "mount /tmp" command and you are done.
+Third, run "mount /tmp" and "chmod a+rwxt /tmp" commands.
+
+Fourth, make sure that "chmod a+rwxt /tmp" command is run by init scripts
+somewhere after "mount -a" command is run.
Encryption keys and plaintext data on above type mount vanish on unmount or
power off. Using journaled file system in such case does not make much
prev parent reply other threads:[~2004-10-25 16:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-24 17:18 Announce loop-AES-v2.2c file/swap crypto package Jari Ruusu
2004-10-25 16:55 ` Jari Ruusu [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=417D2FEE.D0FB3C99@users.sourceforge.net \
--to=jariruusu@users.sourceforge.net \
--cc=linux-crypto@nl.linux.org \
--cc=linux-kernel@vger.kernel.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.
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 NNTP newsgroup(s).