public inbox for linux-newbie@vger.kernel.org
 help / color / mirror / Atom feed
From: suneesh <suneesh@naturesoft.net>
To: knb <kernelnewbies@nl.linux.org>
Cc: linux-newbie@vger.kernel.org
Subject: Re: Encypted Loopback Filesystem
Date: Thu, 05 Aug 2004 14:34:35 +0530	[thread overview]
Message-ID: <4111F823.8050702@naturesoft.net> (raw)
In-Reply-To: <1091472748.5577.26.camel@bijar.nec-labs.com>

[-- Attachment #1: Type: text/plain, Size: 2383 bytes --]

Hi

Using losetup you can set a loop device for a particular partition and 
it will ask
passwords for the same. After this one can mount that loop device to a some
mount point. If the password is not correct, the mount will fail.
For eg:

[root@root]# losetup  -e xor /dev/loop3 /dev/hda2
Password:
[root@root]# mkfs -t ext2 /dev/loop3 100
[root@root]# mount /dev/loop3 /NETBSD/
[root@root]# ls /NETBSD/
lost+found
[root@root]# echo hello > /NETBSD/hello
[root@root]# cat /NETBSD/hello
hello
[root@root]# umount /dev/loop3
[root@root]# losetup -d /dev/loop3

Checking if the partition is encrypted
-------------------------------------------------------
[root@root]# mount /dev/hda2 /NETBSD/
mount: you must specify the filesystem type

Mouting it using password
--------------------------------------
[root@root]# losetup  -e xor /dev/loop3 /dev/hda2
Password:
[root@root]# mount /dev/loop3 /NETBSD/
[root@root]# ls /NETBSD/
hello  lost+found

But after mounting the partitiion, it doesn't provide any security and 
the files will
be accessible by everyone who has the right to access it. The protection 
is that it
will ask for passwords when mounting that partition, so if somebody steals
the computer after a power-off, he will not be able to mount and see the 
files under
the encrypted partition.

Regards

Suneesh


Lei Yang wrote:

>Hello,
>
>I am trying to play around loopback device and want to set up an
>encrypted loopback filesystem. I did the following things:
>
>1. losetup -e serpent /dev/loop0 /etc/crypt
>/ect/crypt: Is a directory
>
>So I tried: losetup -e serpent /dev/loop0 /etc/cryptfile and this time
>cryptfile is a plain txt file.
>
>Enter passwd...
>
>2. mkfs -t ext2 /dev/loop0
>3. mount -t ext2 /dev/loop0 /mnt/crypt
>
>After this, how do I verify that anything happened that has enabled
>encryption? I can't understand where the encrypted filesystem lies in
>here:( Plus, when we say 'encrypted', which file is on earth encrypted?
>Is that files and data in /mnt/crypt are encrypted form of
>/etc/cryptfile? Really confused.
>
>TIA!
>
>Lei 
>
>
>--
>Kernelnewbies: Help each other learn about the Linux kernel.
>Archive:       http://mail.nl.linux.org/kernelnewbies/
>FAQ:           http://kernelnewbies.org/faq/
>
>
>
>  
>


-- 
Suneesh T P,
Senior Associate, Embedded,
NatureSoft Pvt Ltd.
Mailto: suneesh@naturesoft.net
WebSite: www.nature-soft.com


[-- Attachment #2: Type: text/html, Size: 3641 bytes --]

           reply	other threads:[~2004-08-05  9:04 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1091472748.5577.26.camel@bijar.nec-labs.com>]

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=4111F823.8050702@naturesoft.net \
    --to=suneesh@naturesoft.net \
    --cc=kernelnewbies@nl.linux.org \
    --cc=linux-newbie@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